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 support for Python 2.7, and <3.7 ? #960

Closed
MichaelClerx opened this issue Jun 5, 2023 · 3 comments · Fixed by #980
Closed

Drop support for Python 2.7, and <3.7 ? #960

MichaelClerx opened this issue Jun 5, 2023 · 3 comments · Fixed by #980
Labels
code Code and infrastructure issues compatibility OS and Python version issues

Comments

@MichaelClerx
Copy link
Member

Testing is being dropped (again): actions/setup-python#672

Upgrading 3 is easy, using virtual environments is getting popular on systems where users don't have full control, so might as well go straight for 3.7 then?

@MichaelClerx MichaelClerx added the compatibility OS and Python version issues label Jun 5, 2023
@MichaelClerx
Copy link
Member Author

MichaelClerx commented Jun 5, 2023

Stuff that might be nice for Myokit:

  • 3.0
    • No more from __future__
    • New style constructors (super(), and no (object) after every class)
    • No more basestring and needing to think about bytes when handling strings (less of it, anyway)
    • keyword-only arguments
    • exception chaining (raise from), and easier access to tracebacks
  • 3.4
    • enums
    • pathlib
  • 3.5
    • os.scandir
  • 3.6
    • f-strings
  • 3.7
    • Ordinary dict is now ordered (by definition, not as an implementation detail)

@MichaelClerx
Copy link
Member Author

But the bigger benefit would just be less clunky code and less testing

@MichaelClerx MichaelClerx added the code Code and infrastructure issues label Jun 5, 2023
@MichaelClerx MichaelClerx changed the title Drop support for Python 2.7, and <3.7 Drop support for Python 2.7, and <3.7 ? Jun 5, 2023
@MichaelClerx
Copy link
Member Author

At the same time, it's not a lot of work maintaining 2.7 right now. Github might go back on their decision (again), or an easy docker fix or something might show up...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code Code and infrastructure issues compatibility OS and Python version issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant