Skip to content

Rebuild for python 3.13#249

Merged
isuruf merged 19 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-python313-0-1_h8f2626
Feb 18, 2025
Merged

Rebuild for python 3.13#249
isuruf merged 19 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-python313-0-1_h8f2626

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor

@regro-cf-autotick-bot regro-cf-autotick-bot commented Dec 20, 2024

This PR has been triggered in an effort to update python313.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12434062644 - please use this URL for debugging.


Fixes #246

@conda-forge-admin
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.

@wshanks
Copy link
Copy Markdown

wshanks commented Dec 31, 2024

I am trying to understand the problem here. It seems like the build tries to install conda into the Python 3.13 environment for the 3.13 builds but that fails because the 3.13 build of conda doesn't exist yet? Somehow this is not an issue for 3.13 builds of things other than conda though....

Comment thread recipe/meta.yaml
Comment thread recipe/meta.yaml Outdated
@jakirkham
Copy link
Copy Markdown
Member

@conda-forge-admin , please re-render

@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

  • Is the recipe/{meta.yaml,recipe.yaml} file valid?
  • If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
  • Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

@jakirkham
Copy link
Copy Markdown
Member

@conda-forge-admin , please re-render

@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

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

@conda-forge-admin
Copy link
Copy Markdown
Contributor

conda-forge-admin commented Feb 4, 2025

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

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

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

* Provide a default value for `python`
* Convert values to `int`
* Ensure the final result is a `list`
@conda-forge-admin
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.

Besides this is equivalent to `win`, which can already be used.
This doesn't change. Inlining it gives us one less thing to think about.
To push out Python 3.13, temporarily disable conda-build's tests. A
simple re-render will add them back. After Python 3.13 packages are
available, the tests should pass again.
Copy link
Copy Markdown
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

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

As noted in issue ( #246 ), there is a cycle as conda-libmamba-solver requires conda, which in turn requires conda-libmamba-solver. It sounds like we don't want to break the cycle either

Tried a few ways to bypass the cycle here, it looks like the best approach is just to pass --no-tests to disable the test phase entirely

Have done this below and commented on where. All of these are in CI files that will be overwritten when conda-smithy re-renders

This should help us get Conda packages out for Python 3.13. We can re-enable tests with a re-render after

Comment thread .scripts/build_steps.sh
Comment on lines +51 to +53
# Temporary hack to skip testing and push out Python 3.13.
# Re-rendering after will revert this.
EXTRA_CB_OPTIONS="${EXTRA_CB_OPTIONS:-} --no-test"
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.

This temporarily disables the package test phase on Linux

Comment thread .scripts/run_osx_build.sh
Comment on lines +80 to +82
# Temporary hack to skip testing and push out Python 3.13.
# Re-rendering after will revert this.
EXTRA_CB_OPTIONS="${EXTRA_CB_OPTIONS:-} --no-test"
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.

This temporarily disables the package test phase on macOS

Comment on lines +67 to +69
:: Temporary hack to skip testing and push out Python 3.13.
:: Re-rendering after will revert this.
set "EXTRA_CB_OPTIONS=%EXTRA_CB_OPTIONS% --no-test"
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.

This temporarily disables the package test phase on Windows

Comment thread recipe/meta.yaml
Comment on lines +15 to +18
patches:
# Backport https://github.com/conda/conda/pull/14117 for changes in the
# Python 3.13+ logging module internals
- patches/0001-GH-14117-logging-lock-internal-changes-py313.patch
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.

Have merged in Bradley's PR ( #258 ), which the patch from upstream PR ( conda/conda#14117 )

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

conda/conda#14584 may be a better patch to pull in as it was merged.

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.

Thanks Jonathan! 🙏

Glad to see your fix landed 🙂

Yeah we can update the patch. Would you like to send a PR to update it?

@jakirkham jakirkham mentioned this pull request Feb 4, 2025
1 task
Comment thread recipe/meta.yaml Outdated
@beckermr
Copy link
Copy Markdown
Member

beckermr commented Feb 4, 2025

ok LGTM!

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.

Python 3.13 migrator failing

8 participants