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.

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

Drop Python 3.8 support, require 3.9+ #259

Merged
merged 1 commit into from Apr 19, 2023
Merged

Drop Python 3.8 support, require 3.9+ #259

merged 1 commit into from Apr 19, 2023

Conversation

EwoutH
Copy link
Collaborator

@EwoutH EwoutH commented Apr 19, 2023

Following NEP 29 Python 3.8 support is dropped for future minor and major releases, and will require Python 3.9+ from version 2.5.0 onwards.

The freshly released EMAworkbench 2.4.0 will support Python 3.8, as 2.4.x. patch releases.

The docs, readme, changelog, CI config and Pyupgrade are also updated.

Following NEP 29 Python 3.8 support is dropped for future minor and major releases, and will require Python 3.9+ from version 2.5.0 onwards.

The freshly released EMAworkbench 2.4.0 will support Python 3.8, as 2.4.x. patch releases.
@quaquel quaquel merged commit 33bf8e9 into master Apr 19, 2023
17 of 18 checks passed
@coveralls
Copy link

Coverage Status

Coverage: 81.097%. Remained the same when pulling 491f101 on python-3.9-plus into 9a0e5e2 on master.

@EwoutH
Copy link
Collaborator Author

EwoutH commented Apr 19, 2023

For future reference, a small note on DelftBlue (the TU Delft supercomputer) compatibility: The current 2022r2 software stack has Python 3.8 installed. You can either use the EMAworkbench 2.4.x, which supports Python 3.8, or create a Conda env with a newer Python version.

This problem will also resolve itself, since in the next software stack a Python upgrade is planned (which can be tracked here).

@quaquel quaquel deleted the python-3.9-plus branch November 18, 2023 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants