Hi all The z3c.from buildout process from the trunk is broken. Not sure since when. Why do we use such crapy parts like omplette in z3c.form? My traceback ------------ D:\eggDev\Source\z3c\z3c.form\trunk>bin\buildout.exe -N Develop: 'D:\\eggDev\\Source\\z3c\\z3c.form\\trunk\\.' Develop: 'D:\\eggDev\\Source\\z3c\\z3c.form\\trunk\\benchmark' Getting distribution for 'z3c.recipe.sphinxdoc'. Got z3c.recipe.sphinxdoc 0.0.8. Getting distribution for 'Sphinx'. Got sphinx 1.0.5. Getting distribution for 'Jinja2>=2.2'. warning: no previously-included files matching '*' found under directory 'docs\_build' warning: no previously-included files matching '*.pyc' found under directory 'jinja2' warning: no previously-included files matching '*.pyc' found under directory 'docs' warning: no previously-included files matching '*.pyo' found under directory 'jinja2' warning: no previously-included files matching '*.pyo' found under directory 'docs' Installing Jinja2 2.5.5 Caused installation of a distribution: jinja2 2.5.5 with a different project name. Got jinja2 2.5.5. Getting distribution for 'Pygments>=0.8'. Got pygments 1.3.1. Getting distribution for 'collective.recipe.omelette'. Got collective.recipe.omelette 0.9. While: Installing. Getting section omelette. Initializing section omelette. Loading zc.buildout recipe entry collective.recipe.omelette:default. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "d:\home\.buildout\eggs\zc.buildout-1.5.2-py2.6.egg\zc\buildout\buildout.py" , line 1805, in main getattr(buildout, command)(args) File "d:\home\.buildout\eggs\zc.buildout-1.5.2-py2.6.egg\zc\buildout\buildout.py" , line 468, in install [self[part]['recipe'] for part in install_parts] File "d:\home\.buildout\eggs\zc.buildout-1.5.2-py2.6.egg\zc\buildout\buildout.py" , line 1056, in __getitem__ options._initialize() File "d:\home\.buildout\eggs\zc.buildout-1.5.2-py2.6.egg\zc\buildout\buildout.py" , line 1141, in _initialize recipe_class = _install_and_load(reqs, 'zc.buildout', entry, buildout) File "d:\home\.buildout\eggs\zc.buildout-1.5.2-py2.6.egg\zc\buildout\buildout.py" , line 1101, in _install_and_load req.project_name, group, entry) File "c:\python26\lib\site-packages\pkg_resources.py", line 318, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "c:\python26\lib\site-packages\pkg_resources.py", line 2221, in load_entry_point return ep.load() File "c:\python26\lib\site-packages\pkg_resources.py", line 1954, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "d:\home\.buildout\eggs\collective.recipe.omelette-0.9-py2.6.egg\collective\ recipe\omelette\__init__.py", line 27, in <module> from collective.recipe.omelette.utils import symlink, unlink, islink, rmtree, WIN32 File "d:\home\.buildout\eggs\collective.recipe.omelette-0.9-py2.6.egg\collective\ recipe\omelette\utils.py", line 23, in <module> raise EnvironmentError, "Junction.exe not found in path. Collective.recipe.omelette cannot continue. See omelette's README.txt." EnvironmentError: Junction.exe not found in path. Collective.recipe.omelette cannot continue. See omelette's README.txt. Regards Roger Ineichen _____________________________ END OF MESSAGE
On 11/21/10 8:16 AM, Roger wrote:
Hi all
The z3c.from buildout process from the trunk is broken. Not sure since when.
Why do we use such crapy parts like omplette in z3c.form? I'm disappointed you find my attempt to at least provide a possibility to use it on Windows, with the help of junction.exe, crappy. That said, it is probably not appropriate in a project development buildout that is meant to be run on Windows.
David Glick Web Developer davidglick@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report
Hi David
Betreff: Re: [Zope-dev] z3c.form buildout broken
On 11/21/10 8:16 AM, Roger wrote:
Hi all
The z3c.from buildout process from the trunk is broken. Not sure since when.
Why do we use such crapy parts like omplette in z3c.form? I'm disappointed you find my attempt to at least provide a possibility to use it on Windows, with the help of junction.exe, crappy. That said, it is probably not appropriate in a project development buildout that is meant to be run on Windows.
I don't know omelette. I just couldn't checkout z3c.form and check if the coverage-report script generation is also broken like in any other package. It seems to be an issue somewhere that prevents to generate a bin/coverage-report script. Don't know why yet. My suggest whould be; Let's move the content of buildout.cfg to a file called base.cfg and extend buildout.cfg without the omelette part. And add another buildout file called omlette.cfg which additional uses the omelette part. This allows to run builtout without the omelette part: bin/buildout and with omelette: bin/buildout -c omelette.cfg I really do not understand why this is not the default concept for omelette based development. Regards Roger Ineichen
---------- David Glick Web Developer davidglick@groundwire.org 206.286.1235x32
Groundwire: You Are Connected http://groundwire.org
Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture
Check out our 2010 Website Benchmarks Report. How do you stack up?
http://groundwire.org/resources/articles/2010-website-benchmar ks-report
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy. Martin
Hi Martin
Betreff: Re: [Zope-dev] z3c.form buildout broken
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy.
Did you know, the world is round not flat, at least outside the collective ;-) Could this work if we move the omelette part to another config file e.g. omelette.cfg and offer 2 hooks for run buildout? Or is there more magic involved and omelette only works if the buildout configuration file is called buildout.cfg? without omelette: bin/buildout and with omelette: bin/buildout -c omelette.cfg Regards Roger Ineichen
Martin
On Sun, Nov 21, 2010 at 09:01:59PM +0000, Martin Aspeli wrote:
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy.
Does it have a bug tracker? I've a small niggling issue with it that I'd like to resolve some day. *checks PyPI* Cool, the description even has a link to the bug tracker. +10 brownie points. Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest to make it optional, since omelette is rarely necessary for development, it's more of a convenience. Print a warning "skipping omelette symlink tree construction because junction.exe is not present in %PATH%" and continue. Just my €0.02. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
Hello, Monday, November 22, 2010, 11:24:27 AM, you wrote: MG> On Sun, Nov 21, 2010 at 09:01:59PM +0000, Martin Aspeli wrote:
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy.
MG> Does it have a bug tracker? I've a small niggling issue with it that MG> I'd like to resolve some day. MG> *checks PyPI* MG> Cool, the description even has a link to the bug tracker. +10 brownie MG> points. MG> Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest to MG> make it optional, since omelette is rarely necessary for development, MG> it's more of a convenience. Print a warning "skipping omelette symlink tree MG> construction because junction.exe is not present in %PATH%" and MG> continue. Just my €0.02. I guess I need to add this and some other packages to the winbot's jobs. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: "Men and nations behave wisely once they have exhausted all the other alternatives." - Abba Eban
Hi Adam
Betreff: Re: [Zope-dev] z3c.form buildout broken
Hello,
Monday, November 22, 2010, 11:24:27 AM, you wrote:
MG> On Sun, Nov 21, 2010 at 09:01:59PM +0000, Martin Aspeli wrote:
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy.
MG> Does it have a bug tracker? I've a small niggling issue with it MG> that I'd like to resolve some day.
MG> *checks PyPI*
MG> Cool, the description even has a link to the bug tracker. +10 MG> brownie points.
MG> Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest MG> to make it optional, since omelette is rarely necessary for MG> development, it's more of a convenience. Print a warning "skipping MG> omelette symlink tree construction because junction.exe is not MG> present in %PATH%" and continue. Just my €0.02.
I guess I need to add this and some other packages to the winbot's jobs.
If we do so, we need to accept collective.recipe.omelette as a core dependency for our ZTK and BlueBream development. That's defently not what I like to do. But of corse the buildbot should fail if there is any for z3c.form. Regards Roger Ineichen
-- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: "Men and nations behave wisely once they have exhausted all the other alternatives." - Abba Eban
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Hello Roger, Monday, November 22, 2010, 2:33:41 PM, you wrote:
I guess I need to add this and some other packages to the winbot's jobs.
R> If we do so, we need to accept collective.recipe.omelette as R> a core dependency for our ZTK and BlueBream development. R> That's defently not what I like to do. But of corse the buildbot R> should fail if there is any for z3c.form. First and top priority would be to have the tests pass on windows too. Some people don't have windows at hand. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: When a deep injury is done us, we never recover until we forgive. - Alan Paton
Hi Marius
Betreff: Re: [Zope-dev] z3c.form buildout broken
On Sun, Nov 21, 2010 at 09:01:59PM +0000, Martin Aspeli wrote:
On 21 November 2010 16:16, Roger <dev@projekt01.ch> wrote:
Why do we use such crapy parts like omplette in z3c.form?
I never do any development whatsoever without collective.recipe.omelette. It may not be right for z3c.form, but it's not crappy.
Does it have a bug tracker? I've a small niggling issue with it that I'd like to resolve some day.
*checks PyPI*
Cool, the description even has a link to the bug tracker. +10 brownie points.
Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest to make it optional, since omelette is rarely necessary for development, it's more of a convenience. Print a warning "skipping omelette symlink tree construction because junction.exe is not present in %PATH%" and continue. Just my €0.02.
You mean adjusting the omplette recipe. Or is there a way to make failing buildout parts optional in z3c.form. I guess not right? Probably an option like "--skip-part omelette" whould be a nice feature for buildout. Regards Roger Ineichen
Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
* "Roger" <dev@projekt01.ch> [2010-11-22 14:30]:
Probably an option like "--skip-part omelette" whould be a nice feature for buildout.
IIRC, when the parts are originally specified on separate lines base.cfg: [buildout] parts = like this omelette #not: parts = like this you can do this: buildout.cfg [buildout] extends = base.cfg parts -= omelette Don't know whether/how you can do that on the command line, though. Wolfgang
Hi Wolfgang
Betreff: Re: [Zope-dev] z3c.form buildout broken
* "Roger" <dev@projekt01.ch> [2010-11-22 14:30]:
Probably an option like "--skip-part omelette" whould be a nice feature for buildout.
IIRC, when the parts are originally specified on separate lines
base.cfg: [buildout] parts = like this omelette #not: parts = like this
you can do this:
buildout.cfg [buildout] extends = base.cfg parts -= omelette
Don't know whether/how you can do that on the command line, though.
Ah, I didn't know that. Then I guess the other side arround whould also work: buildout.cfg: [buildout] parts = like this buildout-omelette.cfg [buildout] extends = base.cfg parts += omelette I was thinking about a command line options like: bin/buildout -c buildout.cfg --skip-parts=omelette Regards Roger Ineichen
On 11/22/10 2:24 AM, Marius Gedminas wrote:
Regarding the 'junction.exe mandatory on Windows' issue, I'd suggest to make it optional, since omelette is rarely necessary for development, it's more of a convenience. Print a warning "skipping omelette symlink tree construction because junction.exe is not present in %PATH%" and continue. Just my €0.02. I think this makes sense, and just released collective.recipe.omelette 0.10 which should give a warning rather than aborting if junction.exe is missing on Windows. David
David Glick Web Developer davidglick@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture Check out our 2010 Website Benchmarks Report. How do you stack up? http://groundwire.org/resources/articles/2010-website-benchmarks-report
participants (6)
-
Adam GROSZER -
David Glick -
Marius Gedminas -
Martin Aspeli -
Roger -
Wolfgang Schnerring