-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Vote] Deprecate Python2 Support #2994
Comments
Ah finally! So much +1 |
+1
… On Apr 9, 2019, at 10:14 AM, Nick Hynes ***@***.***> wrote:
Ah finally! So much +1
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#2994 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFsp2B9pij56A9ZpgK1qijf1F7UQOe1kks5vfMpogaJpZM4ck_Vd>.
|
+1 |
+1. We (The relay crew) often find not having py3 features(fstring, keword only argument, type annotation, nonlocal) inconvenient. Can we get it to 3.6? fstring(3.6 feature) is used heavily in the relay ahead of time compiler that will be opensourced soon. |
+1, I think we agreed on python3.5 support to be safe because many users' system still only have 3.5 installed. For new features, we can depend on 3.6 if it is isolated enough. |
+1 |
7 similar comments
+1 |
+1 |
+1 |
👍 |
+1 |
+1 |
+1 |
Python2 is deprecated in #2986. We may also send a PR to https://python3statement.org/ |
Let us keep the vote open for a week. |
As we discussed in #2715, most of us agree with switch to Python3 starts with 0.6 release. I want to start a vote to deprecate Python2 support & test in our current master branch.
@dmlc/tvm-committer
The text was updated successfully, but these errors were encountered: