-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
RLS: 0.25.2 #28110
Comments
I don't think we need to wait until then? (the sooner it is already out, the less people will have issues when updating to 3.8) |
Yeah, that's just the deadline. We'll also need to handle building 3.8 binaries after the release. I think that should be doable (just bump the build number on conda-forge when they're ready, and upload only the 3.8 wheels from multibuild). |
shouldn't a bug fix be released with Python-3.8.0rc1 (sept 30th), so that users trying Python-3.8.0rc can look for un-solved bugs only ? |
The earlier the better probably. We need to get things running on our CI first though. |
FYI, @jbrockmendel and I may try to knock out a release this week while we're in town together (likely on Thursday). Ideally we'll be able to get a bit of CI coverage on 3.8 before then. |
is conda-forge any better at 3.8 now? |
No, not yet.
…On Tue, Oct 1, 2019 at 7:23 AM Jeff Reback ***@***.***> wrote:
is conda-forge any better at 3.8 now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28110?email_source=notifications&email_token=AAKAOIRG7Y77BUSFSD2KVEDQMM6LJA5CNFSM4IO6ZMV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEABCHWY#issuecomment-537011163>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIQ5V4BNHC5RYGVMFVLQMM6LJANCNFSM4IO6ZMVQ>
.
|
3.8 is out now. @jbrockmendel are you free to do a release tomorrow? I think the remaining prep work is just to clean up the |
The 0.25.x branch should be almost ready. We have
then I think we're ready. I can't actually do the release this time around. My main laptop is being serviced, and I don't think the machine I'm on can physically run docker. Hopefully @jbrockmendel is able to today (I'll be around to assist). @jbrockmendel can you confirm that you're |
3.8 BinariesIn MacPython/pandas-wheels#64, we're testing our wheel infrastructure on 0.25.x with 3.8. I have two questions
Conda-forge is working on 3.8 packages. Those will likely take a bit longer. |
Yes I think that's not the best idea. @charris is planning to release a Python 3.8 compatible NumPy |
Ah, good to know about the 1.17.3 release. I'll keep my eye on numpy/numpy#14698. We can hold off on releasing 0.25.2 until those are ready. |
@jbrockmendel added to pypi |
OK the 0.25.x branch should be good to go. Will coordinate with @jbrockmendel on releasing. Personally, I'm OK with waiting on NumPy 1.17.3 wheels. We could release 0.25.2 at any time and rebuild wheels for 3.8 when NumPy is ready. But if NumPy is close (next day or two) then it's a tad less work to do it all at once. |
FYI NumPy 1.17.3 wheels (including wheels for Python 3.8) are now available on PyPI. |
Wheels, and conda-forge packages are up (will need to follow up on 3.8 conda packages on conda-forge). Docs are up, sent out the announcements. Something is up with the pdf build: pandas-dev/pandas-release#18 Will get to that eventually. Thanks for running the release @jbrockmendel. |
cc @pandas-dev/pandas-core
Python 3.8 is due on October 21, which will likely beat 1.0.
We should release a 0.25.2 around then that's just 0.25.1 + 3.8 compatibility and regressions from 0.24.x.
The text was updated successfully, but these errors were encountered: