Drop pin_compatible('numpy')
#547
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lookup key with `get`. If it is not found, it will be `None`. If it is found, it can be used without another lookup.
jakirkham
force-pushed
the
drop_pin_np
branch
2 times, most recently
from
d090db9
to
438ff71
Compare
This is no longer needed as `numpy` has `run_exports`.
|
can you rebase and resolve the conflicts with main branch please? |
|
The conflicts appear to be introduced by PR: #552 However there are some changes there that don't quite make sense to me. Let's discuss a bit more in that PR to see what next steps would be |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
pin_compatible('numpy')(this is handled vianumpy'srun_exports){{ pin_compatible("numpy") }}from NumPy docs conda-forge/conda-forge.github.io#2156PIN_PKG_COMPILERcode to lookup key only once