My apologies if this is a wrong venue. Is this a conda-forge problem?
When I run
mamba create -n foo meson-python numpy 'python>=3.13'
the free-threaded python is selected:
+ python 3.13.0 h6355ac2_0_cp313t conda-forge
Cached
+ numpy 2.1.3 py313hb01392b_0 conda-forge
Cached
When python spec is moved to the front, I do get the "usual" version.
However, when I build a python extension with conda-build, I do not control
the order. The extension is created for the free-threaded version. Here is
my requirements section in recipe/meta.yaml:
requirements:
build:
- {{ compiler('c') }}
- {{ compiler('fortran') }}
host:
- python >=3.13
- python_abi =3.13.* *_cp313 # needed to prevent selection of
freethreaded python
- meson-python
- numpy >=2.0
- pip
run:
- python >=3.13
- numpy >=2.0
I did manage to find a workaround, which is the python_abi line. Am I doing
it right?
_______________________________________________
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
