Re: [Zope-dev] Re: bad zope.size to remove from PyPI
On Aug 4, 2008, at 12:37 AM, Aaron Lehmann wrote: On Aug 2, 2008, at 11:45 AM, Chris Withers wrote: 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? If the buildout is nailed to that version or above, and there is none, it breaks. Worse, if someone now adds another egg of the same version, but consumers have cached a version, their buildout won't download it, because it will already have that version in cache. I realize that this particular compound error is unlikely to happen in this instance, but the principle holds. Yes, mistakes happen. What Benji is saying is that deletion is not the right way to remedy them, as unintuitive as that may seem. I do agree that easy_install behavior is pretty insane wrt preferring dev releases over stable old releases. But I think it's pretty reasonable to delete accidental releases, whatever the behavior of setuptools/easy_install/buildout. In the first case you mention where buildout is nailed to that version or above, that would have to be in error, as the release shouldn't have been made in the first place. That also seems true of the second case, but I suppose the difference is the offended person is more innocent there: they should likely contact the person who released it and ask them to not do that again. - C ___ 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 Sun Aug 3 11:00:00 2008 UTC to Mon Aug 4 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: Sun Aug 3 20:56:26 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009955.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Aug 3 20:57:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009956.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Aug 3 20:59:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009957.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Aug 3 21:00:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009958.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Aug 3 21:02:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009959.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 )
[Zope-dev] Re: Zope 3.4 release policy
Benji York wrote: [snip] I also have inclinations to clean up the tests that don't fail, but have other downsides (random confusing output to stderr, not supporting layer teardown). I don't consider them to be release blockers, but I think these would be nice to have in a 3.4.0 final. 3.4.0 is already at rc5, right? If so, I'd be disinclined to do pure refactor-y type things to it. Agreed. I think we should just declare a 3.4.0 at this point. Perfection is nice but we'll never reach it anyway, and it's been a stable base for development for half a year now, so we have quite a bit of validation. Let's start considering 3.4.1 and 3.5. If we get into a habit of releases once every few months (at least bugfix releases) there is less of a reason to hold off on release until things are perfect. Regards, Martijn ___ 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: zope.sqlalchemy dependencies does not respect setup.py dev egg
zope.sqlalchemy specifically requires a SessionExtension hook added in 0.4.7 and 0.5.0b3 to fix a bug that came to light in porting dobbin over to use it: New objects added to a session did not cause a transaction join, so were not committed at the end of the transaction unless the database was accessed. SQLAlchemy 0.4.7 or 0.5beta3 now required. Other than that nothing really changed since 0.2, you should be able to just use that. Laurence David Pratt wrote: 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 ) ___ 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: zope.sqlalchemy dependencies does not respect setup.py dev egg
Hi Laurence. I reverted to 0.2 and I am good to go. I will upgrade to 0.3 when dobbin can use beta0.5.3. Many thanks. Regards, David Laurence Rowe wrote: zope.sqlalchemy specifically requires a SessionExtension hook added in 0.4.7 and 0.5.0b3 to fix a bug that came to light in porting dobbin over to use it: New objects added to a session did not cause a transaction join, so were not committed at the end of the transaction unless the database was accessed. SQLAlchemy 0.4.7 or 0.5beta3 now required. Other than that nothing really changed since 0.2, you should be able to just use that. Laurence David Pratt wrote: 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 ) ___ 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 )
Re: [Zope-dev] Re: Zope 3.4 release policy
Martijn Faassen a écrit : Benji York wrote: [snip] I also have inclinations to clean up the tests that don't fail, but have other downsides (random confusing output to stderr, not supporting layer teardown). I don't consider them to be release blockers, but I think these would be nice to have in a 3.4.0 final. 3.4.0 is already at rc5, right? If so, I'd be disinclined to do pure refactor-y type things to it. Agreed. I think we should just declare a 3.4.0 at this point. Perfection is nice but we'll never reach it anyway, and it's been a stable base for development for half a year now, so we have quite a bit of validation. Let's start considering 3.4.1 and 3.5. If we get into a habit of releases once every few months (at least bugfix releases) there is less of a reason to hold off on release until things are perfect. We should at least include all the existing bugfix releases, because there are some important ones. We don't need it to be called rc6, but 3.4.0 directly. 3.4.0c6 (unreleased) - Upgraded zope.publisher to 3.4.3. - Upgraded zope.app.authentication to 3.4.2. Removed previous versions, as they are not compatible with zope.app.container = 3.5.4 - Upgraded zope.app.container to 3.5.5 - Upgraded zope.testing 3.5.1 to 3.5.4. - Upgraded zc.buildout 1.0.0 to 1.1.1. What are we doing for the changelog of zope.release? Should we finally merge KGS-HISTORY.txt into CHANGES.txt or leave both files as is ? Christophe Regards, Martijn ___ 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 )
Re: [Zope-dev] Re: Zope 3.4 release policy
On Monday 04 August 2008, Christophe Combelles wrote: What are we doing for the changelog of zope.release? Should we finally merge KGS-HISTORY.txt into CHANGES.txt or leave both files as is ? I am okay with the merge (did this for the trunk already), and not record software changes at all. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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] bad zope.size to remove from PyPI
I've found another one, detected by zope.release's list-latest: http://pypi.python.org/pypi/zope.app.externaleditor/3.4.0-r81494 But it seems hidden in pypi. Christophe Combelles a écrit : Hi, 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) Christophe ___ 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.authorizedotnet
Hi, I'm looking for zc.authorizedotnet developers... zvezdan, alga, gary are package index owners at pypi, but this is the only mail listed... I have some changes to support authorized.net ARB mode. I made it as part of GetPaid development (http://code.google.com/p/getpaid/ ) and now we must make a decision, give you a patch so you can include it in the next release or make a vendor branch for your package in our svn... Thanks, Juan Pablo Giménez ___ 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] zc.authorizedotnet
Hi Juan. Certainly we'd hate to see an unnecessary fork. Are you a Zope Contributor? I don't keep up with all the preferred mechanisms for external contributors, so we'll ask around if not. You'll have to make some license assignments (to Zope Foundation and contributors, I believe) and assertions (Zope Public License). We would want tests for the changes, of course. Thanks Gary On Aug 4, 2008, at 5:51 PM, Juan Pablo Gimenez wrote: Hi, I'm looking for zc.authorizedotnet developers... zvezdan, alga, gary are package index owners at pypi, but this is the only mail listed... I have some changes to support authorized.net ARB mode. I made it as part of GetPaid development (http://code.google.com/p/getpaid/ ) and now we must make a decision, give you a patch so you can include it in the next release or make a vendor branch for your package in our svn... Thanks, Juan Pablo Giménez ___ 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 )
