-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-105908: fix barry_as_FLUFL
future import
#105909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Is there no test for this? |
I'm currently adding it. |
Misc/NEWS.d/next/Core and Builtins/2023-06-19-11-04-01.gh-issue-105908.7oanny.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Kirill Podoprigora <[email protected]>
Thank you @thatbirdguythatuknownot . |
@thatbirdguythatuknownot there is a test failure in the "Address sanitizer" test. Is it due to this PR? |
It must be from |
Thanks! This change makes sense. |
Does this need to be backported to 3.12? |
Thanks @thatbirdguythatuknownot for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
GH-105930 is a backport of this pull request to the 3.12 branch. |
(cherry picked from commit 28187a9) Co-authored-by: Crowthebird <[email protected]>
…5930) (cherry picked from commit 28187a9) Co-authored-by: Crowthebird <[email protected]>
In
compiler_setup()
, theflags
parameter is a local struct that does not reflect changes to the pointer passed tonew_compiler()
. Fix by making theflags
parameter a pointer to a struct instead of a struct.__future__
importbarry_as_FLUFL
does not work in the REPL anymore #105908