| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Is there no test for this? |
Sorry, something went wrong.
I'm currently adding it. |
Sorry, something went wrong.
Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
|
@thatbirdguythatuknownot there is a test failure in the "Address sanitizer" test. Is it due to this PR? |
Sorry, something went wrong.
It must be from flags = &_PyCompilerFlags_INIT. I could probably bring back the local_flags variable to prevent it. |
Sorry, something went wrong.
|
Thanks! This change makes sense. |
Sorry, something went wrong.
|
Does this need to be backported to 3.12? |
Sorry, something went wrong.
|
Thanks @thatbirdguythatuknownot for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
|
GH-105930 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
(cherry picked from commit 28187a9) Co-authored-by: Crowthebird <78076854+thatbirdguythatuknownot@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
In compiler_setup(), the flags parameter is a local struct that does not reflect changes to the pointer passed to new_compiler(). Fix by making the flags parameter a pointer to a struct instead of a struct.