Hi, Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ? PEP 8: A Foolish Consistency is the Hobgoblin of Little Minds Regards, Baiju M
On 2009-12-16 08:35, Baiju M wrote:
Hi, Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Once there is a python 2.4 release which fixes the tarfile bug, or once python 2.4 support is officially no longer desirable. Wichert. -- Wichert Akkerman <wichert@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote:
On 2009-12-16 08:35, Baiju M wrote:
Hi, Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Once there is a python 2.4 release which fixes the tarfile bug,
That release is scheduled for February 31st next year. :)
or once python 2.4 support is officially no longer desirable.
In practice, the tarfile bug only affects a very small percentage of packages (they need to contain a file member with a '/' character in the 100th position in its name). Anybody who builds a package which generates such a name will just (eventually, anyway) figure out to use zipfile: for everybody else, the distinction is meaningless. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkspVvUACgkQ+gerLs4ltQ77egCfWaAre4U2rDJGtik2PcdSn34k ER8AniYMarNcjsKoKeK2nEYRPM0zofdK =WRT/ -----END PGP SIGNATURE-----
On Wed, Dec 16, 2009 at 04:53:58PM -0500, Tres Seaver wrote:
Wichert Akkerman wrote:
On 2009-12-16 08:35, Baiju M wrote:
Hi, Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Once there is a python 2.4 release which fixes the tarfile bug,
That release is scheduled for February 31st next year. :)
or once python 2.4 support is officially no longer desirable.
In practice, the tarfile bug only affects a very small percentage of packages (they need to contain a file member with a '/' character in the 100th position in its name). Anybody who builds a package which generates such a name will just (eventually, anyway) figure out to use zipfile: for everybody else, the distinction is meaningless.
Could someone remind me if the bug happens during packing (and breaks the .tgz for everyone, which gets noticed and fixed soon) or during unpacking (and affects only a small percentage of users; those who still use python 2.4, and is therefore more insidious)? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Thu, Dec 17, 2009 at 9:53 PM, Marius Gedminas <marius@gedmin.as> wrote:
Could someone remind me if the bug happens during packing (and breaks the .tgz for everyone, which gets noticed and fixed soon) or during unpacking (and affects only a small percentage of users; those who still use python 2.4, and is therefore more insidious)?
It only happens on unpacking. So the person making the tgz usually won't ever notice and only get mysterious reports about broken installs later on. Hanno
Hi there, Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Which are the exceptions? Regards, Martijn
Hello Martijn, I guess which were created by windowze people. It does zips by default. Wednesday, December 16, 2009, 3:39:00 PM, you wrote: MF> Hi there, MF> Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
MF> Which are the exceptions? MF> Regards, MF> Martijn MF> _______________________________________________ MF> Zope-Dev maillist - Zope-Dev@zope.org MF> https://mail.zope.org/mailman/listinfo/zope-dev MF> ** No cross posts or HTML encoding! ** MF> (Related lists - MF> https://mail.zope.org/mailman/listinfo/zope-announce MF> https://mail.zope.org/mailman/listinfo/zope ) -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Faith affirms what the senses do not affirm, but not the contrary of what they perceive. It is above and not contrary to. - Blaise Pascal
On Wed, Dec 16, 2009 at 4:40 PM, Adam GROSZER <agroszer@gmail.com> wrote:
I guess which were created by windowze people. It does zips by default.
Nope. I only create zips being on Mac OS. With the tarfile module in Python 2.4 being utterly broken, I ran into too much trouble with broken tar.gzips over time. At least in the Plone world we demanded everyone to use zip files all the time as the sdist format. We haven't enforced that, though. Hanno
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 schrieb Hanno Schlichting:
On Wed, Dec 16, 2009 at 4:40 PM, Adam GROSZER <agroszer@gmail.com> wrote:
I guess which were created by windowze people. It does zips by default.
Nope. I only create zips being on Mac OS.
With the tarfile module in Python 2.4 being utterly broken, I ran into too much trouble with broken tar.gzips over time.
At least in the Plone world we demanded everyone to use zip files all the time as the sdist format. We haven't enforced that, though. +0.5
At least I would disallow .bz2 since most people don't have a Python interpreter with bz2 module installed. Andreas - -- ZOPYX Ltd. & Co KG \ zopyx group Charlottenstr. 37/1 \ The full-service network for your D-72070 Tübingen \ Python, Zope and Plone projects www.zopyx.com, info@zopyx.com \ www.zopyxgroup.com - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkspAUkACgkQCJIWIbr9KYyMcwCfZ9+DHuqTkpCTJEewrCeTCZVr +UkAn3Eyf4bW+qXwg8XVOJ3a4dalXG3h =XtMT -----END PGP SIGNATURE-----
On Wed, Dec 16, 2009 at 8:09 PM, Martijn Faassen <faassen@startifact.com> wrote:
Hi there,
Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Which are the exceptions?
I just checked the "included" ZTK packages, here is the list: zope.container-3.9.1.zip zope.container-3.10.0.zip zope.contenttype-3.4.2.zip zope.copypastemove-3.4.1.zip zope.dublincore-3.4.1.zip zope.error-3.5.0.zip zope.formlib-3.5.0.zip zope.formlib-3.5.2.zip zope.html-2.0.0.zip zope.html-1.2.0.zip zope.i18n-3.7.1.zip zope.i18n-3.6.0.zip zope.i18nmessageid-3.4.2.zip zope.interface-3.5.0.zip zope.keyreference-3.6.2.zip zope.proxy-3.4.0.zip zope.proxy-3.4.1.zip zope.proxy-3.4.2.zip zope.publisher-3.3.3.zip zope.publisher-3.6.0.zip zope.publisher-3.6.1.zip zope.publisher-3.6.4.zip zope.publisher-3.11.0.zip zope.ramcache-1.0.zip zope.security-3.5.2.zip zope.security-3.4.1.zip zope.sendmail-3.5.1.zip zope.server-3.6.0.zip zope.session-3.9.1.zip zope.site-3.8.0.zip zope.tal-3.5.2.zip zope.testbrowser-3.7.0a1.zip zope.testing-3.8.2.zip zope.traversing-3.7.2.zip zope.traversing-3.5.3.zip zope.traversing-3.10.0.zip zope.traversing-3.9.0.zip zope.viewlet-3.5.0.zip zope.viewlet-3.6.1.zip Regards, Baiju M
On Wed, Dec 16, 2009 at 08:35, Baiju M <mbaiju@zeomega.com> wrote:
Hi, Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Why do we need consistency? I mostly use tgz, but that's only because I forget that I should use zip. :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64
Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Why does anyone care? They both work the same on all platforms... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Wed, Dec 16, 2009 at 9:23 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ?
Why does anyone care? They both work the same on all platforms...
Others has already raised their concern against .tar.gz as it is not working in Python 2.4 And bz2 module might be missing for many Python installations. (BTW, We don't have any bz2 source packages released) Regards, Baiju M
On Wed, Dec 16, 2009 at 17:31, Baiju M <mbaiju@zeomega.com> wrote:
Others has already raised their concern against .tar.gz as it is not working in Python 2.4
And bz2 module might be missing for many Python installations. (BTW, We don't have any bz2 source packages released)
Right. So for consistency we should use zip. Then again, I'm don't see why we would want to be consistent. :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Baiju M wrote:
On Wed, Dec 16, 2009 at 9:23 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ? Why does anyone care? They both work the same on all platforms...
Others has already raised their concern against .tar.gz as it is not working in Python 2.4
It doesn't affect the huge majority of pacakges we produce. For any package it does affect, we use zip, sure.
And bz2 module might be missing for many Python installations. (BTW, We don't have any bz2 source packages released)
That still doesn't require consitency: we just need to test that the packages we make can be installed on all supported platforms. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkspV2UACgkQ+gerLs4ltQ5+hwCgn5ABDO3+M8jL3NJO5VA8Zw1Z gKYAn0nlRUWoAvtf4xum0jpTFRtvKPII =623s -----END PGP SIGNATURE-----
Baiju M wrote:
On Wed, Dec 16, 2009 at 9:23 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Most of the source distribution packages of ZTK are in .tar.gz format. But there are few exceptions. For consistency, can we use .tar.gz format for all releases ? Why does anyone care? They both work the same on all platforms...
Others has already raised their concern against .tar.gz as it is not working in Python 2.4
And bz2 module might be missing for many Python installations.
I suggest we stick to the status quo for the time being then (zip and tgz, no bz2). If matters are fixed in Python 2.5 we should look into dropping Python 2.4 support again sometime in the near future. Regards, Martijn
participants (10)
-
Adam GROSZER -
Andreas Jung -
Baiju M -
Chris Withers -
Hanno Schlichting -
Lennart Regebro -
Marius Gedminas -
Martijn Faassen -
Tres Seaver -
Wichert Akkerman