-
Notifications
You must be signed in to change notification settings - Fork 114
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
virtualenv plugin doesn't work with current tox #427
Comments
Unfortunately,
|
It seems rather unhappy with that:
This is with:
|
Advantages ========== - Can do the entire loading in one shot in pure rust from a python iterable. - Work using rust semantics. - Really just works. - Only requires a pyi for type declarations (?). Drawbacks ========= - Likely slower than cffi for pypy, but unlikely to be slower than the slog of pure python. - Graal don't work in tox (oracle/graalpython#427).
Advantages ========== - Can do the entire loading in one shot in pure rust from a python iterable. - Work using rust semantics. - Really just works. - Only requires a pyi for type declarations (?). Drawbacks ========= - Likely slower than cffi for pypy, but unlikely to be slower than the slog of pure python. - Graal don't work in tox (oracle/graalpython#427).
I can reproduce that, it seems that a recent virtualenv release broke the plugin. I'll look into it, thank you for the report |
🫡 |
Fixed on master, you can get the fixed version already by installing the plugin from github:
|
Finally got around to trying it, it failed with the tox 4.20.1 but after upgrading to 4.21.2 it's now running just fine 👍 |
Trying to add graal to an existing project I'm hitting an issue where it doesn't seem to cooperate with tox / virtualenv. The test project is just composed of 3 files:
pyproject.toml
test.py
tox.ini
using the global tox (4.20.0 installed via pipx on a 3.10) hits a TypeError:
creating a local venv using graal, it installs an outdated tox (3.28.0), complains that it wants
isolated_build = True
, then fails withTypeError: 'NoneType' object is not callable
anyway (it doesn't provide a complete traceback, but I assume the issue is similar to the one in 4.20)The text was updated successfully, but these errors were encountered: