-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
2022.11.21: pep517 build do not isntall nox/tox_to_nox.jinja2 #671
Comments
I think this is because we don't explicitly mention it here: https://github.com/wntrblm/nox/blob/6957a4c1bf4f8f403fc30664812cbb19eb0b2417/pyproject.toml#LL70 I've just added: - package-data = { "nox" = [ "py.typed" ] }
+ package-data = { "nox" = [ "py.typed", "tox_to_nox.jinja2" ] } And I can now see the |
Sure, done. |
Thx 👍 |
Any chance of a release with this fix? ATM |
Current Behavior
Looks like pep517 based build do not adds nox/tox_to_nox.jinja2 to generated .whl archive,
Because of that pytest is failing
After add in install prpocedure manuall install that file pytest is OK
Expected Behavior
Looks like nox/tox_to_nox.jinja2 shopuld be part of the generated .whl archive.
Steps To Reproduce
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesEnvironment
Anything else?
No response
The text was updated successfully, but these errors were encountered: