I fixed the unit tests of the zope.interface package, which were broken by the last release of zope.testing. Can somebody make a release, or give me access to the PyPI package? My nickname is kobold. Best regards. Fabio
On Tue, Dec 22, 2009 at 10:48 PM, Fabio Tranchitella <kobold@kobold.it> wrote:
I fixed the unit tests of the zope.interface package, which were broken by the last release of zope.testing. Can somebody make a release, or give me access to the PyPI package? My nickname is kobold.
I'd rather see a new zope.testing release fixing the BBB foul, which is much less hassle. zope.interface has C extensions and thus a new release needs all the Windows binary eggs to be made again. Hanno
* 2009-12-22 22:54, Hanno Schlichting wrote:
I'd rather see a new zope.testing release fixing the BBB foul, which is much less hassle.
Isn't the new release emitting a deprecation warning? In this case, I'd fix zope.interface (and all the other packages).
zope.interface has C extensions and thus a new release needs all the Windows binary eggs to be made again.
Not a big issue, I can prepare all the Window eggs if this is thee problem; by the way, i checked out your releases (zope.schema, zope.location, zope.configuration) and the source package is released as a zip file: is there a policy for using tarballs for ZTK packages or it is okey to use zip files, too? Thanks, Fabio
On Tue, Dec 22, 2009 at 11:03 PM, Fabio Tranchitella <kobold@kobold.it> wrote:
* 2009-12-22 22:54, Hanno Schlichting wrote: Isn't the new release emitting a deprecation warning? In this case, I'd fix zope.interface (and all the other packages).
I'm not sure. I only work against the ZTK, which doesn't use the misbehaving zope.testing yet.
zope.interface has C extensions and thus a new release needs all the Windows binary eggs to be made again.
Not a big issue, I can prepare all the Window eggs if this is thee problem;
Ok, I've given you PyPi access to zope.interface :-)
by the way, i checked out your releases (zope.schema, zope.location, zope.configuration) and the source package is released as a zip file: is there a policy for using tarballs for ZTK packages or it is okey to use zip files, too?
We just had that debate a couple days ago. We concluded that using both tar.gz and zip are fine for source releases. Only bzip2 is forbidden, as it's not available on all platforms. Hanno
On Tue, Dec 22, 2009 at 10:54:18PM +0100, Hanno Schlichting wrote:
On Tue, Dec 22, 2009 at 10:48 PM, Fabio Tranchitella <kobold@kobold.it> wrote:
I fixed the unit tests of the zope.interface package, which were broken by the last release of zope.testing. Can somebody make a release, or give me access to the PyPI package? My nickname is kobold.
I'd rather see a new zope.testing release fixing the BBB foul, which is much less hassle.
Releasing 3.8.5 now.
zope.interface has C extensions and thus a new release needs all the Windows binary eggs to be made again.
I wish it were possible to cross-compile those on Linux. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On 2009-12-23, at 0624, Marius Gedminas wrote:
Releasing 3.8.5 now.
…and it's broken. The testrunner directory isn't included in the tarball so egg_info fails. In addition, the PyPI page has been destroyed because of a ReST syntax error somewhere. Matt
On Wed, Dec 23, 2009 at 06:34:17AM +0000, Matthew Wilkes wrote:
On 2009-12-23, at 0624, Marius Gedminas wrote:
Releasing 3.8.5 now.
…and it's broken. The testrunner directory isn't included in the tarball so egg_info fails.
Gah, setuptools claims another victim! I must be using a version that doesn't support svn 1.6 working dirs. :( Can we please have a check for that in zest.releaser?
In addition, the PyPI page has been destroyed because of a ReST syntax error somewhere.
That's been happening before, check out http://pypi.python.org/pypi/zope.testing/3.8.4 and this bug I filed yesterday: https://sourceforge.net/tracker/?func=detail&aid=2919627&group_id=66150&atid... Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
Hello Marius, Wednesday, December 23, 2009, 8:03:31 AM, you wrote: MG> Gah, setuptools claims another victim! I must be using a version that MG> doesn't support svn 1.6 working dirs. :( yah. But it seems to get it right after a bin/buildout. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: This screen intentionally left blank.
On 12/23/09 8:03 AM, Marius Gedminas wrote:
On Wed, Dec 23, 2009 at 06:34:17AM +0000, Matthew Wilkes wrote:
On 2009-12-23, at 0624, Marius Gedminas wrote:
Releasing 3.8.5 now.
…and it's broken. The testrunner directory isn't included in the tarball so egg_info fails.
Gah, setuptools claims another victim! I must be using a version that doesn't support svn 1.6 working dirs. :(
Can we please have a check for that in zest.releaser?
A check for that? Seems sensible. I'm not getting around to do that (last two days in my current job; laptopless in the weekend) in the next few days, though. Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets"
participants (6)
-
Adam GROSZER -
Fabio Tranchitella -
Hanno Schlichting -
Marius Gedminas -
Matthew Wilkes -
Reinout van Rees