3.11.1 and 3.12 alphas need additional path configuration on Windows #2817
Comments
This was referenced Dec 18, 2022
Closed
Merged
bors bot
added a commit
that referenced
this issue
Dec 18, 2022
2821: ci: pin more to 3.11.0 r=davidhewitt a=davidhewitt Still getting some windows failures due to #2817. Pin more stuff for now :( Co-authored-by: David Hewitt <[email protected]>
bors bot
added a commit
that referenced
this issue
Dec 18, 2022
2821: ci: pin more to 3.11.0 r=davidhewitt a=davidhewitt Still getting some windows failures due to #2817. Pin more stuff for now :( Co-authored-by: David Hewitt <[email protected]>
Merged
bors bot
added a commit
that referenced
this issue
Feb 28, 2023
2990: Fix `clippy::redundant_closure` lint firing for pyfunction defaults r=adamreichold a=davidhewitt Fixes #2988 I'll push a follow-up for the FIXME as a separate PR. 2991: unpin 3.11 ci jobs r=adamreichold a=davidhewitt With Python 3.11.2 released for a couple weeks now, I think #2817 is probably not an issue in CI any more. Co-authored-by: David Hewitt <[email protected]>
|
It seems this is no longer the case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://github.com/PyO3/pyo3/actions/runs/3721944864/jobs/6312442577#step:11:1094 - we have CI failures on Windows along the lines of
Appears to be the following upstream issue: python/cpython#100171
We may need to do something smarter in
auto-initializedepending on what the outcome of decisions upstream are. We have had several issues of interacting with virtualenvs in the past, e.g. #1741 #1896, maybe it's now time anyway to implement a new "default" inprepare_freethreaded_pythonwhich covers what users are most likely to want?The text was updated successfully, but these errors were encountered: