Tres Seaver wrote:
Huh? Why? I just don't buy this. We've effectively had a bdfl
pronouncement that setuptools is dead. distribute 0.6 *is* now the live
supported setuptools so any project that relies on the package called
setuptools should now be using the distribute distribution...
Are you
kiorky a écrit :
[]
This may be quite current even if it's not a good habit to have circular
dependencies between distributions.
Imagine that.
B(0.7) - A(0.6).
A(0.6) - B(0.7).
Can i have the same namespace ns shared between the twice distributions with
both the setuptools
On Wed, Oct 14, 2009 at 4:19 PM, kiorky kio...@cryptelium.net wrote:
kiorky a écrit :
[]
This may be quite current even if it's not a good habit to have circular
dependencies between distributions.
Imagine that.
B(0.7) - A(0.6).
A(0.6) - B(0.7).
Can i have the same namespace ns
Tarek Ziadé a écrit :
On Wed, Oct 14, 2009 at 4:19 PM, kiorky kio...@cryptelium.net wrote:
kiorky a écrit :
[]
This may be quite current even if it's not a good habit to have circular
dependencies between distributions.
Imagine that.
B(0.7) - A(0.6).
A(0.6) - B(0.7).
Can i have the
On 2009-10-12, P.J. Eby p...@telecommunity.com wrote:
At 08:09 AM 10/12/2009 +, Reinout van Rees wrote:
OTOH, grumbl ... horrible breakage ... essential piece of infrastructure ...
allowed to persist I'm pretty grumpy right now.
Relax, take a deep breath, and then easy_install
On 2009-10-12, Hanno Schlichting ha...@hannosch.eu wrote:
Hi.
On Mon, Oct 12, 2009 at 9:10 AM, Reinout van Rees rein...@vanrees.org wrote:
- When using buildout, I get lots of warnings. The 1.4.2 isn't out yet, but
I
also won't update all old projects' pinned zc.buildout version so I'm
On Oct 13, 2009, at 3:15 AM, Reinout van Rees wrote:
On 2009-10-12, P.J. Eby p...@telecommunity.com wrote:
At 08:09 AM 10/12/2009 +, Reinout van Rees wrote:
OTOH, grumbl ... horrible breakage ... essential piece of
infrastructure ...
allowed to persist I'm pretty grumpy right now.
On 2009-10-09, Chris Withers ch...@simplistix.co.uk wrote:
Huh? Why? I just don't buy this. We've effectively had a bdfl pronouncement
that setuptools is dead. distribute 0.6 *is* now the live supported
setuptools so any project that relies on the package called setuptools
should now be using
Reinout van Rees rein...@vanrees.org writes:
Time for the BDFL to flip some ownership bits for setuptools in pypi.
You appear to think the BDFL has powers outside the Python language and
extending to third-party projects that are independent.
Regardless of what I think of Setuptools or
On 2009-10-12, Ben Finney ben+pyt...@benfinney.id.au wrote:
Reinout van Rees rein...@vanrees.org writes:
Time for the BDFL to flip some ownership bits for setuptools in pypi.
You appear to think the BDFL has powers outside the Python language and
extending to third-party projects that are
Hi.
On Mon, Oct 12, 2009 at 9:10 AM, Reinout van Rees rein...@vanrees.org wrote:
- When using buildout, I get lots of warnings. The 1.4.2 isn't out yet, but I
also won't update all old projects' pinned zc.buildout version so I'm stuck
with warnings for a time.
Note that buildout is only
On Mon, Oct 12, 2009 at 9:10 AM, Reinout van Rees rein...@vanrees.org wrote:
On 2009-10-09, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Fri, Oct 9, 2009 at 2:03 PM, kiorky kio...@cryptelium.net wrote:
AND no, virtualenv must continue to provide setuptools, backward
compatibility, you know?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Huh? Why? I just don't buy this. We've effectively had a bdfl
pronouncement that setuptools is dead. distribute 0.6 *is* now the live
supported setuptools so any project that relies on the package called
setuptools should
Reinout van Rees wrote:
OTOH, grumbl ... horrible breakage ... essential piece of infrastructure ...
allowed to persist I'm pretty grumpy right now.
I'd just like to point out that if anyone finds setuptools to
be essential to them, it's because they've chosen to make
themselves
At 08:09 AM 10/12/2009 +, Reinout van Rees wrote:
OTOH, grumbl ... horrible breakage ... essential piece of infrastructure ...
allowed to persist I'm pretty grumpy right now.
Relax, take a deep breath, and then easy_install setuptools==dev or
setuptools==dev06. ;-)
It turned out
On Tue, Oct 13, 2009 at 12:35 AM, P.J. Eby p...@telecommunity.com wrote:
At 08:09 AM 10/12/2009 +, Reinout van Rees wrote:
OTOH, grumbl ... horrible breakage ... essential piece of infrastructure
...
allowed to persist I'm pretty grumpy right now.
Relax, take a deep breath, and
kiorky wrote:
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
2009/10/9 Chris Withers ch...@simplistix.co.uk:
Why are there effectively 3 forks on virtualenv now, just to get it to use
distribute? Is it really so hard to work with Ian Bicking to be the real
virtualenv using distribute instead of setuptools
Well I would expect Ian to want to take it a bit
On Fri, Oct 9, 2009 at 12:54 PM, Chris Withers ch...@simplistix.co.uk wrote:
kiorky wrote:
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
Hi Chris,
As far as i know, we just give links for power users/developers to know how to
find the actual related repositories.
It s *CLEARLY* specified *IN THE HOMEPAGE METADATA* that the official thing
lives inside florian branch. Those are not 3 forks, but 3 branches or the same
code. And the
On Fri, Oct 9, 2009 at 2:03 PM, kiorky kio...@cryptelium.net wrote:
AND no, virtualenv must continue to provide setuptools, backward
compatibility,
you know?
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice
Chris Withers ch...@simplistix.co.uk writes:
Why are there effectively 3 forks on virtualenv now, just to get it to
use distribute? Is it really so hard to work with Ian Bicking to be
the real virtualenv using distribute instead of setuptools, especially
in the way of the bdfl pronouncement?
2009/10/9 Tarek Ziadé ziade.ta...@gmail.com:
I think the word fork here, in DVCS principles, just means that you
copy a repository
to work with, and eventually ask for the main repo to merge the changes.
Yeah, it's just a branch, basically. But it is hard to get an overview.
--
Lennart
On Fri, Oct 9, 2009 at 2:36 PM, Lennart Regebro rege...@gmail.com wrote:
2009/10/9 Tarek Ziadé ziade.ta...@gmail.com:
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice it.
I guess the point is that is should
Hi tarek,
Tarek Ziadé a écrit :
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice it.
Living in my 0.6.x snail sandbox is not a solution.
As it seems that Distribute 0.7 won't for a long time.
setuptools
On Fri, Oct 9, 2009 at 2:43 PM, kiorky kio...@cryptelium.net wrote:
Hi tarek,
Tarek Ziadé a écrit :
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice it.
Living in my 0.6.x snail sandbox is not a solution.
Tarek Ziadé a écrit :
On Fri, Oct 9, 2009 at 2:43 PM, kiorky kio...@cryptelium.net wrote:
Hi tarek,
Tarek Ziadé a écrit :
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice it.
Living in my 0.6.x snail
kiorky kirjoitti:
Tarek Ziadé a écrit :
On Fri, Oct 9, 2009 at 2:43 PM, kiorky kio...@cryptelium.net wrote:
Hi tarek,
Tarek Ziadé a écrit :
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice
On Fri, Oct 9, 2009 at 3:32 PM, kiorky kio...@cryptelium.net wrote:
Why they can't ?
As i understood all those readings, packages for 0.6 and 0.7 will be
installable
with the appropriate distribute version, thus side by side, but for me, they
may
be incompatibles together.
They may be ?
Tarek Ziadé wrote:
I think the word fork here, in DVCS principles, just means that you
copy a repository
to work with, and eventually ask for the main repo to merge the changes.
So what's the main repo?
What one of these three options should someone looking to use
virtualenv-distribute
kiorky wrote:
Lennart Regebro a écrit :
2009/10/9 Tarek Ziadé ziade.ta...@gmail.com:
The *whole* point of Distribute 0.6.x is to be backward compatible, meaning
that if virtualenv switch to it, you will not even notice it.
I guess the point is that is should still work even if you don't want
Chris Withers a écrit :
Tarek Ziadé wrote:
I think the word fork here, in DVCS principles, just means that you
copy a repository
to work with, and eventually ask for the main repo to merge the changes.
So what's the main repo?
What one of these three options should someone looking to
Tarek Ziadé a écrit :
On Fri, Oct 9, 2009 at 3:32 PM, kiorky kio...@cryptelium.net wrote:
And also, to use them together, what a hell. For package A i need 0.6 (hard
requirement), for package B i need 0.7 (hard requirement), for C i need 0.6.
C
depend on A which depends on B. I also have
On Fri, Oct 9, 2009 at 5:54 AM, Chris Withers ch...@simplistix.co.uk wrote:
kiorky wrote:
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
Ian Bicking a écrit :
On Fri, Oct 9, 2009 at 5:54 AM, Chris Withers ch...@simplistix.co.uk wrote:
kiorky wrote:
I think one (pjenvey) was an experiment, and another is actually a
released virtualenv-distribute package (updating the name in setup.py,
etc). And the third, I dunno.
The
Ian Bicking wrote:
I think one (pjenvey) was an experiment, and another is actually a
released virtualenv-distribute package (updating the name in setup.py,
etc). And the third, I dunno.
Anyway -- I'm reluctant to switch virtualenv to distribute right now,
as I'm not confident it is ready for
36 matches
Mail list logo
