📦 allow 3.14 builds + update setuptools#394
Conversation
|
I still need to check whether this troubles the pypi release pipeline |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
| authors = [{name = "Safran", email = "[email protected]"}] | ||
| description = "A package that implements a data model tailored for AI and ML in the context of physics problems" | ||
| requires-python = ">=3.11, <3.14" | ||
| requires-python = ">=3.11, <=3.14.3" |
There was a problem hiding this comment.
Why not <3.15 ? You specifically want to filter out versions above 3.14.4 ?
There was a problem hiding this comment.
True! I wanted to limit to the current python version but it is indeed too restrictive
|
in this PR (to ProtoV1) i added the github actions to test against python 3.14, I discovered, Muscat is not out for osx python 3.14. Working on a MR for muscat. |
|
I am working on plaid's SPACK recipe not conda's. Muscat is not a plaid dependency however it is indeed essential to have it as well. Do you see some obstacles for Muscat's SPACK recipe for python 3.14? |
|
I know, but the GitHub action are configured with conda. So to support plaid fully, we need to push Muscat to 3.14, or change the GitHub action to use pypi as backend. For the moment there is not hard point to publish a Muscat package for 3.14. I'm already working on the recipe. |
|
the recipe is ready waiting for some feedback before merging. conda-forge/muscat-split-feedstock#61 |
3 participants
Thanks for contributing! Please make sure your PR title and content follow the guidelines.
Leave this checklist below in your PR description and tick the corresponding boxes.
Checklist
📋 Description (optional)
Preparing the deployment of plaid in Spack: need latest build and run dependencies to be compatible
This needed a small refactor in the pyproject.toml