-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Windows embedable support #2353
Conversation
Signed-off-by: Bernát Gábor <[email protected]>
For example, for Python 3.10 the embeddable file name would be "python310.zip". If this file would be found in `sys.path`, the virtualenv should copy it into the "<venv>\Scripts\python310.zip".
Helps to test virtualenv creator classes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to fix the tests first here 👍
Of course. Just give me some time) |
The importlib accepts a Path-like objects from Python 3.6
It is possible to make pass CPython3 tests under Python 2, but it's better to disable it instead of decreasing the readability and performance of Python 3 style.
Hm. Looks like last PR must fix 1 test here. |
Can you rebase the PR on main? |
I expected the error to occurs in this PR #2363 and I fix it. But it seems we need to merge that PR and restart tests here to see logs and catch the error. New logs should tell us more about the error, at least the path to non-existent file. |
Merged now so you'll need to rebase against main 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow) I expected an exception, but OK) |
with this PR, I'm now getting |
tox -e fix_lint
)docs/changelog
folderAfter these steps #1774 (comment)
the embeddable Python should works fine with virtualenv.
Virtualenv now ships zipped std lib packages along with other dll and pyd files.