Re: [Python-Dev] fixing broken build

2008-03-27 Thread Christian Heimes
Neal Norwitz schrieb:
 Christian,
 
 Please fix the build on the various buildbots that are failing or
 revert your changes for unicode literals.  The build failures started
 to occur at r61953.  There were several more (~5) follow up checkins.
 
 You can find all the failures here:  http://www.python.org/dev/buildbot/all/
 
 There seem to be at least two variations for how setup.py is failing.
 See below.

I've already fixed the problem in r61956. I didn't noticed the issue
with a non initialized var until I compiled Python without pydebug. In
order to fix the problem on the build bots one has to remove all pyc and
pyo files.

Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] fixing broken build

2008-03-27 Thread M.-A. Lemburg
On 2008-03-27 09:20, Christian Heimes wrote:
 Neal Norwitz schrieb:
 Christian,

 Please fix the build on the various buildbots that are failing or
 revert your changes for unicode literals.  The build failures started
 to occur at r61953.  There were several more (~5) follow up checkins.

 You can find all the failures here:  http://www.python.org/dev/buildbot/all/

 There seem to be at least two variations for how setup.py is failing.
 See below.
 
 I've already fixed the problem in r61956. I didn't noticed the issue
 with a non initialized var until I compiled Python without pydebug. In
 order to fix the problem on the build bots one has to remove all pyc and
 pyo files.

I'm not sure why that's necessary, but whenever you change something
in the compiler, please remember to update the PYC magic.

I'd also suggest that you run a non-debug build of Python to test
any checkins before committing them. The debug builds change various
ways the code is built.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Mar 27 2008)
  Python/Zope Consulting and Support ...http://www.egenix.com/
  mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
  mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/


 Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! 


eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] fixing broken build

2008-03-27 Thread Christian Heimes
M.-A. Lemburg schrieb:
 I'm not sure why that's necessary, but whenever you change something
 in the compiler, please remember to update the PYC magic.
 
 I'd also suggest that you run a non-debug build of Python to test
 any checkins before committing them. The debug builds change various
 ways the code is built.

Changing the pyc magic isn't required here. Some files were compiled to
bytecode with the wrong flags because I didn't initialize the flags
correctly. I (ab)used a temporary change of the magic to force a
recompilation of bytecode. All build bots are fine again.

I usually don't test the new code with a non-debug build unless a
release is immanent. A full test run already takes a considerable amount
of time (10 minutes) and debug builds usually catch more errors than
plain builds. I've to draw the line somewhere ...

Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com