Skip to content

Conversation

@wchargin
Copy link
Contributor

@wchargin wchargin commented Jan 2, 2020

Summary:
A new year, a new dawn. The https://pythonclock.org/ has expired, and
TensorFlow has dropped Python 2 support:
https://groups.google.com/a/tensorflow.org/d/msg/developers/ifEAGK3aPls/jlEuWYObBgAJ

As noted in the above announcement, TensorFlow 2.1.0 will be released
with Python 2.7 support, but we’ve already released the corresponding
TensorBoard 2.1.0, so we no longer need to test with Python 2 at head.

Test Plan:
That CI passes quickly suffices.

wchargin-branch: travis-nopy2

Summary:
A new year, a new dawn. The <https://pythonclock.org/> has expired, and
TensorFlow has dropped Python 2 support:
<https://groups.google.com/a/tensorflow.org/d/msg/developers/ifEAGK3aPls/jlEuWYObBgAJ>

As noted in the above announcement, TensorFlow 2.1.0 will be released
with Python 2.7 support, but we’ve already released the corresponding
TensorBoard 2.1.0, so we no longer need to test with Python 2 at head.

Test Plan:
That CI passes quickly suffices.

wchargin-branch: travis-nopy2
Copy link
Contributor

@caisq caisq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy 2020!

@caisq
Copy link
Contributor

caisq commented Jan 2, 2020

I'm approving this PR based on the following considerations:

  • It'll ease the load on tensorboard's CI on Travis, which is currently pretty slow and puts a hindrance on developer speed.
  • Officially, python2 has reached its EOL.

There might be other constraints that require tensorboard to be python2-compatible for a certain period of time (e.g., 1 year) from now. If such constraints become apparent, we can revisit this.

@wchargin
Copy link
Contributor Author

wchargin commented Jan 2, 2020

Agreed, and note also that the 2.1 release branch still tests against
Python 2.7, so any patch releases will run against 2.7 as well by
default, too. This is already stronger than what TensorFlow promises in
their announcement. Of course, as you note, we can always adjust in
either direction.

@wchargin wchargin merged commit ca4d640 into master Jan 2, 2020
@wchargin wchargin deleted the wchargin-travis-nopy2 branch January 2, 2020 19:09
bileschi pushed a commit to bileschi/tensorboard that referenced this pull request Mar 2, 2020
Summary:
A new year, a new dawn. The <https://pythonclock.org/> has expired, and
TensorFlow has dropped Python 2 support:
<https://groups.google.com/a/tensorflow.org/d/msg/developers/ifEAGK3aPls/jlEuWYObBgAJ>

As noted in the above announcement, TensorFlow 2.1.0 will be released
with Python 2.7 support, but we’ve already released the corresponding
TensorBoard 2.1.0, so we no longer need to test with Python 2 at head.

Test Plan:
That CI passes quickly suffices.

wchargin-branch: travis-nopy2
@bileschi bileschi mentioned this pull request Mar 3, 2020
nfelt pushed a commit that referenced this pull request Mar 4, 2020
Summary:
A new year, a new dawn. The <https://pythonclock.org/> has expired, and
TensorFlow has dropped Python 2 support:
<https://groups.google.com/a/tensorflow.org/d/msg/developers/ifEAGK3aPls/jlEuWYObBgAJ>

As noted in the above announcement, TensorFlow 2.1.0 will be released
with Python 2.7 support, but we’ve already released the corresponding
TensorBoard 2.1.0, so we no longer need to test with Python 2 at head.

Test Plan:
That CI passes quickly suffices.

wchargin-branch: travis-nopy2
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.

3 participants