-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BLD: support 3.8 pre #27266
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
BLD: support 3.8 pre #27266
Conversation
this is not working yet :-< https://travis-ci.org/pandas-dev/pandas/jobs/555081822
any ideas here @mattip |
I think you need to add |
You are building NumPy since NumPy does not yet provide a wheel for python3.8, and somehow the build script is not adding that flag. NumPy seems to be adding it into the CI configurations. This might be a bug in the way I cannot reproduce on python3.7 (ubuntu 18.04), in a clean virtualenv this works with no error
|
interesting, is there any way to force this on pip? |
Can you try this in a clean python 3.8 virtualenv?
|
I tried this exactly on macosx and it fails as well (was using the conda install via the pre channel for python & pip; cython from source) e.g. I was always doing |
Maybe we only set the flag automatically for gcc (I assume you are using clang)? What happens if you
You should see the flag appear in the compile flags in the call to the compiler |
Anything left to do here? |
numpy is not installing correctly yet. |
Steps I took to reproduce, these succeeded for me on x86-64 Ubuntu 18.04
|
@TomAugspurger didnt you recently have a PR that was 3.8-specific? Does that make this either easy or redundant? |
That was only tested against 3.8 locally. We would ideally have a 3.8 build
on CI before release 0.25.2.
I think we'll need to wait for 3.8b4, otherwise we'll have segfaults from
https://bugs.python.org/issue37915.
…On Wed, Aug 28, 2019 at 11:51 AM jbrockmendel ***@***.***> wrote:
@TomAugspurger <https://github.com/TomAugspurger> didnt you recently have
a PR that was 3.8-specific? Does that make this either easy or redundant?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27266?email_source=notifications&email_token=AAKAOITU2LX5THWB4IAWHKDQG2UKNA5CNFSM4H6T6ZDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5LYOKY#issuecomment-525829931>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIXVP3ISU2CSP4KNY3DQG2UKNANCNFSM4H6T6ZDA>
.
|
|
Not really. We use conda on CI.
Travis already provided a python-dev base environment. If anyone wants to,
we'd probably be OK with a PR that added
a new entry on travis using 3.8 from travis and compiling NumPy from source
as a stopgap until conda packages are
ready for 3.8.
…On Mon, Sep 16, 2019 at 12:00 PM jbrockmendel ***@***.***> wrote:
I think we'll need to wait for 3.8b4
pyenv install 3.8-dev now installs 3.8b4. Does that un-block this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27266?email_source=notifications&email_token=AAKAOITOR5WDEISO6O3TJWLQJ63SHA5CNFSM4H6T6ZDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Z2A4I#issuecomment-531865713>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIRXAWF3YNEF7X4XQKTQJ63SHANCNFSM4H6T6ZDA>
.
|
looks like @jbrockmendel is working on this now. |
closes #26626