[Zope-dev] zope.sqlalchemy dependencies does not respect setup.py dev egg
Hi. I have been working with z3c.dobbin 0.4.1 which uses zope.sqlalchemy and z3c.saconfig. The last usable state was 4 days ago when changes were made to release of zope.sqlalchemy where dependencies were changed without changing the version. Revision 88953 was made to zope.sqlalchemy but shows the same package version as 88952 (where SA dependencies were changed to no longer include beta0.5.2). beta0.5.2 was the requirement for z3c.dobbin and it will not work with beta0.5.3. Malthe is currently making changes to dobbin in the interim so it will eventually work again. I thought by checking out revision 88952 and using it as a dev egg in my buildout, I could get back to work. Is this a bug in buildout since dev egg should take precedence regardless? I guess there were some problems with how this was handled. If trunk had been marked as 0.3dev it might have made the difference because both were 0.3 regardless of the change of state and dependencies. When I run the buildout the dev egg's requires.txt is below regardess of what is in setup.py. Doesn't matter what I do my build fails. Any suggestions? Many thanks. Regards, David requires.txt setuptools SQLAlchemy>=0.4.7,!=0.5.0beta1,!=0.5.0beta2 transaction zope.interface [test] zope.testing docutils setup.py install_requires=[ 'setuptools', 'SQLAlchemy==0.5.0beta2', # or >=0.5b3 'transaction', 'zope.interface', ], ___ 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: bad "zope.size" to remove from PyPI
On Sat, Aug 2, 2008 at 9:27 AM, Benji York <[EMAIL PROTECTED]> wrote: > Still, it's likely that someone was using it and their buildouts are now > broken. We should have instead generated a proper release with a higher > version number and left the dev release alone. Yes. It would be even better if PyPI refused registrations of dev versions. -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ 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: bad "zope.size" to remove from PyPI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: > El 2 Aug 2008, a las 17:45 , Chris Withers escribió: >> Benji York wrote: In case anybody's wondering how this complies with our "no removal of any release whatsoever" policy [1], be assured that a 3.4dev-r73090 thing isn't a release by our standards. This version number not only contains the 'dev' marker, meaning it must have come from a development branch (possibly the trunk), it also contains the -rXXX suffix meaning it was made right from a subversion checkout without having created a tags first (why else would you want to include the revision number). >>> Still, it's likely that someone was using it and their buildouts >>> are now >>> broken. We should have instead generated a proper release with a >>> higher >>> version number and left the dev release alone. >> This is silly. >> >> Mistakes happen. Buildout and/or setuptools should be tolerant of >> accidental releases that are then removed from PyPI. >> >> What currently happens in cases like this? > > Nothing. It's only a problem if somebody pinned zope.size version to > 3.4dev-r73090 in their buildout.cfg. But that's their own fault IMHO > because it's clearly not a release. We ought to look at yanking PyPI privileges for anybody who is pushing such eggs out. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIlLRY+gerLs4ltQ4RAieGAKDaDX6HX+xZZMA4sVGX6YbpoCVFLQCfW5gY 4AZZlvIHyyTx2uGZvJrYp8E= =WSJT -END PGP SIGNATURE- ___ 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: bad "zope.size" to remove from PyPI
El 2 Aug 2008, a las 17:45 , Chris Withers escribió: Benji York wrote: In case anybody's wondering how this complies with our "no removal of any release whatsoever" policy [1], be assured that a 3.4dev-r73090 thing isn't a release by our standards. This version number not only contains the 'dev' marker, meaning it must have come from a development branch (possibly the trunk), it also contains the -rXXX suffix meaning it was made right from a subversion checkout without having created a tags first (why else would you want to include the revision number). Still, it's likely that someone was using it and their buildouts are now broken. We should have instead generated a proper release with a higher version number and left the dev release alone. This is silly. Mistakes happen. Buildout and/or setuptools should be tolerant of accidental releases that are then removed from PyPI. What currently happens in cases like this? Nothing. It's only a problem if somebody pinned zope.size version to 3.4dev-r73090 in their buildout.cfg. But that's their own fault IMHO because it's clearly not a release.___ 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: bad "zope.size" to remove from PyPI
Benji York wrote: In case anybody's wondering how this complies with our "no removal of any release whatsoever" policy [1], be assured that a 3.4dev-r73090 thing isn't a release by our standards. This version number not only contains the 'dev' marker, meaning it must have come from a development branch (possibly the trunk), it also contains the -rXXX suffix meaning it was made right from a subversion checkout without having created a tags first (why else would you want to include the revision number). Still, it's likely that someone was using it and their buildouts are now broken. We should have instead generated a proper release with a higher version number and left the dev release alone. This is silly. Mistakes happen. Buildout and/or setuptools should be tolerant of accidental releases that are then removed from PyPI. What currently happens in cases like this? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ 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: bad "zope.size" to remove from PyPI
On Fri, Aug 1, 2008 at 7:03 PM, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: > Christophe Combelles wrote: >> >> could someone remove this package from the PyPI : >> http://pypi.python.org/pypi/zope.size/3.4dev-r73090 >> >> This is an empty development version, considered more recent by PyPI than >> the latest released version 3.4.0. (which is r78211) > > Done. > > In case anybody's wondering how this complies with our "no removal of any > release whatsoever" policy [1], be assured that a 3.4dev-r73090 thing isn't > a release by our standards. This version number not only contains the 'dev' > marker, meaning it must have come from a development branch (possibly the > trunk), it also contains the -rXXX suffix meaning it was made right from a > subversion checkout without having created a tags first (why else would you > want to include the revision number). Still, it's likely that someone was using it and their buildouts are now broken. We should have instead generated a proper release with a higher version number and left the dev release alone. -- Benji York Senior Software Engineer Zope Corporation ___ 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] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Fri Aug 1 11:00:00 2008 UTC to Sat Aug 2 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 1 20:55:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009945.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 1 20:57:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009946.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 1 20:58:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009947.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 1 21:00:06 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009948.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 1 21:01:36 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009949.html ___ 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 )
