Skip to content
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

Drop python 2 support #2554

Closed
jasongrout opened this issue Sep 7, 2019 · 2 comments
Closed

Drop python 2 support #2554

jasongrout opened this issue Sep 7, 2019 · 2 comments
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@jasongrout
Copy link
Member

jasongrout commented Sep 7, 2019

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.

@jasongrout jasongrout added this to the 8.0 milestone Sep 7, 2019
@vidartf
Copy link
Member

vidartf commented Sep 8, 2019

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.

@hugovk
Copy link
Contributor

hugovk commented Sep 11, 2019

Please see PR #2558 to take care of some of this.

@vidartf vidartf closed this as completed Jan 7, 2020
@lock lock bot added the resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label May 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

3 participants