You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/maintainer/knowledge_base.md
+8-20Lines changed: 8 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -533,9 +533,10 @@ requirements:
533
533
- numpy
534
534
run:
535
535
- python
536
-
- {{ pin_compatible("numpy") }}
537
536
```
538
537
538
+
For more details about numpy see the dedicated [section](#building-against-numpy).
539
+
539
540
With MPI, openmpi is required for the build platform as the compiler wrappers are binaries, but mpich is not required as the compiler wrappers are scripts (see [example](https://github.com/conda-forge/mpi4py-feedstock/blob/743d379c4a04/recipe/meta.yaml#L37)):
540
541
541
542
```yaml
@@ -770,36 +771,23 @@ host:
770
771
- numpy
771
772
```
772
773
773
-
At the time of writing (January, 2025), above is equivalent to the following,
774
-
775
-
```yaml
776
-
host:
777
-
- numpy 1.22 # [py==39]
778
-
- numpy 1.22 # [py==310]
779
-
- numpy 1.23 # [py==311]
780
-
- numpy 1.26 # [py==312]
781
-
```
782
-
783
-
though the ongoing migration for numpy 2.0 has already been applied to many
784
-
feedstocks, in which case the pinning looks like
774
+
At the time of writing (June 2025), above is equivalent to the following,
785
775
786
-
```yaml
776
+
```yaml title="recipe/conda_build_config.yaml"
787
777
host:
788
-
- numpy 2.0 # [py==39]
789
-
- numpy 2.0 # [py==310]
790
-
- numpy 2.0 # [py==311]
791
-
- numpy 2.0 # [py==312]
778
+
- numpy 2.*
792
779
```
793
780
794
-
See the pinning repository for what the pinning corresponds to at time of writing
[what the pinning corresponds to](https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml#L742) at any given time.
796
783
797
784
In either case, the actual runtime requirements are determined through numpy's
798
785
run-export, which is:
799
786
800
787
- `>=1.2x,<2`if you're building against numpy 1.2x
801
788
- `>=1.19,<3`if you're building against numpy 2.0
802
789
- `>=1.21,<3`if you're building against numpy 2.1 or 2.2
790
+
- `>=1.23,<3`if you're building against numpy 2.3
803
791
804
792
If the package you are building has a higher minimum requirement for numpy, please add this under `run`:
0 commit comments