-
-
Notifications
You must be signed in to change notification settings - Fork 536
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
Python2 compatibility #225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm glad there weren't more changes needed, if we haven't been running python2 tests!!!
84eecee
to
be3296d
Compare
Bit premature but I think I've got it now. |
Devil's advocate here. Was this really necessary? Xarray just merged a PR to remove py2 compat ;-) |
After going through all the effort I'd be very tempted to say no, but we'll probably drop py2 compatibility for all projects at the same time. |
Related: https://twitter.com/mrocklin/status/1083889299211223040 "Here's a new one. The Dask-Kubernetes subproject just accepted a patch to support Python 2 (Dask's Kubernetes was Python 3 only), then cut a release, and immediately dropped Python 2 again." |
Panel replaces ParamNB and ParamBokeh, which both supported Python2, and I don't want people ever to have any reason to turn to those older projects. When we drop Python2 support in Panel (which we will!), we can now safely point people who are stuck on py2 to use an older Panel release, rather than having them pointlessly invest in ParamNB or ParamBokeh. |
No description provided.