-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
ENH newer OSX SDKs #69
Conversation
@conda-forge-admin, please rerender. |
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 ( |
…nda-forge-pinning 2019.11.01
@conda-forge/pyqt any thoughts on the failure here? |
…nda-forge-pinning 2019.11.01
skip: true # [ppc64le] | ||
run_exports: | ||
{{ pin_subpackage('pyqt', max_pin='x.x') }} | ||
|
||
requirements: | ||
run_constrained: # [osx] | ||
- __osx >={{ MACOSX_DEPLOYMENT_TARGET|default("10.9") }} # [osx] |
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.
I wonder if it is this straightforward to standardize, is there a way to move this into something like conda-forge-pinning
?
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.
Not that I could think of unless we change the condition to be run
instead of run_constrained
which forces the user to use conda>=4.8
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)Relates to conda-forge/conda-forge.github.io#891