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

Modernize python support #307

Merged
merged 20 commits into from
Aug 30, 2024
Merged

Modernize python support #307

merged 20 commits into from
Aug 30, 2024

Conversation

tseaver
Copy link
Member

@tseaver tseaver commented May 2, 2024

  • Drop old Python versions (< 3.8), add newer ones (up to 3.12).
  • Remove all the "straddle" compatibility stuff FBO Python 2.7
  • Pin pyramid < 2.0dev, until it can be reviewed in depth.
  • Fix deprecation warnings from pyramid.
  • Silence deprecation warnings related to pkg_resources.
  • Make 'py.test' the testrunner (to support the newer Python versions).
  • Replace cryptacular with plain bcrypt -- the enscons builder that cryptacular needs barfs on Python 3.12.

@tseaver tseaver requested review from mcdonc and cguardia May 2, 2024 23:01
@mcdonc
Copy link
Member

mcdonc commented May 3, 2024

Lol you're nuts.

I'll try to go over it over the weekend or possibly next week, because the last time I tried it with e.g. youshouldsing under Pyramid 2.X, it was very unhappy.

@tseaver
Copy link
Member Author

tseaver commented May 3, 2024

@mcdonc Thanks. Note that this PR doesn't tackle compatibility with Pyramid 2 (it actually adds a pin against it). The Pyramid-induces changes are purely about deprecations, some of which (laughably) have to be removed / redone for Pyramid 2 support.

Test failure tracked in #312
@tseaver tseaver merged commit 37336c8 into master Aug 30, 2024
7 checks passed
@tseaver tseaver deleted the tseaver-modernize_python_support branch August 30, 2024 15:42
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.

2 participants