-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 support for Python 3.8 #12720
Drop support for Python 3.8 #12720
Conversation
Codecov Report
@@ Coverage Diff @@
## branch-3.2 #12720 +/- ##
===========================================
Coverage 92.36% 92.36%
===========================================
Files 315 315
Lines 19962 19962
===========================================
Hits 18437 18437
Misses 1525 1525 |
It does not make sense to me to drop support right before a minor release. If the release is imminent, then we can just endure the short wait, to give users the benefit of increased options, and remove right after the release. cc @bokeh/core |
I'm +1 on waiting until after 3.1. With my Panel hat on I'd prefer to support Python 3.7 in Panel 1.0 and then drop it immediately thereafter and since Panel 1.0 will pin to bokeh 3.1 that would make it impossible. |
3fa9999
to
0d4f100
Compare
66d40cf
to
aedad6e
Compare
aedad6e
to
c9e6b01
Compare
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is about two weeks earlier than BEP 9 stipulates, but it will be fulfilled by the time 3.1 is released. In the meantime, this will reduce CI test time by a considerable margin (testing another Python version is about 50~60 minutes cumulative).