Failing to install the my project in the virtual environment #5151
-
Hello everyone, I'm following the flask tutorial in the flask docs and stuck on trying to make the project installable. I have added the pyproject.toml and MANIFEST.in as indicated in the tutorial but when I run `Usage: -e option requires 1 argument` I'm not quite sure what positional argument to add but when I add the application package (blog) as a positional argument, I get this error: `Obtaining file:///D:/flask/tut/blog × Getting requirements to build editable did not run successfully.
note: This error originates from a subprocess, and is likely not a problem with pip. × Getting requirements to build editable did not run successfully. note: This error originates from a subprocess, and is likely not a problem with pip` That was after I temporarily moved the pyproject.toml and MANIFEST.in into the package Also I'm using windows and you can look at my project here |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
try |
Beta Was this translation helpful? Give feedback.
-
Using Windows for web dev is already a poor choice. I seriously recommend you to consider using at least WSL2 instead of doing this stuff directly on Windows. vscode remote still lets you run your editor on windows, but the stuff would not run on windows itself that way. Anyway, are you sure you did |
Beta Was this translation helpful? Give feedback.
-
I ran into this problem following the flaskr tutorial. The problem lies in the other directories in the root folder created earlier in the tutorial (instances and tests). This confuses pip install as well as build automation. You are offered the solutions 1-3 but those are not very clear on howto if you are new to creating packages and wheels in python. Easiest is number 3 by adding the following lines to your pyproject.toml file:
Now pip install and build have the package explicitly defined an do there thing without overthinking the presence of other directories. Maybe someone can add this to the tutorial so newcomers don't get confused ? |
Beta Was this translation helpful? Give feedback.
I ran into this problem following the flaskr tutorial. The problem lies in the other directories in the root folder created earlier in the tutorial (instances and tests). This confuses pip install as well as build automation. You are offered the solutions 1-3 but those are not very clear on howto if you are new to creating packages and wheels in python. Easiest is number 3 by adding the following lines to your pyproject.toml file:
Now pip install and build have the package explicitly defined an do there thing without overthinking the presence of other directories. Maybe someone can add this to the tutorial so newcomers don't get confused ?