Rebuild for python 3.13#249
Conversation
…onda-forge-pinning 2024.12.20.14.58.42
|
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 ( |
|
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.... |
|
@conda-forge-admin , please re-render |
|
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 The following suggestions might help debug any issues:
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. |
|
@conda-forge-admin , please re-render |
|
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. |
|
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 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`
|
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 ( |
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.
jakirkham
left a comment
There was a problem hiding this comment.
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
| # 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" |
There was a problem hiding this comment.
This temporarily disables the package test phase on Linux
| # 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" |
There was a problem hiding this comment.
This temporarily disables the package test phase on macOS
| :: 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" |
There was a problem hiding this comment.
This temporarily disables the package test phase on Windows
| 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 |
There was a problem hiding this comment.
Have merged in Bradley's PR ( #258 ), which the patch from upstream PR ( conda/conda#14117 )
There was a problem hiding this comment.
conda/conda#14584 may be a better patch to pull in as it was merged.
There was a problem hiding this comment.
Thanks Jonathan! 🙏
Glad to see your fix landed 🙂
Yeah we can update the patch. Would you like to send a PR to update it?
|
ok LGTM! |
This PR has been triggered in an effort to update python313.
Notes and instructions for merging this PR:
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-rerunlabel 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 botin a PR comment to have theconda-forge-adminadd 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