-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with Towncrier 24.7 #92
Comments
This issue also affecting pypa/setuptools#4533. |
Pin `towncrier` until we find a solution to sphinx-contrib/sphinxcontrib-towncrier#92.
Thanks for notifying me! |
Pin `towncrier` until we find a solution to sphinx-contrib/sphinxcontrib-towncrier#92.
sphinxcontrib-towncrier is incompatible with towncrier 24.7 (sphinx-contrib/sphinxcontrib-towncrier#92)
- Bump PORTREVISION for package change textproc/py-towncrier has been updated to 24.7.1 in 4bd3073. However towncrier 24.7+ is incompatible with sphinxcontrib-towncrier. Therefore, it causes build failure when DOCS option is enabled. Reference: https://pkg-status.freebsd.org/package19/data/140amd64-default-build-as-user/39a5c2d0b3e6/logs/py311-pip-23.3.2_1.log sphinx-contrib/sphinxcontrib-towncrier#92 PR: 280570
- Bump PORTREVISION for package change Change py-sphinxcontrib-towncrier and this port from incompatible py-towncrier to compatible py-towncrier23. Therefore, DOCS can be enabled again. Reference: sphinx-contrib/sphinxcontrib-towncrier#92 PR: 280570
Would it be possible to create a release which limits the version of the towncrier dependency? |
- Temporarly disable DOCS option due to the conflit between the docs build-dependency textproc/py-towncrier with textproc/py-towncrier23, which the other dependency py-sphinxcontrib-towncrier now depends on. I prefer to disable this option instead of changing the dependency to py-towncrier23 because a user may have already installed py-towncrier in the system for other reasons before updating. Other reference: sphinx-contrib/sphinxcontrib-towncrier#92 - Bump PORTREVISION PR: 280687
@commonism it'd be pointless as pip's depresolver would just backtrack to the previous version. |
Pip does not do that |
I can assure you, with my PyPA hat on, that pip's dependency resolver ( |
If Of course, things may be more complicated if some other package passed to |
That's it. You still have to manually constrain the user request on what to install. But if you don't — backtracking happens. That said, I don't see how this would be different with or without a release just bumping the metadata. When I find time to work on this, I won't be looking into trivial stop-gaps and will just fix the incompatibility 🤷♂️ It doesn't make sense to me to spend that time twice. |
- Temporarly disable DOCS option due to the conflit between the docs build-dependency textproc/py-towncrier with textproc/py-towncrier23, which the other dependency py-sphinxcontrib-towncrier now depends on. I prefer to disable this option instead of changing the dependency to py-towncrier23 because a user may have already installed py-towncrier in the system for other reasons before updating. Other reference: sphinx-contrib/sphinxcontrib-towncrier#92 - Bump PORTREVISION PR: 280687
updates: - [github.com/astral-sh/ruff-pre-commit: v0.6.1 → v0.6.2](astral-sh/ruff-pre-commit@v0.6.1...v0.6.2) - [github.com/pre-commit/mirrors-mypy: v1.11.1 → v1.11.2](pre-commit/mirrors-mypy@v1.11.1...v1.11.2) * Fix sphinx with a more robust fix Until sphinx-contrib/sphinxcontrib-towncrier#92 is resolved. Co-authored-by: Pierre Sassoulas <[email protected]>
updates: - [github.com/astral-sh/ruff-pre-commit: v0.6.1 → v0.6.2](astral-sh/ruff-pre-commit@v0.6.1...v0.6.2) - [github.com/pre-commit/mirrors-mypy: v1.11.1 → v1.11.2](pre-commit/mirrors-mypy@v1.11.1...v1.11.2) * Fix sphinx with a more robust fix Until sphinx-contrib/sphinxcontrib-towncrier#92 is resolved. Co-authored-by: Pierre Sassoulas <[email protected]>
@webknjaz I was just about to offer some help on fixing this issue but it looks like you have something planned for tomorrow already :-) There are basically then three pathways based on the version of Towncrier:
The main question is how to distinguish pathway 1 from 2: checking for the current TypeError is not ideal because if another parameter is added to the new Happy to put together a PR if that would be helpful, just let me know your thoughts. |
@bennyrowland well, I added it on the board of the aiohttp sprint because it's used in the infra and it would be nice to have. IIRC I was trying hard to keep Python 3.6 support for one final release and was planning to drop all EOL versions right after, shrinking the matrix by a lot. But I didn't take into account some bits of this repos infra and broke it. Never had time to pick it up. |
Looks like the just-released Towncrier 24.7 has broken some API you're using:
See https://github.com/python-attrs/attrs/actions/runs/10176118290/job/28144823882#step:6:29 for full CI failure.
The text was updated successfully, but these errors were encountered: