[issue11487] build_installer.py should avoid relying on a young Python

Ned Deily added the comment: The changes for Issue21383 added calls to "make touch" to build_installer.py so the initial problem reported here should no longer occur on any OS X installer build. As to the more general problem of needing to use "make touch" because hg checkouts do not preserve

[issue11487] build_installer.py should avoid relying on a young Python

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11487] build_installer.py should avoid relying on a young Python

Ronald Oussoren added the comment: Issue11485 contains a comment of someone that ran into the same issue is me. -- ___ Python tracker ___ ___

[issue11487] build_installer.py should avoid relying on a young Python

Ned Deily added the comment: Note, there is a fix for the "$MACOSX_DEPLOYMENT_TARGET mismatch" Ronald mentions in Issue9516 and is only a problem if, during the build, /usr/bin/env python is a Python 2.7 that was built with a different deployment target. Python 2.6 and earlier are not suscep

[issue11487] build_installer.py should avoid relying on a young Python

David Bolen added the comment: Guess I cry uncle - not sure how it used to work then. I just did a dummy svn checkout off of the older svn.python.org from trunk and the .[ch] files appear to have dates earlier than the asdl.py script, so I would have assumed it would have the same problem.

[issue11487] build_installer.py should avoid relying on a young Python

Antoine Pitrou added the comment: (the change will probably make things worse actually; see http://bugs.python.org/issue11419) -- ___ Python tracker ___ ___

[issue11487] build_installer.py should avoid relying on a young Python

Antoine Pitrou added the comment: > I suspect this may be an issue now because the old svn approach was a > full checkout for each build, whereas the hg approach is to pull to > the local clone, and then just update the build tree. So in the svn > case all the files would have a good shot at th

[issue11487] build_installer.py should avoid relying on a young Python

David Bolen added the comment: Note in the meantime, I've manually touched those two files on the dmg buildbot and it builds successfully. As Antoine pointed out to me separately, the hg update used by the buildbot should leave that intact, so this should stop any buildbot failures for the t

[issue11487] build_installer.py should avoid relying on a young Python

David Bolen added the comment: Note that some of my last comment was before I saw the others, so I'm fine with script changes if that seems ok to others. >From Ronald: "This is because the header file and input grammar have the same timestamp, and which forces the rebuild." Note in the buil

[issue11487] build_installer.py should avoid relying on a young Python

Ronald Oussoren added the comment: This does not only affect the installer. On my machine the python on $PATH was build using the 10.6 deployment target. When I build python from a fresh checkout I get an error message because the 10.6 python gets run with deployment target 10.4 and then barf

[issue11487] build_installer.py should avoid relying on a young Python

David Bolen added the comment: Just a few thoughts that were in part in an earlier exchange with Antoine. It seems to me that if the Python-ast.[ch] files are included in the repository then they ought to be up to date as part of any given change set. So I think I'd actually prefer having th

[issue11487] build_installer.py should avoid relying on a young Python

Ronald Oussoren added the comment: To avoid duplicate work: I'll commit a patch during the pycon sprints -- ___ Python tracker ___ __

[issue11487] build_installer.py should avoid relying on a young Python

Ronald Oussoren added the comment: I noticed this myself as well when building a fresh checkout, without build_installer.py. This is because the header file and input grammar have the same timestamp, and which forces the rebuild. That causes problems on OSX when you build with a different d

[issue11487] build_installer.py should avoid relying on a young Python

New submission from Antoine Pitrou : There was this failure in the daily DMG builder: http://www.python.org/dev/buildbot/all/builders/3.x.dmg/builds/423/steps/compile/logs/stdio The problem is that asdl_c.py gets run by the Makefile with the standard Python, which on this machine is 2.3.5 (acco