You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the app locally using pyent to support the 3.9 requirement. However, I have ask the app to create an new app that requires Python 3.12. The app did ask for and helped setup an appropriate venv for the new app immediately after I inputted the requirements for the new app. However GPT-Pilot does not seem to understand how to use the target app's venv.
This has resulted in my having to run "command -requests" -- e.g., "Can I run command: pytest tests/test_db.py with 60s timeout?" -- outside of GPT-Pilot. Otherwise the pytest configured for 3.9 will fail.
Workaround: I keep a separate terminal window open to the target project being implemented in order to use the venv that was created in the beginning of the project. This allows me to say "no" to the requests from GTP-Pilot and copy/paste the command(s) into the terminal window to be run there.
Effect(s):
o This issue increases the burden on the developer and reduces the overall attractiveness of using GPT-Pilot for development.
The text was updated successfully, but these errors were encountered:
JeffreyPeacock
changed the title
[Bug]: The version of Python (3.9) defines how a new Python app will be treated during development, and hamper the UX.
[Bug]: The version of Python (3.9) defines how a new Python app will be treated during development, and hampers the UX.
Nov 15, 2024
Version
Command-line (Python) version
Operating System
Ubuntu Linux
What happened?
I am running the app locally using
pyent
to support the 3.9 requirement. However, I have ask the app to create an new app that requires Python 3.12. The app did ask for and helped setup an appropriatevenv
for the new app immediately after I inputted the requirements for the new app. However GPT-Pilot does not seem to understand how to use the target app'svenv
.This has resulted in my having to run "command -requests" -- e.g., "Can I run command:
pytest tests/test_db.py
with 60s timeout?" -- outside of GPT-Pilot. Otherwise thepytest
configured for 3.9 will fail.Workaround: I keep a separate terminal window open to the target project being implemented in order to use the
venv
that was created in the beginning of the project. This allows me to say "no" to the requests from GTP-Pilot and copy/paste the command(s) into the terminal window to be run there.Effect(s):
o This issue increases the burden on the developer and reduces the overall attractiveness of using GPT-Pilot for development.
The text was updated successfully, but these errors were encountered: