Had a broken pipeline caused by this exact practice of pinning the upper range of Python (in my case, to <3.13
) in requires-python
- the dependency was Numpy, and I was using PDM to install the project dependencies in a container.
What caused confusion was that this pinning appeared to be done on a release branch, while the main project TOML had no such pinning. I had to apply the same pin to my project’s requires-python
in order for the PDM install to work in the pipelines.
I can remove this pin, but I’ve left it in place out of safety, but I’m surprised by how easily such failures can be triggered.