-
Notifications
You must be signed in to change notification settings - Fork 22
feat(release): Enable sdist artifacts #398
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
Conversation
|
I've had issues with Unless I remember the problem incorrectly, it looks like maturin has been fixed to support this use case. When I build the sdist it now includes these files: So it looks like Maturin is now
I think at a minimum we need to add a step to the sdist CI that verifies we can install each of the sdists generated for each module. |
|
I'm also open to merging #275 but don't know enough about freethreading to know what else needs to be fixed there. |
I will try to add a test to verify.
All the tests seem to pass without obvious issues. I haven’t looked deeply enough into the codebase to say for certain, but I think experimental support should be fine. Most of the heavy lifting is done in PyO3's internals. So using safe api's is thread-safe. |
I think you can just add a It was mostly this comment about adding pytest-freethread before merging it. If we declare but then use |
|
Where should I add this test, in the test-python workflow? And should it run for every MR, just for main or on release? |
No I think you can just add it as a step between building and uploading the sdist in the release workflow. I think the CI is too long to test on every PR. I'm happy to just have that verify before it gets pushed to PyPI |
6922569 to
85d817c
Compare
|
Done, tested the job here https://github.com/kylebarron/arro3/actions/runs/17586733255/job/49956641911 |
|
Thanks! |
While testing various packages on free-threaded Python (3.13t and 3.14t), I needed to install arro3. Because there are no prebuilt wheels or a published sdist, I currently have to install arro3 directly from Git. To make this easier, I’d like to re-enable publishing of the sdist distribution.
I noticed this was previously disabled in #113. I tested the sdist locally and did not encounter any issues. If there were specific problems that led to disabling it, could you elaborate on them and confirm whether they’re now resolved?