On 5 Oct, 2009, at 13:54, Tarek Ziadé wrote:
On Mon, Oct 5, 2009 at 1:30 PM, Ronald Oussoren ronaldousso...@mac.com
wrote:
Nobody will adopt it until they are forced to. This unfortunate bug
means people are forced to quicker than expected. I don't think
that's
an actual problem.
This
Tarek Ziadé wrote:
The proper answer is : Setuptools is on the top of Distutils and has
to evolve with it.
And since it monkey patches it, it has to be changed when a Distutils
release breaks it.
I want to note that the issue here is not monkey-patching, it is
subclassing the command classes.
P.J. Eby kirjoitti:
At 11:53 AM 10/5/2009 +0200, Lennart Regebro wrote:
2009/10/5 Jeff Rush j...@taupro.com:
Very unfortunate, as in, it should NOT have happened. And
*especially*
without any announcement on python.org or mention on the
python-committers list of something this major.
K. Richard Pixley wrote:
Alex Grönholm wrote:
There is a lack of consensus regarding how exactly they should work.
If we are having this much trouble deciding how a third party tool
should work, it is certainly not going to be merged into distutils
until those issues have been resolved.
An update on the immediate issue: after discussion elsewhere, it was
decided that there were enough other problems with 2.6.3 to warrant a
quick release of 2.6.4. Tarek has checked in a change to distutils to
unbreak the setuptools currently out in the field. If all goes well,
2.6.4 should
kiorky wrote:
Hi,
for the folks using virtualenv-distribute, i forked it to make the last 0.6.3
install instead of 0.6.1.
See :
http://bitbucket.org/kiorky/virtualenv-distribute/
Install it:
easy_install
2009/10/6 Chris Withers ch...@simplistix.co.uk:
kiorky wrote:
Hi,
for the folks using virtualenv-distribute, i forked it to make the last
0.6.3
install instead of 0.6.1.
See :
http://bitbucket.org/kiorky/virtualenv-distribute/
Install it:
easy_install
2009/10/6 Lennart Regebro rege...@gmail.com:
I think it's a fork of Virtualenv, no? Which uses a fork of distribute. :)
I meant that it uses a fork of setuptools, obviously
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
It's just a fork of virtualenv to use distribute.
It does not use a fork of distribute but distribute itself ;)
Lennart Regebro a écrit :
2009/10/6 Lennart Regebro rege...@gmail.com:
I think it's a fork of Virtualenv, no? Which uses a fork of distribute. :)
I meant that it uses a fork of
Anyway, it's released now on pypi as virtualenv-distribute-1.3.4.2.
The code is also merged in florian branch and it has been decided that's the
main repository.
kiorky a écrit :
It's just a fork of virtualenv to use distribute.
It does not use a fork of distribute but distribute itself ;)
2009/10/6 kiorky kio...@cryptelium.net:
Anyway, it's released now on pypi as virtualenv-distribute-1.3.4.2.
The code is also merged in florian branch and it has been decided that's the
main repository.
What is the florian branch, and in general, could you provide some
more info. Your emails
Hi,
I installed Distribute on a Snow Leopard box using the default Python that
comes with OS X. I used the installation method recommended in the docs, the
distribute_setup.py script. Now easy_install fails no matter what package I
try to install (it does not get around to looking for the name of
On Tue, Oct 6, 2009 at 4:37 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi,
I installed Distribute on a Snow Leopard box using the default Python that
comes with OS X. I used the installation method recommended in the docs, the
distribute_setup.py script. Now easy_install fails no
On Tue, Oct 6, 2009 at 4:43 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Tue, Oct 6, 2009 at 4:37 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi,
I installed Distribute on a Snow Leopard box using the default Python
that
comes with OS X. I used the installation method
On Tue, Oct 6, 2009 at 5:00 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Tue, Oct 6, 2009 at 4:55 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Yes, that fixed it. Thanks!
Great. The bug is still to be fixed though, would you mind adding an
issue following this link:
On Tue, Oct 6, 2009 at 5:12 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Reported as issue #59.
Thank you
--
Tarek Ziadé | http://ziade.org | オープンソースはすごい! | 开源传万世，因有你参与
___
Distutils-SIG maillist - Distutils-SIG@python.org
Ronald Oussoren ronaldousso...@mac.com wrote:
Installing distribute is therefore not problematic for most people, if
they know that the project exists. The fact that distribute is a
seperate project from setuptools can be a problem for people:
installing a bugfix release for a software
Hi Lennart,
If i read 'virtualenv-distribute 1.3.4.2 on pypi'
I can do some googling or even do some Pypi searching for
'virtualenv-distribute'.
Thus, the first link found may be [1].
On this link, the second sentence is:
The fork was started by Philip Jenvey at
On Tue, Oct 6, 2009 at 7:00 PM, Bill Janssen jans...@parc.com wrote:
For me, it's more a matter of OS X 10.6 already comes with setuptools;
how can I mitigate the impact of this buggy unmaintained package on the
systems I'm building to deploy on OS X?. Adding distribute to the mix,
however
At 09:20 AM 10/6/2009 +0300, Alex Grönholm wrote:
P.J. Eby kirjoitti:
At 11:53 AM 10/5/2009 +0200, Lennart Regebro wrote:
2009/10/5 Jeff Rush j...@taupro.com:
Very unfortunate, as in, it should NOT have happened. And *especially*
without any announcement on python.org or mention on the
2009/10/6 P.J. Eby p...@telecommunity.com:
Yes, but that's got nothing to do with the bug that's been being discussed.
The same change bit pywin32, and it doesn't use setuptools at all.
True. The problem was a badly documented interface, which meant people
used it in one way, but a bug fix
On Tue, 06 Oct 2009 10:25:04 -0700, kiorky kio...@cryptelium.net wrote:
The fork was started by Philip Jenvey at
http://bitbucket.org/pjenvey/virtualenv-distribute/ and this version by
Florian
Schulze lives at http://bitbucket.org/fschulze/virtualenv-distribute/
[1] -
I'm happy to announce that ActivePython 2.6.3.7 is now available for
download from:
http://www.activestate.com/activepython/
This is a patch-level release that updates ActivePython to core Python
2.6.3 along with the fixes for a couple of critical regressions that
instigated the work on
On Oct 6, 2009, at 10:36 AM, Hanno Schlichting wrote:
On Tue, Oct 6, 2009 at 7:00 PM, Bill Janssen jans...@parc.com wrote:
For me, it's more a matter of OS X 10.6 already comes with setuptools;
how can I mitigate the impact of this buggy unmaintained package on the
systems I'm building to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
2009/10/5 Jeff Rush j...@taupro.com:
Very unfortunate, as in, it should NOT have happened. And *especially*
without any announcement on python.org or mention on the
python-committers list of something this major.
Well
Tres Seaver wrote:
Bugfixes which break backward compatibility in minor relaseses are
major fouls, period.
Sure, but what does backward compatibility even mean for distutils ? Not
much, as any non trivial extension needs to use undocumented
implementation details.
As PJE points out, the
26 matches
Mail list logo
