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

move to python 3.8+ #834

Closed
wants to merge 4 commits into from
Closed

Conversation

danieleades
Copy link
Contributor

sphinx 6.0 beta is out, and drops support for python <3.8.
sphinx-needs can follow suit (once the stable release is out)

@danwos
Copy link
Member

danwos commented Aug 4, 2023

I would like to close this PR, as it seems to outdated.
Any concerns?

@chrisjsewell
Copy link
Member

I would like to close this PR, as it seems to outdated. Any concerns?

@danwos to bump to new versions of sphinx, this would still be required. Python 3.7 is also end-of-life: https://devguide.python.org/versions/

What are your thoughts on bumping python/sphinx versions? Speaking with @ubmarco he suggested that we are less "aggressive" on bumping versions, since some businesses have to deal with older versions of Python?

@ubmarco
Copy link
Member

ubmarco commented Oct 12, 2023

We also have the Compatibility with Sphinx 7.2 PR now.
It contains new version constraints and remarks wrt API incompatibilities.
Support for Sphinx < 7.2 with one version of sphinx-needs will require a lot of code branches to make all Sphinx versions happy.

@chrisjsewell
Copy link
Member

superceded by #1056

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

Successfully merging this pull request may close these issues.

4 participants