-
Notifications
You must be signed in to change notification settings - Fork 209
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
Update to python 3.0 compliance #1047
Comments
Python has a 2_to_3 script that should take care of most of it. It would be a matter of running the script, pylinting the result, and running our tests. Hopefully it would mostly just work. |
Sounds good but lets not make this a priority. 2020 is a while from now and 2.7 won't disappear over night. |
I agree with Rob's plan.
…On Thu, Jan 26, 2017 at 10:07 AM, Robert Jacob ***@***.***> wrote:
Sounds good but lets not make this a priority. 2020 is a while from now
and 2.7 won't disappear over night.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1047 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHlxE8dIOVhq938o6pcU_xbhCFDKkTZ4ks5rWNLGgaJpZM4LuLYA>
.
|
Yes, and even then, 2.7 will never disappear. They just won't release any further updates to it. |
For the future, as a Python 3 evangelist, I would like to work on this |
End of life for python 2.7 is 2020. What needs to be done to update cime to python 3?
The text was updated successfully, but these errors were encountered: