Re: [Zope-dev] i18nmessageid has a broken link
On May 9, 2008, at 9:37 AM, Sebastian Wehrmann wrote: the zope.i18nmessageid package has a broken link on http://download.zope.org/zope3.4/zope.i18nmessageid/ . The 'zope.i18nmessageid-3.4.3-py2.4-linux-i686.egg' does not exist any more on pypi. Could someone please fix it? This egg was deliberately removed. I don't know the whole story about pypi and zope so I wouldn't dare to remove the egg myself, but it was removed. If I easy_install zope.i18nmessageid on my Mac I will get that linux specific egg. That egg won't work on my computer. So I asked those who know more about this and they say that only windows eggs are allowed to be binary, the rest should be source eggs. That makes sense to me. It looks like you work for gocept? Christian Theune was also saying that this egg shouldn't be on pypi, so you could talk to your colleague :) Why do you need this linux specific egg anyway? /Tim ___ 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] pinning, nailing and kgs'ing
On Feb 3, 2008, at 3:35 AM, Kevin Teague wrote: I wanted to try using the snowsprint-viewlets2 branch of grok in my project the other day. It took me a little time to figure out how to do this, so I thought it'd be nice if there was a bit of documentation on how-to pull in a development version of Grok into a grok project, so I wrote this: http://grok.zope.org/documentation/how-to/trail-blazing I couldn't access this page. The easiest way to use grok trunk/branch is to use svn:externals and change a few lines in buildout.cfg [buildout] develop = . src/grok src/grok/martian [versions] martian = and put this in svn:externals for src/ grok svn://svn.zope.org/repos/main/grok/branches/snowsprint-viewlets2 Anyways, I hope I don't sound too complain-y, but it would be much appreciated if the terminology and plan for maintaining the Zope 3.4 release series was made a bit clearer. And it would also be really nice if the Grok terminology and release methods lined up with the Zope 3 terminology and release methods :) Grok should use KGS. Someone just needs to do the work. /Tim ___ 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] zopeproject and eggs lead to wrong zopeversion
On Nov 26, 2007, at 2:28 PM, Philipp von Weitershausen wrote: Christophe Combelles wrote: Hello, An full-egg zope 3.4 buildout installed with zopeproject tells me the zope version is 3.3.1 (in /++etc++process/): - I have a fully eggified zope 3.4 installed with zopeproject. - I also have a zope 3.3.1 installed on the system python. When I start the 3.4 full-egg instance, I've discovered that zope.app.applicationcontrol.zopeversion tries to reach zope/app/ version.txt to determine the major zope version. Since version.txt does not seem to be included in any egg, it fallbacks to the system zope installed. system zope? It seems like you have a globally available Zope installation. This will obviously confuse any *local* sandbox, such as the one created with zopeproject. Make sure you don't have any Zope libraries on your standard PYTHONPATH. Wouldn't it make sense if zopeproject didn't include system python in PYTHONPATH at all? /Tim ___ 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] z3c.rml svn checkout
This tells you how to use the svn repository: http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ /Tim On Nov 1, 2007, at 1:44 PM, Catalin Constantin wrote: Hello I am trying to checkout latest version of z3c.rml and i get the following error: svn co http://svn.zope.org/z3c.rml/ z3c.rml svn: PROPFIND request failed on '/z3c.rml' svn: PROPFIND of '/z3c.rml': 301 Moved (http://svn.zope.org) Thanks, -- Catalin Constantin ___ 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 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] zc.buildout installing parts not asked for
When using zc.buildout I discovered that it installed a part that I
didn't
specify in the 'parts' option. This happened because I referenced this
part somewhere else. Is this how it's supposed to be? I would prefer
if it
only installs the parts I specify in parts. I don't see anything
wrong with
reusing options from a part that I don't necessarily want to install.
This is a buildout.cfg that will reproduce it. The 'notusedinparts'
part is
installed even if not specified in 'parts'. It's installed because of
the
'dummy' option in the 'tok' section. Is this how it was meant to be?
[buildout]
develop = recipes
parts = tok
[tok]
recipe = recipes:debug
dummy = ${notusedinparts:someoption}
[notusedinparts]
recipe = recipes:debug
someoption = why
/Tim
ps. I tried to send this to the distutils-sig list, but it got stuck
in mailman
saying Message has a suspicious header and it doesn't look like
anyone wants to approve the email, so I'm trying here instead.
___
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 )
