-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Updated continuous integration #38
Conversation
Should we just drop |
CI disabled. Gonna close/reopen to trigger it. |
1b09785
to
c0a3bda
Compare
@pllim - I don't think we need to drop any pytest versions at this point, think it should all work |
You wanna be adventurous and have pytestdev use Python 3.12? 😅 |
Does Python 3.12 work with the openastronomy workflows? |
I have no idea. I just know @bsipocz added a Python 3.12 job for pytest-doctestplus (and I don't have time to check right now). |
@pllim lets just merge this for now if you are happy with it and I can investigate separately? |
- macos: py310-test-pytest73 | ||
- windows: py311-test-pytest74 | ||
- linux: py311-test-pytestdev | ||
publish: |
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.
What does this mean? Can we still use the "Build wheels" label on PRs here?
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.
The wheels are always built in PRs with this config. It's so fast there's no point making it optional.
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.
Wheels will always be built but only published to PyPI on a tag
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.
OK so after we have merged this, we should delete that "Build wheels" label.
This drops Python 3.7 testing without dropping Python 3.7 support. Should we just drop 3.7 completely? Line 30 in e006ea1
|
Oops yes meant to update setup.cfg |
IMO, do one last release before dropping 3.7, that's what we did elsewhere. Or is it hopelessly incompatible already? |
Re py3.12: there wasn't any big issues, but this one fix was needed, which may or may not effect this plugin: scientific-python/pytest-doctestplus#215 |
Can add back python 3.7, not a problem! |
I've added back Python 3.7, hopefully this should still pass |
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.
LGTM but I'll let Brigitta have a look too. Thanks!
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.
Versions certainly need to be updated, but I don't see why relying on a middle layer makes sense for these super simple plugins.
.github/workflows/ci_workflows.yml
Outdated
uses: OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml@v1 | ||
with: | ||
envs: | | ||
- linux: py37-test-pytest46 |
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.
Somewhat unrelated improvement: instead of pytest46
I like to call it pytestoldest
, and pin it to the actual stated minimum version rather than a wildcard in that series. E.g. pytest==4.6.0
If a fix is needed from an actual bugfix, then bump the minimum version to reflect that.
(for the rest of the versions I feel the flexible wildcard is fine, we need a wide enough matrix to cover over versions but don't need to test everything).
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.
Sounds good, will do
Oh, and I can repeat what @pllim said above, please add py3.12 testing (can be done separately, but it's really time to make stuff compatible if it's not yet) |
FWIW, I opened: |
5d96746
to
18be9b8
Compare
3abe6e9
to
c745a36
Compare
I don't think you can pull astropy or tables for py312. You also have to pull in pandas dev. Lines 37 to 41 in e006ea1
|
Hmm at the moment astropy is a required dependency for the test suite. Rather than re-write everything maybe we can just wait? |
Simplified publish workflow Make publish job dependent on tests Add back Python 3.7 Rename pytest46 to pytestoldest and add Python 3.12 testing Use latest developer version of Numpy and pytest for Python 3.12 Co-authored-by: P. L. Lim <[email protected]>
25b0076
to
98e772b
Compare
across the board and add the codestyle check. Fix PEP 8 complaints. Auto-cancel duplicate Action jobs.
d8a4e31
to
beba1cb
Compare
Handle FutureWarning from pandas 3.0 Skip failing pandas test caused by numpy 2.0 Updated matrix to run a stable job in py312
Gonna merge and then do a release. 🤞 |
Just simplifying the CI and adding recent versions of pytest
Fix #39