-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
sdist is missing tests #1674
Comments
tests are written in Rust, what downstream would run Rust tests for a Python sdist? |
I'm packaging |
Thanks, I understand the benefits. I'm just not sure whether adding tests to sdist would work since it needs to be run by And why not using the github release |
Github tarball is possible too, but it creates a bit more maintenance work because there is no simple way how to find the tarball automatically. The sdist url is directly referenced from PyPI so it could be easily found without manual intervention. BTW, if tests should be run using |
|
fwiw the github api provides a way to get the tarball of the latest release, and we also link the github url from pypi, so you might be able to get your automation this way: https://docs.github.com/de/rest/releases/releases?apiVersion=2022-11-28#get-the-latest-release |
Git doesn't guarantee that the generated archives will be stable. There have already been cases in the past when changes in git or one of its dependencies suddenly caused all archives to change and broke all downstream consumers via checksum mismatches. |
I'm going to close this because we don't have any tests written in Python to distribute, and I'm removing |
Bug Description
The sdist package as PyPI is missing tests, although
noxfile.py
file is in the sdist. Please add tests to sdist to make downstream testing easier. Thank you.Your maturin version (
maturin --version
)1.1.0
Your Python version (
python -V
)N/A
Your pip version (
pip -V
)N/A
What bindings you're using
None
Does
cargo build
work?If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash
/
)?Steps to Reproduce
The text was updated successfully, but these errors were encountered: