-
Notifications
You must be signed in to change notification settings - Fork 2
Set up Github Actions #1
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
Conversation
mgax
commented
Oct 8, 2024
- Update the Readme with syntax highlighting.
- Update PyPI links.
- Set up CI and publishing actions.
tox.ini
Outdated
| py39-django42-wagtail62 | ||
| py{39,310,311,312}-django42-wagtail62 | ||
| py{310,311,312}-django{50,51}-wagtail62 | ||
| py312-django42-wagtail{52,60,61,62} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
drive-by suggestion
| py312-django42-wagtail{52,60,61,62} | |
| py312-django42-wagtail{52,62} |
since 6.0 and 6.1 are no longer officially supported
other than that, I would take a more opinionated stance and do Python 3.11+ (but that is only me)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good call about Wagtail versions, thanks!
I'm not sure about only supporting Python 3.11+ though. In general, I agree with the sentiment, but I can imagine somebody jumping in to rescue a legacy project, and hoping to pull the production database, without doing a major upgrade beforehand. It's a simple package, and doesn't cost us much to support older Pythons (aside from some CI time).
zerolab
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few suggestions that can be addressed as a follow up.
Thanks @mgax