Skip to content

python 3.12.12 - #815

Merged
conda-forge-admin merged 8 commits into
conda-forge:3.12from
xhochy:3.12-rerender2
Oct 13, 2025
Merged

conda-forge-admin merged 8 commits into
conda-forge:3.12from
xhochy:3.12-rerender2

Conversation

@xhochy

@xhochy xhochy commented Sep 25, 2025

Copy link
Copy Markdown
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

…5.09.25.19.16.51

Other tools:
- conda-build 25.7.0
- rattler-build 0.47.0
- rattler-build-conda-compat 1.4.6
@conda-forge-admin

conda-forge-admin commented Sep 25, 2025

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/18466603854. Examine the logs at this URL for more detail.

@isuruf

isuruf commented Sep 25, 2025

Copy link
Copy Markdown
Member

We build with ffat-lto-objects to avoid these issues. Does that not work as expected?

@xhochy

xhochy commented Sep 26, 2025

Copy link
Copy Markdown
Member Author

No, it doesn't, see conda-forge/uwsgi-feedstock#100 This failed for all Python versions and succeed on a retry for Python 3.13 which was rebuilt in the meantime.

@isuruf

isuruf commented Sep 28, 2025

Copy link
Copy Markdown
Member

Can you try and see if replacing libpython${PY_VER}.a with libpython${PY_VER}.notlto.a works?

@xhochy xhochy changed the title [3.12] Rebuild for GCC 14 python 3.12.12 Oct 10, 2025
xhochy and others added 3 commits October 10, 2025 14:20
…5.10.08.21.44.29

Other tools:
- conda-build 25.9.0
- rattler-build 0.47.1
- rattler-build-conda-compat 1.4.8
Comment thread recipe/meta.yaml Outdated
{% set ver2nd = ''.join(version.split('.')[0:2]) %}
{% set ver3nd = ''.join(version.split('.')[0:3]) %}
{% set build_number = 0 %}
{% set build_number = 1 %}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

spurious build number bump

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

FWIW, the same things occurred for the other (very similar) PRs for 3.10, 3.11 and 3.13, but those are merged already now. 🤷

@isuruf isuruf added the automerge Merge the PR when CI passes label Oct 13, 2025
@conda-forge-admin
conda-forge-admin merged commit dcba610 into conda-forge:3.12 Oct 13, 2025
14 checks passed
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

@xhochy
xhochy deleted the 3.12-rerender2 branch October 13, 2025 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants