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.

Sign up for GitHub

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

Jump to bottom

Go through the code looking for improvements that can be made when abandoning Python 2.x. #46

Open
4 tasks
Tracked by #27
CSchoel opened this issue Aug 10, 2024 · 0 comments
Open
4 tasks
Tracked by #27

Go through the code looking for improvements that can be made when abandoning Python 2.x. #46

CSchoel opened this issue Aug 10, 2024 · 0 comments
Assignees
@CSchoel
Milestone
Release nolds 1.0

Comments

@CSchoel
Copy link
Owner

CSchoel commented Aug 10, 2024 •
edited
Loading

By dropping support for Python 2.x, we can modernize the codebase and get rid of from __future__ import and other hacks.

  • Check where we do from __future__ import, removing all those instances and simplifying the codebase accordingly.
  • Run pyupgrade over the codebase.
  • Check with Ruff if there are any outdated parts in the codebase left.
  • Check that the unit tests still run after all changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CSchoel CSchoel

Labels
None yet
Projects
None yet
Milestone
Release nolds 1.0
Development

No branches or pull requests
1 participant
@CSchoel