Re: [Zope3-dev] zc.buildout and develop-eggs
Hey, Am Mittwoch, den 02.05.2007, 09:36 -0400 schrieb Jim Fulton: On May 2, 2007, at 9:31 AM, Michael Howitz wrote: Am 02.05.2007 um 15:12 schrieb Jim Fulton: Assuming that you have a checkout of the trunk zc.form, then you are mistaken. The version number in the setup.py file: http://svn.zope.org/zc.form/trunk/setup.py?view=auto is 0.1dev. This is before 0.1dev-r74753 and thus doesn't satisfy the requirement zc.form=0.1dev-r74753. If you aren't using the trunk of zc.form, you should share what version you are using. I'm using the trunk of zc.form. So I thought the trunk should be counted as newer as each snapshot release. You thought wrong. Well. It definitely should be. Reading the setuptools documentation again it becomes obvious how the version numbering scheme has to be used to make that happen: Note: the project version number you specify in setup.py should always be the next version of your software, not the last released version. So, the trunk's version in setup.py should be 0.1 in this case. Making a snapshot release would be done using:: $ python setup.py egg_info -rb.dev sdist This results in the egg being labeled: project-0.1.dev-r1234 Now, a develop egg would be version 0.1 which is represented by the trunk, just not released yet. And any snapshot will have the pre-release tag dev and the post-release tags given by the subversion revision. IMHO we should take care arranging our setup.py files in this way. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zc.buildout and develop-eggs
On May 2, 2007, at 7:30 AM, Michael Howitz wrote: Hi, I discovered an unecpected behavior ob zc.buildout: I have a package which depends in its setup.py on zc.form=0.1dev- r74753. In my buildout.cfg I decaled zc.form as a develop-egg by pointing to its svn-checkout. The problem is that the zope start script generated by buildout does not contain the path of the development egg but of the released egg. If I remove the version requirement and depend from zc.form (with out a version declaration) then the devlopment egg is in the path. Is this a bug in zc.buildout or expected behavior? It is expected behavior. buildout will always prefer a develop egg that meets the given requirements. My guess is that 0.1dev-r74753 is later than the version given in setup.py. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zc.buildout and develop-eggs
Am 02.05.2007 um 14:43 schrieb Jim Fulton: [...] It is expected behavior. buildout will always prefer a develop egg that meets the given requirements. I wanted to point out that in my case this is not true. buildout preferes the released egg if it required with a minimum version. Without this version declaration the develop egg is preferred. So, when I depend on zc.form=0.1dev-r74753 the egg of the release is preferred (and put into path) instead of the develop egg. If I depend on zc.form the develop egg is preferred. Hope this makes my problem a bit clearer. Yours sincerely, Michael Howitz gocept gmbh co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon: +49 345 12298898 · fax: +49 345 12298891 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zc.buildout and develop-eggs
On May 2, 2007, at 9:31 AM, Michael Howitz wrote: Am 02.05.2007 um 15:12 schrieb Jim Fulton: Assuming that you have a checkout of the trunk zc.form, then you are mistaken. The version number in the setup.py file: http://svn.zope.org/zc.form/trunk/setup.py?view=auto is 0.1dev. This is before 0.1dev-r74753 and thus doesn't satisfy the requirement zc.form=0.1dev-r74753. If you aren't using the trunk of zc.form, you should share what version you are using. I'm using the trunk of zc.form. So I thought the trunk should be counted as newer as each snapshot release. You thought wrong. So the expectation that develop eggs are used when ty are declared seems to be wrong. Right. But then the only way to use develop eggs and declare egg versions in dependencies is to have a always a higher version in svn trunk than each existing snapshot release. Or to declare your requirements more carefully. The only way to use develop eggs is to make sure that they satisfy any requirements you provide. I don't think this is so good. I'm sorry you feel that way. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
