Bump python from 3.12 to 3.13 - #182
Conversation
|
|
|
The condalock timed out on this. @itcarroll @weiji14 Do y'all know what happened by any chance? I think its working up to the same on #183 too. It seemed fine on our previous PRs. |
|
I restarted condalock 137, because that looked like a weird network failure. It got through the locking step. Let's see what happens. Condalock 136 looks like a true locking problem. |
|
It sounds like #177 may have broken the passing of credentials to git push. So made an adjustment and rerunning the conda lock. |
|
@tsnow03, let's test/debug on your PR at #183 first, the solver will be faster and we can check whether there's something wrong with the credentials. There are some issues with PRs on GitHub and I'm wondering if that's causing some trouble. |
Bumps [python](https://github.com/python/cpython) from 3.12.13 to 3.13.13. - [Release notes](https://github.com/python/cpython/releases/tag/v3.13.13) - [Changelog](https://docs.python.org/3.13/whatsnew/3.13.html) - [Commits](python/cpython@v3.12.13...v3.13.13)
|
/condalock |
|
Looks like mamba=2.7.0 did something good, locking now takes ~10min! Ready for review now 🎉 |
|
amaze amaze Now I'm more comfortable reverting most of #191, coming in a sec. Running a package compare here, I see one minor fallback in s3fs.
The s3fs changelog shows it, oddly, as a no-op so LGTM! |
4 participants
Bumps python from 3.12.13 to 3.13.13.
Previous Python upgrade at ff4cc56