-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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
DOC: Plans for 2.7 #20540
DOC: Plans for 2.7 #20540
Conversation
Do we need to send a notice about this to the pydata/pandas-dev mailing list to give people the chance to give feedback? |
Codecov Report
@@ Coverage Diff @@
## master #20540 +/- ##
==========================================
+ Coverage 91.81% 91.84% +0.02%
==========================================
Files 152 152
Lines 49259 49259
==========================================
+ Hits 45229 45241 +12
+ Misses 4030 4018 -12
Continue to review full report at Codecov.
|
lgtm this i already promise enough (maybe even too much) merge away |
doc/source/install.rst
Outdated
Starting **January 1, 2019**, all major release will be Python 3 only. | ||
|
||
Starting **January 1, 2020**, the pandas maintainers will stop supporting Python 2. The released packages will still be | ||
available on PyPI and through conda, but will not recieve any more bugfixes. |
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.
minor typo: recieve --> receive
Sure, are we comfortable with the proposal and timeline? Personally, I'm not sure how much backporting we can commit to doing over 2019. Is there any benefit to being ahead of NumPy here, by a bit, since they're a dependency? |
[ci skip]
actually I don't think we should commit to a LTS release at all. The final release of 2.7 is Dec 31, 2018. |
Updated the text about 2.7 support after December 31, 2018 to reflect the default of "we're done with 2.7. If someone wants to continue supporting it, let us know." |
lgtm. @jorisvandenbossche |
we also need to remember to keep this warning in here for each release |
I'll send out a note to the mailing list.
…On Fri, Mar 30, 2018 at 3:06 PM, Jeff Reback ***@***.***> wrote:
we also need to remember to keep this warning in here for each release
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20540 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIhOYt3HXO8QJQRY_hwDo58Uu_Hqbks5tjpBIgaJpZM4TA3lh>
.
|
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.
that sounds reasonable time line
thanks @TomAugspurger |
The link in the whatsnew warning doesn't work: http://pandas-docs.github.io/pandas-docs-travis/whatsnew.html |
I've created a PR to http://www.python3statement.org to add pandas to the timeline: |
Closes #18894
Just some sample text, essentially following NumPy.
Of course, it'd be nice if 1.0 happened to be the LTS, but we'll see.