-
Notifications
You must be signed in to change notification settings - Fork 0
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
Pandas27 Release v0.24.3 #1
base: 0.24.x
Are you sure you want to change the base?
Conversation
…numpy previously installed. Affects Python 2.7 installs, and could install incorrect version in Python 3 installs as well. Also added build script for building pip wheels
Hi there (posting here since there aren't issues). On the pydata mailing list, there's some confusion about whether this is an "official" release of pandas: https://groups.google.com/forum/#!search/pydata/pydata/KGpSHxiR4Rc/aII9R5kEBgAJ Could you update a few things to indicate that this package isn't from the pandas team?
Thanks! |
Hi, This fork was only necessary because of a bug that wasn't addressed on: This fix was intended for an organization I work with, but we ended up changing our development workflow to accommodate the bug rather than use this package. Thanks for the heads up on the confusion, I thought it was evident enough in pypi since the "Maintainer" field lists my name out beside it. It appears I cannot easily change the package description, so I will have to just delete the pypi release. Its a shame really, I managed to create a workflow to build the binaries for pandas automatically and it took nearly a day to finish compiling them all. I will leave this GitHub fork active in case anyone comes across an issue using pandas with python 2.7 Thanks, |
You can make a new release with an updated description, right?
…On Sat, Sep 7, 2019 at 6:44 PM Spencer Callicott ***@***.***> wrote:
Hi,
This fork was only necessary because of a bug that wasn't addressed on:
Issue 27435 <pandas-dev#27435>
This fix was intended for an organization I work with, but we ended up
changing our development workflow to accommodate the bug rather than use
this package. Thanks for the heads up on the confusion, I thought it was
evident enough in pypi since the "Maintainer" field lists my name out
beside it.
It appears I cannot easily change the package description
<pypi/warehouse#2170>, so I will have to just
delete the pypi release. Its a shame really, I managed to create a workflow
to build the binaries for pandas automatically and it took nearly a day to
finish compiling them all.
I will leave this GitHub fork active in case anyone comes across an issue
using pandas with python 2.7
Thanks,
Tuxprogrammer
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AAKAOITE7JJIK2FWKK3GA43QIQ4F7A5CNFSM4IRPSVE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FEL4Y#issuecomment-529155571>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIWHCZFV3KNKQW6LWKDQIQ4F7ANCNFSM4IRPSVEQ>
.
|
@Tuxprogrammer would you be interested in doing this patch as a PR to pandas? In that case we would consider backporting it and releasing as 0.24.3 |
This is only here to compare the edits made from v0.24.2 to 0.24.3