Christian Theune wrote:
Sticking to this thread ...
[...]
--
Ran 5634 tests in 1433.151s
FAILED (failures=3, errors=2)
Any comments? Still hesitating to release the binaries, but I have them
around.
I changed setup.py to add the
Tim Peters wrote:
Someone with setup.py courage needs to step up to the plate then. The
Windows build process is way hard enough to follow already without
adding reams of arbitrary new makefile cruft to paper over setup.py
bugs. Perhaps someone on Linux could volunteer to run Zope trunk
tests
[Tim Peters]
Someone with setup.py courage needs to step up to the plate then. The
Windows build process is way hard enough to follow already without
adding reams of arbitrary new makefile cruft to paper over setup.py
bugs. Perhaps someone on Linux could volunteer to run Zope trunk
tests
Hi!
Tim Peters wrote:
[yuppie]
I did that more than once,
Did what more than once?
Updating setup.py. (Or reminding people to do it themselves if they add
new files and forget to update setup.py.)
but why can't people clean up after themselves?
Which people, cleaning up what? Sorry, I'm not
Tim Peters wrote:
[Tim Peters]
...
I think this gets worse with Zope3 code, and especially when mixed in
with Zope2. Zope3 still uses setup.py for testing from a checkout,
but uses zpkgtools for building a distribution: those two subsystems
have nothing in common, and get out of synch with each
On Mon, 25 Apr 2005 10:54:23 +0200, Christian Theune [EMAIL PROTECTED] wrote:
Hi,
and again, I got to complain about building Zope on Windows. This time
it's the 2.8 branch again with the 2.8b1 release.
It looks like the WinBuilders aren't taken care for at all. The ZClass
tests didn't got into
Am Montag, den 25.04.2005, 12:21 +0200 schrieb Florian Schulze:
I wanted to look a bit into this, but quickly ran into problems. I checked
out WinBuilders and Zope 2.8. I was easily able to use inst/configure.py
and nmake to compile and install Zope. But how do I generate the Zope.tgz
A
