-
-
Notifications
You must be signed in to change notification settings - Fork 18.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
COMPAT: broken pickle compat from 0.19.2 -> 0.20.2 for UTC tz's #16608
Labels
Milestone
Comments
@jorisvandenbossche @TomAugspurger any objection to doing a 0.20.3 in a few weeks? |
jreback
added a commit
to jreback/pandas
that referenced
this issue
Jun 6, 2017
jreback
added a commit
to jreback/pandas
that referenced
this issue
Jun 6, 2017
No objection. I would just start tagging stuff as 0.20.3 and make a 0.20.3 whatsnew file. If we in the end decide that we don't find it worth to release (which probably will not be the case), we can easily move those things to 0.21 (it's just moving the whatsnew entries). |
Fine by me as well.
…On Tue, Jun 6, 2017 at 6:31 AM, Joris Van den Bossche < ***@***.***> wrote:
No objection. I would just start tagging stuff as 0.20.3 and make a 0.20.3
whatsnew file. If we in the end decide that we don't find it worth to
release (which probably will not be the case), we can easily move those
things to 0.21 (it's just moving the whatsnew entries).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16608 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIpF5mN22fVlSwZLzp3LEBMzjd61Oks5sBTiPgaJpZM4NwpDq>
.
|
jreback
added a commit
that referenced
this issue
Jun 6, 2017
Kiv
pushed a commit
to Kiv/pandas
that referenced
this issue
Jun 11, 2017
stangirala
pushed a commit
to stangirala/pandas
that referenced
this issue
Jun 11, 2017
TomAugspurger
pushed a commit
to TomAugspurger/pandas
that referenced
this issue
Jul 6, 2017
closes pandas-dev#16608 (cherry picked from commit 697d026)
TomAugspurger
pushed a commit
that referenced
this issue
Jul 7, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
broken in 0.20.1/2
works fine for tz-aware but non-UTC (e.g. US/Eastern is fine).
The text was updated successfully, but these errors were encountered: