Skip to content

Conversation

@sbailey
Copy link
Contributor

@sbailey sbailey commented Nov 13, 2025

desihub/desitarget#864 fixed the underlying incompatibility that previously required us to pin pip==25.2 . This PR removes that pinned version. This may trigger similar issues in other packages for followup.

@sbailey
Copy link
Contributor Author

sbailey commented Nov 13, 2025

This doesn't work with the pinned desimodel==0.19.3 which was before desimodel pyproject.toml and setup.cfg were added. This highlights that we probably have a bunch of tags that can't be installed with pip 25.3. To be continued...

@weaverba137
Copy link
Member

It looks like you didn't add --no-build-isolation.

@coveralls
Copy link

Coverage Status

coverage: 37.704% (-0.009%) from 37.713%
when pulling ab63c24 on pip_version
into 6a90a05 on main.

@weaverba137
Copy link
Member

@sbailey, I think this OK to merge as-is if you would rather address issues like pyproject.toml separately.

@sbailey
Copy link
Contributor Author

sbailey commented Nov 18, 2025

Yes, let's address pyproject.toml in a separate PR.

Summarizing the state of installing other desi packages that were tagged before adding pyproject.toml + setup.cfg — either

  • pin pip<25.3 (or perhaps pin setuptools, but pinning pip has the same effect); or
  • pip install --no-build-isolation ...

Those workaround don't require any changes to desispec itself, but they impact how we install packages for testing.

@sbailey sbailey merged commit 660b603 into main Nov 18, 2025
18 checks passed
@sbailey sbailey deleted the pip_version branch November 18, 2025 18:02
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

Successfully merging this pull request may close these issues.

3 participants