Skip to content
Merged
25 changes: 0 additions & 25 deletions recipe/conda_build_config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -44,28 +44,3 @@ zip_keys:
- python_version
- python_impl_version
- python_implementation

# to help PBP generate a proper build graph
python:
- "3.10"
- "3.11"
- "3.12"
- "3.13"
- "3.13"
- "3.14"
- "3.14"
- "3.15"
- "3.15"
numpy:
- "2.1"
- "2.1"
- "2.1"
- "2.1"
- "2.1"
- "2.1"
- "2.1"
# TODO: numpy 2.6.0 is not released yet;
# upstream says py315 support starts with Python 3.15.0rc1 (~Jul 2026)
# keep 2.4 for now. Recheck when 2.6.0 is released.
- "2.5"
- "2.5"
Comment on lines -47 to -71

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If these were originally added to help with PBP generation, has something improved on the PBP side such that we can remove them?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was needed a long time ago, but now it's already in a global cbc.yaml. It was a bug on PBP. I don't recall when it was fixes

11 changes: 8 additions & 3 deletions recipe/meta.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{% set build_num = 4 %}
{% set build_num = 5 %}
{% if python_impl_version is not defined %}
{% set python_impl_version = "3.8" %}
{% endif %}
Expand All @@ -16,12 +16,17 @@ package:
build:
number: {{ build_num }}
string: {{ build_num }}_{{ python_abi_tag }}
track_features: # [python_implementation != "cpython"]
track_features:
- pypy # [python_implementation == "pypy"]
- native_graalpy # [python_implementation == "graalpy"]
# Required for PBP.
- freethreading # [python_implementation == "cpython" and python_abi_tag.endswith("t")]
# force_ignore_keys required for PBP. Ignore aggregate python zip_keys (numpy /
# is_freethreading / is_python_min) so this matrix does not collide.
force_ignore_keys:
- python
- numpy
- is_freethreading
- is_python_min
Comment on lines +23 to +29

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a question about this: given my experiments and the need for python to use is_freethreading in order to discriminate between 314 and 314t python variants at build and run time then I wonder if we're missing something here by "force ignoring" these keys?


requirements:
run_constrained:
Expand Down