Re: [Zope-dev] [Checkins] SVN: zopetoolkit/doc/source/releaseteam/ minutes of ztk releaseteam meeting 11/09
On 11/18/10 11:16 , Jan-Wijbrand Kolman wrote:
+The ZTK would like to use distribute by default.
Is the distribute project still alive? The reason I ask is that my recent experience is that bugs reported in setuptools are fixed very quickly, while there is no response from the distribute team. Wichert.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/18/2010 05:19 AM, Wichert Akkerman wrote:
On 11/18/10 11:16 , Jan-Wijbrand Kolman wrote:
+The ZTK would like to use distribute by default.
Is the distribute project still alive? The reason I ask is that my recent experience is that bugs reported in setuptools are fixed very quickly, while there is no response from the distribute team.
It does look as though development velocity on 'distribute' has slowed to a pace quite comparable to setuptools, with setuptools having the more recent release. The two trackers are at: http://bitbucket.org/tarek/distribute/issues?status=open&status=new&kind=bug... http://bugs.python.org/setuptools/ The bitbucket UI doesn't show recency of issue activity, which would make the two easier to compare. I'm -1 on preferring 'distribute' in any overt way in the ZTK. Folks who want it can already use it when bootstrapping a buildout:: $ /path/to/python bootstrap.py --distribute or when creating a virtualenv:: $ /path/to/virtualenv --no-site-packages --distribute envdir The ZTK should not grow any creeping dependencies on 'distribute'. 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzlSzUACgkQ+gerLs4ltQ5ojwCghD2OXQUiQPcDWbxsCRe4D+5m KXQAn1wAFcskUdV4Ls8UBtX739tXyDmf =IgjS -----END PGP SIGNATURE-----
On 11/18/10 16:50 , Tres Seaver wrote:
I'm -1 on preferring 'distribute' in any overt way in the ZTK. Folks who want it can already use it when bootstrapping a buildout::
+1 (on your -1) Wichert.
On 11/18/10 16:50 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/18/2010 05:19 AM, Wichert Akkerman wrote:
On 11/18/10 11:16 , Jan-Wijbrand Kolman wrote:
+The ZTK would like to use distribute by default.
Is the distribute project still alive? The reason I ask is that my recent experience is that bugs reported in setuptools are fixed very quickly, while there is no response from the distribute team.
It does look as though development velocity on 'distribute' has slowed to a pace quite comparable to setuptools, with setuptools having the more recent release. The two trackers are at:
http://bitbucket.org/tarek/distribute/issues?status=open&status=new&kind=bug...
http://bugs.python.org/setuptools/
The bitbucket UI doesn't show recency of issue activity, which would make the two easier to compare.
I'm -1 on preferring 'distribute' in any overt way in the ZTK. Folks who want it can already use it when bootstrapping a buildout::
I'll make sure this is put back on the ztk release team agenda. Note though that there was no intention to introduce "creeping" dependencies on distribute other than preferring it over setuptools. I guess we had the idea distribute was still all the rage. The Grok project also got a few reports of strange, hard to reproduce installation problems (shutil not importable in some weird way for example), when people were using setuptools (in combination with a virtualenv, and zc.buildout 1.5.2) that were gone when they tried with the distribute option. regards, jw
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/19/2010 03:20 AM, Jan-Wijbrand Kolman wrote:
On 11/18/10 16:50 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/18/2010 05:19 AM, Wichert Akkerman wrote:
On 11/18/10 11:16 , Jan-Wijbrand Kolman wrote:
+The ZTK would like to use distribute by default.
Is the distribute project still alive? The reason I ask is that my recent experience is that bugs reported in setuptools are fixed very quickly, while there is no response from the distribute team.
It does look as though development velocity on 'distribute' has slowed to a pace quite comparable to setuptools, with setuptools having the more recent release. The two trackers are at:
http://bitbucket.org/tarek/distribute/issues?status=open&status=new&kind=bug...
http://bugs.python.org/setuptools/
The bitbucket UI doesn't show recency of issue activity, which would make the two easier to compare.
I'm -1 on preferring 'distribute' in any overt way in the ZTK. Folks who want it can already use it when bootstrapping a buildout::
I'll make sure this is put back on the ztk release team agenda.
Note though that there was no intention to introduce "creeping" dependencies on distribute other than preferring it over setuptools. I guess we had the idea distribute was still all the rage.
The Grok project also got a few reports of strange, hard to reproduce installation problems (shutil not importable in some weird way for example), when people were using setuptools (in combination with a virtualenv, and zc.buildout 1.5.2) that were gone when they tried with the distribute option.
AFAIK, zc.buildout >= 1.5 is still flaky when used with a virtualenv, which saddens me: it damaged a feature I frequently used (virtualenv compatibilty) in order to pursue one I strongly dislike (use with a system python). 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzmiSIACgkQ+gerLs4ltQ6NhgCdFc4XrsjJGe6Ap+eN8OQvEB6T X00AnjKRnENEF6x2P2fSfv6BldoLKOIh =qqlK -----END PGP SIGNATURE-----
participants (3)
-
Jan-Wijbrand Kolman -
Tres Seaver -
Wichert Akkerman