Re: [Zope-dev] Re: Windows Binaries for 2.8b1
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 other. It would be better if Z3's setup.py used zpkgtools too, but it doesn't now. Yup. We encountered this pain in working on the 3.1 release. I'm hoping to spend some time with Fred tomorrow to see if we can make a checkout use more of zpkgtools. zpkgtools is still a work in progress though. I expect we'll evolve it a bit more in the course of the 3.1 release. In any case, nothing in Z2 (including WinBuilders) knows anything about how to live with zpkgtools now. Yup. I'd like to fix this for 2.9. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Windows Binaries for 2.8b1
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 following this. Contributers. setup.py. AFAICS two things could help them: - giving feedback by running nightly test on a not-in-place installation That would be helpful. - reducing the need for setup.py updates by switching to the Zope 3 setup code 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 other. It would be better if Z3's setup.py used zpkgtools too, but it doesn't now. In any case, nothing in Z2 (including WinBuilders) knows anything about how to live with zpkgtools now. For Zope 2.8, there may not be a realistic alternative to teaching Zope 2.8's setup.py how to install the Z3 bits in Zope 2.8. It already does this for other pieces. For example, ZODB 3.4 (which Zope 2.8 uses) inherited the same setup.py-vs-zpkgtools schizophrenia from Zope3, but Zope 2.8's setup.py learned how to install ZODB 3.4 independent of that (indeed, ZODB's own setup.py has never been part of any Zope checkout that I know of). Seems I wasn't specific enough. I just meant setup.py, not the other setup code from Zope 3. The Zope 2 code requires to specify each directory. The Zope 3 code walks through all subdirectories and searchs for files with the specified file extensions. That code is already part of the Zope 2 setup.py, but only used for the Zope 3 stuff. I didn't try it, but I guess it would not be too hard to use it for all the other packages as well. Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Windows Binaries for 2.8b1
[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 from the result of doing "setup.py install ...", and add missing >> files to setup.py until that works. The WinBuilders tests can't >> possibly work either so long as setup.py neglects to install necessary >> files. [yuppie] > Done. (besides the Zope 3 failures) Thank you! > I did that more than once, Did what more than once? > but why can't people clean up after themselves? Which people, cleaning up what? Sorry, I'm not following this. > AFAICS two things could help them: > > - giving feedback by running nightly test on a not-in-place installation That would be helpful. > - reducing the need for setup.py updates by switching to the Zope 3 > setup code 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 other. It would be better if Z3's setup.py used zpkgtools too, but it doesn't now. In any case, nothing in Z2 (including WinBuilders) knows anything about how to live with zpkgtools now. For Zope 2.8, there may not be a realistic alternative to teaching Zope 2.8's setup.py how to install the Z3 bits in Zope 2.8. It already does this for other pieces. For example, ZODB 3.4 (which Zope 2.8 uses) inherited the same setup.py-vs-zpkgtools schizophrenia from Zope3, but Zope 2.8's setup.py learned how to install ZODB 3.4 independent of that (indeed, ZODB's own setup.py has never been part of any Zope checkout that I know of). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Windows Binaries for 2.8b1
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 from the result of doing "setup.py install ...", and add missing files to setup.py until that works. The WinBuilders tests can't possibly work either so long as setup.py neglects to install necessary files. Done. (besides the Zope 3 failures) I did that more than once, but why can't people clean up after themselves? AFAICS two things could help them: - giving feedback by running nightly test on a not-in-place installation - reducing the need for setup.py updates by switching to the Zope 3 setup code Just my 2 cents. Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Windows Binaries for 2.8b1
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 files you added manually. Besides the 2 ZServer tests the same tests fail on Linux. The setup code for the Zope 3 stuff works different and I don't want to fork it. So these errors should be discussed with the Zope 3 people. I think you should release what you have now. But for the next beta these errors should be release blockers. Maybe you can run Windows tests *before* Andreas tags the next beta release? Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Windows Binaries for 2.8b1
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 tar-packed source checkout is ok. > needed for WinBuilders? Will WinBuilders work with InnoSetup 5.0.8? Not AFAIK. Cheers, CHristian -- gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Windows Binaries for 2.8b1
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 the procedure of getting packaged so I had to copy
those files manually for running the tests. Then the doctest module
doesn't comply with platform independent handling of path names using
'variable.split("/")' and relatives.
The now running tests fail pretty much in various places (Catalog,
ZODB, ...)
I'm not able to do any work on this as I'm lacking time. I took the job
of building the releases as long as it's pressing the "do it now button"
and running the tests seeing them pass. I did not take the job of
cleaning up Zope for Windows. The WinBuilders are a really annoying
thing, I'm glad they went away for Zope3.
To notice: Zope 2.8a1 has not been available as Windows release and
neither will be 2.8b1. You really want to blindly go forward for an RC
not having a single external user running any 2.8 release at all?
I'm pretty annoyed right now.
Cheers,
Christian
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
needed for WinBuilders? Will WinBuilders work with InnoSetup 5.0.8?
Regards,
Florian Schulze
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
