-
Notifications
You must be signed in to change notification settings - Fork 24
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 #59
Conversation
This revision bump backports parts of the upstream PR gentoo#59 related to nose to pytest transition. Additionally, py3.11 support is enabled. Upstream-PR: ecordell/pymacaroons#59 Signed-off-by: Petr Vaněk <[email protected]>
Only parts related to nose to pytest transition are backported. Backported-from: ecordell#59
This revision bump applies patch which backports parts of the upstream PR gentoo#59 related to nose to pytest transition. Additionally, py3.11 support is enabled. Upstream-PR: ecordell/pymacaroons#59 Signed-off-by: Petr Vaněk <[email protected]>
This revision bump applies patch which backports parts of the upstream PR gentoo#59 related to nose to pytest transition. Additionally: - py3.11 support is enabled - update DESCRIPTION Upstream-PR: ecordell/pymacaroons#59 Co-authored-by: Michał Górny <[email protected]> Signed-off-by: Petr Vaněk <[email protected]>
This revision bump applies patch which backports parts of the upstream PR gentoo#59 related to nose to pytest transition. Additionally: - py3.11 support is enabled - update DESCRIPTION Upstream-PR: ecordell/pymacaroons#59 Co-authored-by: Michał Górny <[email protected]> Signed-off-by: Petr Vaněk <[email protected]>
This revision bump applies patch which backports parts of the upstream PR #59 related to nose to pytest transition. Additionally: - py3.11 support is enabled - update DESCRIPTION Upstream-PR: ecordell/pymacaroons#59 Co-authored-by: Michał Górny <[email protected]> Signed-off-by: Petr Vaněk <[email protected]> Closes: #28022 Signed-off-by: Michał Górny <[email protected]>
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.
Thank you!
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.
Thanks for picking this up!
This looks good to me, if we find any issues after merging we can can fix them afterwards (GHA changes sometimes take a couple of tries).
push: | ||
pull_request: | ||
schedule: | ||
- cron: '0 12 * * 0' # run once a week on Sunday |
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.
why run once a week if there have been no changes?
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.
Because of #60 - my PR was green a year ago when I created it, but there will be changes which break CI, e.g. updated dependencies, transitive dependencies or updated system packages / os. It is just a best practice to run CI jobs weekly to fix such breakages in a timely manner, and not e.g. when one needs to fix an urgent security issue.
This is a first start.
hypothesis
which needs some tests to be rewrittenhypothesis
to the latest compatible versionAlso see discussion at #58
Given this PR gets merged, there should be follow-up PRs with adding back coverage report and adding support for Python 3.10 and possibly for dropping support for obsolete Python versions.