-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected behavior with virtualenvs #424
Comments
Hmm. I've got a feeling I remember that there's something odd about the way virtualenvs work on Windows, but I don't remember what it is. 😕 Does |
If flit install goes away, will we be able to still use the simlink trick so that we can develop inner development space and run in site-packages?
Our would I be better just to add my project to the Python path?
From: Thomas Kluyver ***@***.***>
Sent: Saturday, July 31, 2021 12:22 PM
To: takluyver/flit ***@***.***>
Cc: Doug Ransom ***@***.***>; Author ***@***.***>
Subject: Re: [takluyver/flit] Unexpected behavior with virtualenvs (#424)
Hmm. I've got a feeling I remember that there's something odd about the way virtualenvs work on Windows, but I don't remember what it is. 😕
Does pip install . work? That should now automatically make a wheel and then install it for you. One day, flit install will probably go away in favour of using pip directly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftakluyver%2Fflit%2Fissues%2F424%23issuecomment-890393594&data=04%7C01%7C%7Ca3377d5e2acc45cdbe9d08d9545877d0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637633561202147420%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IC6nGShB4gGbbtBuQgouXYH87aE9OzNIZFeOgss9KqY%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA262UVRASWFQU7B3OVR3P3T2RENLANCNFSM5A3CMT3A&data=04%7C01%7C%7Ca3377d5e2acc45cdbe9d08d9545877d0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637633561202147420%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CUVXSodOyRD9HTIodX6R7tjKPqxN6sbxYPq6%2FswVmic%3D&reserved=0>.
|
There's work towards a standardised mechanism for editable installs, so That said, I may still keep the symlink trick around, so long as it's not too much work to maintain, because it appeals to me more than the |
I'm not aware of anything like that; let me know if you find/make one. 🙂 |
Hm. I think most if the information for a published package on pypi is available through this api: https://warehouse.readthedocs.io/api-reference/json.html#project |
On windows,
flit install
flit install --symlink
flit install --env
flit install --python = c:\users\dougr\onedrive\doug\codingprojects\dt\nl\scripts\python.exe
All install in the base python instead of the virtual environment.
The workaround is
More information on python (from the [pyenvutils](https://pypi.org/project/pyenvutils/ module also packaged with flit).
The text was updated successfully, but these errors were encountered: