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
Python 2 has end-of-life on January 1, 2020. Accordingly, a few of us feel that we should make an 8.0 ipywidgets release that moves to Python 3 only before then.
The text was updated successfully, but these errors were encountered:
I agree. Let's use this issue as a tracker for things to refactor as a part of that switch. E.g. "change this API to use async generator"; "change this internal code to cleanup bytestring/unicode use", etc.
lockbot
added
the
resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
label
May 21, 2020
lockbot
locked as resolved and limited conversation to collaborators
May 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
resolved-lockedClosed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Python 2 has end-of-life on January 1, 2020. Accordingly, a few of us feel that we should make an 8.0 ipywidgets release that moves to Python 3 only before then.
The text was updated successfully, but these errors were encountered: