I don't know how far I'll get with this. Using the current
Zope-2_7-branch of the Zope module at cvs.zope.org:/cvs-repository,
building Zope via
python setup.py build_ext -i
worked fine when I got up today, using the released Python 2.4. One
of its tests fails, because of a Python bug that
It works on Linux, with Zope 2.7.4. Just as a note to others (I've mentioned
this to Tim already) if you set an environment variable DISTUTILS_DEBUG
before running a setup.py, you get very verbose information about what's going
on, and, more importantly, full tracebacks rather than terse error
[Anthony Baxter]
It works on Linux, with Zope 2.7.4.
Thanks!
Just as a note to others (I've mentioned this to Tim already) if you set an
environment variable DISTUTILS_DEBUG before running a setup.py, you get
very verbose information about what's going on, and, more importantly, full
This is going to need someone who understands distutils internals.
The strings we end up passing to putenv() grow absurdly large, and
sooner or later Windows gets very unhappy with them.
os.py has a
elif name in ('os2', 'nt'): # Where Env Var Names Must Be UPPERCASE
class controlling
On Thu, Mar 10, 2005 at 12:46:23PM -0500, Tim Peters wrote:
This is going to need someone who understands distutils internals.
The strings we end up passing to putenv() grow absurdly large, and
sooner or later Windows gets very unhappy with them.
In distutils.msvccompiler:
def __init__
[ A.M. Kuchling]
In distutils.msvccompiler:
def __init__ (self, verbose=0, dry_run=0, force=0):
...
self.initialized = False
def compile(self, sources,
output_dir=None, macros=None, include_dirs=None, debug=0,
extra_preargs=None,
