Skip to content
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

Prohibitive sphinx lower bound #260

Closed
ascillitoe opened this issue Sep 27, 2022 · 6 comments
Closed

Prohibitive sphinx lower bound #260

ascillitoe opened this issue Sep 27, 2022 · 6 comments

Comments

@ascillitoe
Copy link

In #258 (and version 1.19.3) the pyproject.toml was updated to contain:

dependencies = ["Sphinx>=5.2.1"]

Does this mean sphinx-autodoc-typehints is now only compatible with the very latest sphinx version? Is there a breaking change in sphinx that necessitates this?

@ascillitoe
Copy link
Author

ascillitoe commented Sep 27, 2022

It seems this restrictive sphinx lower bound was first introduced as Sphinx>=5.1.1 in ccc75d2.

@gaborbernat
Copy link
Member

Does this mean sphinx-autodoc-typehints is now only compatible with the very latest sphinx version? Is there a breaking change in sphinx that necessitates this?

This is the only version we test for, so it make sense to declare requiring this.

@ascillitoe
Copy link
Author

😳

@gaborbernat
Copy link
Member

Why would you not want to use the latest stable release?

@jklaise
Copy link

jklaise commented Sep 27, 2022

In the ideal world we would, but it's not that simple - even now we have some blockers with newer sphinx releases due to latex builds, so we need to pin sphinx until we can resolve it. In the meantime if there are improvements in extensions such as sphinx-autodoc-typehints that are not breaking changes with older sphinx versions then those are most welcome.

I think it's very natural to run on older versions of sphinx for many projects until time allows one to update - I wouldn't be surprised that many projects run sphinx 4.x with sphinx-autodoc-typehints. A restrictive lower bound on a dependency signals that there is some breaking change, but as I understand, it may not be the case here. Lower bounding the requirement to a very recent sphinx version without breaking changes being done or reported just means many projects will keep using 1.19.2 until they can upgrade their sphinx stack, and not benefit from updates to the extension in the meantime.

@gaborbernat
Copy link
Member

gaborbernat commented Sep 27, 2022

The problem that as we add changes we never test with older versions so there's no gurantee at all that an older version of sphinx will work with the latest version of sphinx-autodoc-typehints. If it does work that's a happy happen stance.

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

No branches or pull requests

3 participants