Closed boxydog closed 8 months ago
After merging this, the next step would be to start uncommenting the ruff rules and letting it fix them, or fixing them manually if need be. pyupgrade and django-upgrade also very helpful.
This will change hundreds of lines of code in shallow ways to be closer to python 3 best practices. For example, using foo.a
instead of getattr(foo, "a")
.
Again, personally I would squash-commit all PRs, but it's your project.
FYI, this passed: https://github.com/boxydog/askbot-devel/actions. Not sure why it doesn't show up on the PR. Different repo, I guess.
@boxydog I'll be reviewing these Fri-Mon, but possibly earlier. Thank you!
Note with this new pyproject.toml, it works to replace the deprecated python setup.py install
with python -m pip install .
. See also https://packaging.python.org/en/latest/discussions/setup-py-deprecated/#setup-py-deprecated.
Also, you can use pip-compile
to create a real requirements.txt
with all requirements pinned.
Also run it in the github tests.