Skip to content

Uploading nightly wheels to the Scientific Python nightly channel #1033

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

Open
matthewfeickert opened this issue Mar 27, 2025 · 6 comments
Open

Comments

@matthewfeickert
Copy link

👋 Would you be interested/willing to upload nightly wheels to the scientific-python nightly channel?

This would make the wheels easier to discover by hosting them in a "standard" place. It will also make it easier for downstream projects to test against multiple packages, since they won't need to specify multiple locations in their CI scripts.

You can read more about why and how we are building / testing against nightly wheels here:
https://scientific-python.org/specs/spec-0004/

We also provide a GitHub action to upload and manage nightly builds:
https://github.com/scientific-python/upload-nightly-action/

If you have questions we (@jarrodmillman, @bsipocz, @tupui, @Carreau, @matthewfeickert) can help address them.

Example process here: scientific-python/upload-nightly-action#82

@LecrisUT
Copy link
Collaborator

I guess if there are users wanting some new feature currently in development, I don't see why not. We also provide a copr repo for nightly builds if they want to go the full Fedora integration and really test against all the new packages.

@matthewfeickert
Copy link
Author

I guess if there are users wanting some new feature currently in development, I don't see why not.

Great. Please see scientific-python/upload-nightly-action#124 to get onboarded and to ask any questions you have. 👍

We also provide a copr repo for nightly builds if they want to go the full Fedora integration and really test against all the new packages

That's good to know, but we're focusing on testing the broader Scientific Python ecosystem together. I will also admit that I don't know anything about Fedora testing, but we also don't currently suggest that anyone install the Scientific Python ecosystem at the operating system level.

@henryiii
Copy link
Collaborator

CMake 4 and a few others things are taking my time at the moment, but I'm in favor. :)

@LecrisUT
Copy link
Collaborator

CMake 4 and a few others things are taking my time at the moment

Dealing with the fallout of projects having too low cmake_minimum_required ? I also got a list of ~700 packages to forward to Fedora colleagues.

@henryiii
Copy link
Collaborator

henryiii commented Mar 27, 2025

Mostly updating things at the moment, like cmake-python-distributions and https://cliutils.gitlab.io/modern-cmake. You can work around any projects that are set too low with -DCMAKE_POLICY_VERSION_MINIMUM=3.5 (and they've been producing warnings for a long time, though people ignore those warnings). Setting an upper limit also fixes it.

@LecrisUT
Copy link
Collaborator

You can work around any projects that are set too low with -DCMAKE_POLICY_VERSION_MINIMUM=3.5 (and they've been producing warnings for a long time, though people ignore those warnings). Setting an upper limit also fixes it.

I thought about setting -DCMAKE_POLICY_VERSION_MINIMUM but that could still lead to broken -devel packages and I want to force the maintainers to contact the upstream about updating this properly with good modern practices. I hope I have it all covered in https://fedoraproject.org/wiki/Changes/CMake4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants