You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
In general I like the idea of moving to python 3.6. I see two problems however:
People on Debian (or Ubuntu, etc. ) will not update to 3.6 until the new distribution release is made. This would require those developers to manually install the new update. I don't see this as a big problem, but something to consider nontheless.
The new features are great, but we need to make sure we are actually using them. Just taking the format strings as an example, is there a tool that automatically checks that we are not using "%s" instead?
Given that we are having trouble finding people to help us on the project as it currently stands, requiring our developers to manually update to Python 3.6 might scare them away. Otherwise I say, go ahead!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since Python 3.6 is out and brings a bunch of nice features incl. but not limited to formatted strings, kwarg order preservation, private version in dicts, Asynchronous generators, new module for cryptographic purposes, MUCH saner variable annotation syntax and a bunch of other changes that you can check here.
I'd like to start a discussion about us moving to Python3.6.
The text was updated successfully, but these errors were encountered: