-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-103186: In test_tools.freeze, fetch CONFIG_ARGS from original source directory #103213
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
gh-103186: In test_tools.freeze, fetch CONFIG_ARGS from original source directory #103213
Conversation
instead of fetching from intermediate instance. As "make clean" is called against the intermediate instance, the build directory is cleared and the config arguments lookup fails with a ModuleNotFoundError
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Hello @erlend-aasland: I saw you worked on a similar change recently, would appreciate any feedback. Hello freeze experts: There is probably another way to capture the same info from the intermediate instance as long as we do so before "make clean" is called - but that solution felt messy. Please let me know whether I should have a go at improving the variable naming here as SRCDIR (original), srcdir (intermediate) and builddir (frozen) could cause confusion... |
@terryjreedy (as a participant of the parent issue) |
The following new exception for missing make file in the intermediate python instance is passing on all platforms except Ubuntu as part of the Github CI pipeline builds:
I'm happy to remove this, as technically the existence of the Makefile depends on ./configure being run successfully first? |
It depends on ./configure
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Closing as a duplicate of gh-102152. |
This is not a duplicate of gh-102152, which fetched CONFIG_ARGS from the copied source directory instead of from the build directory. This PR fetches CONFIG_ARGS from the original source directory, so it is slightly different, and possibly more correct; I don't have the bandwidth to look at this right now. I'll definitely be able to review it around the summit in a couple of weeks. |
Hi @erlend-aasland / @terryjreedy, |
This PR involves things beyond my knowledge. Erland, if you cannot finish this, can you suggest another reviewer? |
This reverts commit 4f3060a.
@kumaraditya303, should we backport this to 3.12? |
Yes |
Thanks @TabLand for the PR, and @erlend-aasland for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
GH-106667 is a backport of this pull request to the 3.12 branch. |
…l source directory (pythonGH-103213) Fetch CONFIG_ARGS from the original source directory, instead of from the copied source tree. When "make clean" is executed in the copied source tree, the build directory is cleared and the configure argument lookup fails. However, the original source directory still contains this information. (cherry picked from commit de82732) Co-authored-by: Ijtaba Hussain <ijtabahussain@live.com>
…al source directory (GH-103213) (#106667) gh-103186: In test_tools.freeze, fetch CONFIG_ARGS from original source directory (GH-103213) Fetch CONFIG_ARGS from the original source directory, instead of from the copied source tree. When "make clean" is executed in the copied source tree, the build directory is cleared and the configure argument lookup fails. However, the original source directory still contains this information. (cherry picked from commit de82732) Co-authored-by: Ijtaba Hussain <ijtabahussain@live.com>
instead of fetching from intermediate instance. As "make clean" is called against the intermediate instance, the build directory is cleared and the config arguments lookup fails with a ModuleNotFoundError:
More context here: #103186 (comment)