Open heckad opened 9 months ago
Thank you for this report. I admit that some skeleton downstream projects are not that much associated with version-specific language features, and thus may be relaxed to allow yet unstable versions of the language. The issue should be addressed at the infrastructure level in the project skeleton, and the fix should be applied among all downstream projects, including this one.
This will be fixed in v1.0.0, a release that enters into semver and primarily values stability.
As a workaround for the installation problem now, you might want to either (1) set your Python version in [tool.poetry.dependencies]
to never exceed the latest Python 3.12, e.g. python = ">=3.8,<3.13"
or (2) in [tool.poetry.dependencies]
, add the line proxyvars = { version = "^0.9.1", python = ">=3.8,<3.13" }
to only install proxyvars
on Python <3.13. The latter option will break your project Python 3.13+ provided proxyvars
is its hard dependency, so I would recommend the first one until a fix in the proxyvars
metadata is released.
As I can see, the Python spec is incorrectly set to <=3.12
which I think only allows 3.12.0
as a maximum version.
Making a quick release to set it to <3.13
. It was fixed in other projects, this one remained.
v0.9.2 released. The suggested temporary workarounds should work. Please hang on until a ready-for-production v1.0.0 is released, and the >=3.8,<4.0
range will be allowed!
v1.0.0 should come out in April.