Open deronnax opened 6 months ago
This forces users to enable pre-releases when resolving dependencies, for example:
× No solution found when resolving dependencies:
╰─▶ Because only dparse<0.6.4b0 is available and safety>=3.0.0 depends on dparse>=0.6.4b0, we can conclude that safety>=3.0.0 cannot be used.
And because only the following versions of safety are available:
safety<=3.0.0
safety==3.0.1
safety==3.1.0
safety==3.2.0
and mkdocs-autorefs depends on safety>=3.0, we can conclude that the requirements are unsatisfiable.
hint: dparse was requested with a pre-release marker (e.g., dparse>=0.6.4b0), but pre-releases weren't enabled (try: `--prerelease=allow`)
Opting into pre-releases would allow them in the whole dependency graph, not just for dparse, so that's not really something I'd want to do :thinking:
Any blockers for going from a beta release to a final release :slightly_smiling_face:?
@pawamoy had the same issue, fixed it by adding the dparse
pre release version to the dependancies. then you can do the rye sync
without --pre
[tool.rye]
managed = true
dev-dependencies = [
...,
"dparse>=0.6.4b0",
"safety>=3.2.3"
]
it's been 8,5 months since the last non-beta release. Also, none of the current release runs on python 3.12 because older dparse releases use
ConfigParser.readfp()
which is removed in Python 3.12.