-
-
Notifications
You must be signed in to change notification settings - Fork 36
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 1.1.0rc0 #84
Rls 1.1.0rc0 #84
Conversation
…da-forge-pinning 2020.07.17.17.28.25
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
Documentation on acceptable licenses can be found here. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hmm, we seem to be running into pandas-dev/pandas#33315 / pandas-dev/pandas#33314. I'm not sure what's best here, but I'm leaning towards patching the setup.py to ignore errors on OSX?
|
recipe/meta.yaml
Outdated
- cython >=0.28.2 | ||
- numpy | ||
- cython >=0.29.16 | ||
- numpy >=1.15.4 |
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.
Pin exact here to get the oldest possible numpy version.
@conda-forge-admin, please rerender |
…da-forge-pinning 2020.07.18.02.18.36
- cython >=0.28.2 | ||
- numpy | ||
- cython >=0.29.16 | ||
- numpy ==1.15.4 # [py != 38] |
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.
@xhochy can you check my work here? NumPy 1.17.3 is the first to support python 3.8.
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.
Seems that this will need some work for other platforms:
conda_build.exceptions.DependencyNeedsBuildingError: Unsatisfiable dependencies for platform linux-aarch64: {'numpy==1.15.4'}
cc @odidev if you have any suggestions.
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.
Actually we build Python 3.8 wheels with numpy 1.16 on conda-forge. #85
Also made a PR to ease numpy pinnings for maintainers: conda-forge/conda-forge-pinning-feedstock#701
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.
Seems that this will need some work for other platforms:
conda_build.exceptions.DependencyNeedsBuildingError: Unsatisfiable dependencies for platform linux-aarch64: {'numpy==1.15.4'}
cc @odidev if you have any suggestions.
@TomAugspurger,
Can we use numpy>=1.16.3
?
Note: AArch64 and PowerPC architectures are supported from numpy version >= 1.16.3(reference 1.16.3).
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.
Uwe fixed it in #85 if you want to check that.
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.
Thanks :)
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. |
@conda-forge-admin, please rerender |
One notable change, the label will now be |
…da-forge-pinning 2020.07.18.20.56.00
aarch64 is failing because of #84 (comment). I'm not sure why powerpc is timing out, but I'm not going to hold up the rest for it. |
Just a guess based off of error message and this SO post: https://stackoverflow.com/questions/12652641/cflags-wl-export-dynamic-vs-linker-flags-export-dynamic But maybe the argument should be |
Alternately maybe we can get rid of that option altogether? Not super familiar with this toolchain so not clear where that is coming from, but the man page for
I don't think pandas needs that at all? And it may in fact be beneficial to remove? |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)