-
-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Python 3.6.0b4 64-bit has no sys._mercurial info #72759
Comments
The release build for 3.6.0b3 64-bit is missing Mercurial info: >>> import sys
>>> sys._mercurial
('CPython', '', '')
>>> sys.version
'3.6.0b3 (default, Nov 1 2016, 03:21:01) [MSC v.1900 64 bit (AMD64)]' The debug build and the 32-bit builds are fine. It needs further investigation, but I assume the PGO build is to blame, as we only run PGO on the 64-bit release build. |
The same is on 3.5.2 on ubuntu 16.10 |
We're not responsible for the builds released by Linux distros. There's a good chance they didn't build from mercurial, but used the source release plus patches. |
New changeset 25cb7df5b19d by Steve Dower in branch '3.6': New changeset ae8f525cef2a by Steve Dower in branch 'default': |
I suspect this is because my PATH was getting too long within my build script because of setting up the VS build environment too many times (if PATH gets too long then new processes may ignore or truncate it). The commit should cut this down to the point where we don't lose Mercurial off of PATH, but I'm running validation builds to be sure. As this only applies to the Windows builds and we haven't seen it against 3.5 yet, I'm dropping that from the versions list. |
New changeset d997e64130bd by Steve Dower in branch '3.6': New changeset 35f510158490 by Steve Dower in branch 'default': |
Wasn't fixed as well as I'd like, so I clearly need a better approach here. |
Attaching the patch here for visibility. In short, rather than relying on PATH to find hg.exe, we now precalculate it and pass it in to the build. This completely avoids the problem where modifying PATH multiple times for different builds was causing Mercurial to fall off. This patch also fixes two other issues with my build script - the PGOOPTS need to come before CERTOPTS, as they are parsed by different scripts, and the debug build command fell off somewhere which resulted in the debug builds not being rebuilt for 3.6.0b4 - they are still the 3.6.0b3 debug build. |
New changeset 089886be06df by Steve Dower in branch '3.6': New changeset d0958078bcb6 by Steve Dower in branch 'default': |
Ned approved this last night on IRC, so now it's in. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: