Skip to content

matplotlib 3.11.1 - #40

Open
maciejtraczyk wants to merge 1 commit into
masterfrom
PKG-17483
Open

maciejtraczyk wants to merge 1 commit into
masterfrom
PKG-17483

Conversation

@maciejtraczyk

Copy link
Copy Markdown

@maciejtraczyk
maciejtraczyk force-pushed the PKG-17483 branch 4 times, most recently from 29e36ea to f1199ed Compare September 14, 2026 14:28
@package-build-platform

Copy link
Copy Markdown
Failed to submit graph for f1199ed

Message:
Failed to run command: 'pbp generate from-feedstock --output /tmp/tmpmndn83ft/matplotlib-feedstock.yaml --custom-metadata-file /tmp/tmpmndn83ft/custom_metadata.yaml --release-name matplotlib-feedstock-40-f1199edd33941e0c444573ea44afa4ac92468768 matplotlib-feedstock/recipe', with error: 'INFO:root:Found feedstock matplotlib-feedstock at /tmp/tmpmndn83ft/matplotlib-feedstock/recipe
INFO:root:Build/Test graph from matplotlib-feedstock
Created by sbx_user1051 on 2026-09-14 14:28:30
Command line: /opt/conda/envs/webhook-listener/bin/pbp generate from-feedstock --output /tmp/tmpmndn83ft/matplotlib-feedstock.yaml --custom-metadata-file /tmp/tmpmndn83ft/custom_metadata.yaml --release-name matplotlib-feedstock-40-f1199edd33941e0c444573ea44afa4ac92468768 matplotlib-feedstock/recipe

INFO:root:Creating graph from feedstock at: matplotlib-feedstock
INFO:pbpcli.utils.common:Setting env var: CONDA_SUBDIR = linux-64.
INFO:pbpcli.utils.expand_variants:Elapsed time for get_package_variants: 0.11 seconds
INFO:pbpcli.utils.expand_variants:Matrix vars: 5 unchanging vars:(473), changing vars (5): ['blas_impl', 'cuda_compiler_version', 'is_python_min', 'numpy', 'python']
INFO:pbpcli.utils.expand_variants:Elapsed time for preparation for render: 0.00 seconds
INFO:pbpcli.utils.common:Setting env var: CONDA_PKGS_DIRS = /tmp/conda_pkgs_5eon8cas.
INFO:pbpcli.utils.common:Unsetting env var: CONDA_PKGS_DIRS
INFO:pbpcli.utils.common:Unsetting env var: CONDA_SUBDIR
Error: bad character '>=' in package version dependency 'pyqt'
Perhaps you meant 'pyqt >=6.11'
'
aws lambda request id: 9d94129c-cf4d-5d10-bee2-71bec98d9793
View in Grafana

Comment thread recipe/meta.yaml
run:
- python
- pyqt >=5 # [(linux64 or win) and python_impl == "cpython"]
- pyqt {{pyqt}} # [(linux64 or win) and python_impl == "cpython"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
- pyqt {{pyqt}} # [(linux64 or win) and python_impl == "cpython"]
- pyqt >=5 # [(linux64 or win) and python_impl == "cpython"]

Prefer >=5 notation in the run section over {{pyqt}} (it's designed for the host section).

Do we need pyqt {{pyqt}} in the host to pin it 6.11? See https://github.com/AnacondaRecipes/aggregate/blob/master/conda_build_config.yaml#L891C6-L891C10

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.

this change was change was suggested by linter check but you're right it suppose to apply only to the host section I had to missed that.

"matplotlib-feedstock/recipe/meta.yaml:/outputs/1/requirements/host/1: host_section_needs_exact_pinnings: pyqt in host should be pinned to its conda_build_config.yaml value: pyqt {{ pyqt }}."

when it comes to bumping pyqt into 6.11 I think we can stay with >= 5 as there Is no sign of it as a requirement so to avoid further solver conflicts In my opinion we can stay with >=5, unless I missing something @skupr-anaconda?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The linter flags pinning in host so that a specific version is used (i.e. the one set in the cbc).
The runtime constraint itself is set by the run_exports of the package (https://github.com/AnacondaRecipes/pyqt-feedstock/blob/master/recipe/meta.yaml#L65).

So

host:
- pyqt {{ pyqt }}
run:
- pyqt >=5

Will render as:

host:
- pyqt 6.11
run:
- pyqt >=5
- pyqt >=6.11.0,<6.12.0

We shouldn't pin in run to pyqt {{ pyqt }}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants