You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to use the tool virtualenv-tools to build a deployable packages.
We are creating our virtualenv with Python 3.11 and when virtualenv-tools tries to unmarshal the PYC files, it of course fails, because the bytecode does not match.
Wheel, being an installation format that is intended to work across multiple versions of Python, does not generally include .pyc files.
and
Wheel archives do not need to include .pyc and are less tied to a specific Python version or implementation.
So, while including PYCs is not explicitly prohibited, it is apparently not best practice nor recommended. According to the maintainer of virtualenv-tools, apparently it is wrong. :) See: Yelp/virtualenv-tools#29
Could we get another wheel without the PYC files? I would be happy to submit a PR, but this appears to be a build issue, and the repo doesn't contain that information.
Thanks!
The text was updated successfully, but these errors were encountered:
I think this was fixed in #906, but I haven't done another release yet. I will work on that soon, but I think in the meantime you could pin the version to 0.15.0 which doesn't have the .pyc files.
We are trying to use the tool virtualenv-tools to build a deployable packages.
We are creating our virtualenv with Python 3.11 and when virtualenv-tools tries to unmarshal the PYC files, it of course fails, because the bytecode does not match.
According to the wheel spec (https://packaging.python.org/en/latest/specifications/binary-distribution-format/)
and
So, while including PYCs is not explicitly prohibited, it is apparently not best practice nor recommended. According to the maintainer of virtualenv-tools, apparently it is wrong. :) See: Yelp/virtualenv-tools#29
Could we get another wheel without the PYC files? I would be happy to submit a PR, but this appears to be a build issue, and the repo doesn't contain that information.
Thanks!
The text was updated successfully, but these errors were encountered: