However, this second approach doesn't include the expected bin directory and other stuff I'm used to seeing on Linux. I can create a virtualenv with: "C:\Program Files\Mu\Python\python.exe" -m venv -without-pip foo :-/ Any idea how I might get around this? (HINT: I believe the answer is "you can't".) as a regular user, I can't write to anything within "C:\Program Files". This is, I believe due to file system permissions (i.e. If I try to do "C:\Program Files\Mu\Python\python.exe" -m venv foo I get complaints about ensurepip not working. These shortcomings can be solved in the same way we ensure tkinter is available during packaging. As a result I've just copied them over manually from a regular Python install. I realise that the default Python that comes with Mu does NOT have the necessary venv, ensurepip and pip modules in the expected places. ![]() Using just the Python version installed with Mu, try to create a virtualenv and run scripts from within it by calling the virtualenv's Python executable directly. So I've been tearing my hair out over this today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |