On Wed, Aug 17, 2011 at 11:00 PM, Nick Coghlan wrote:
> It's actually for the same reason that unittest changes are backported
> under the unittest2 name - the distutils2 name can be used in the
> future to get Python 3.4 packaging features in Python 3.3, but that
> would be difficult if the backp
On Thu, Aug 18, 2011 at 12:15 PM, Fred Drake wrote:
> On Wed, Aug 17, 2011 at 9:15 PM, Chris McDonough wrote:
>> I'll throw this out there.. why is it going to have a different name on
>> python2 than on python3?
>
> So it can be a drop-in replacement for the existing distutils2, I'd expect.
>
>
On Wed, Aug 17, 2011 at 9:15 PM, Chris McDonough wrote:
> I'll throw this out there.. why is it going to have a different name on
> python2 than on python3?
So it can be a drop-in replacement for the existing distutils2, I'd expect.
"packaging" is new with Python3, and is the Guido-approved name
I'll throw this out there.. why is it going to have a different name on
python2 than on python3?
- C
On Wed, 2011-08-17 at 22:30 +, Vinay Sajip wrote:
> Tarek Ziadé gmail.com> writes:
>
> > IOW, the task to do is:
> >
> > 1/ copy packaging and all its stdlib dependencies in a standalone pr
Tarek Ziadé gmail.com> writes:
> IOW, the task to do is:
>
> 1/ copy packaging and all its stdlib dependencies in a standalone project
> 2/ rename packaging to distutils2
> 3/ make it work under older 2.x and 3.x (2.x would be the priority) <
> 4/ release it, promote its usage
> 5/ consolid
Den 10.08.2011 13:43, skrev Guido van Rossum:
They have a specific plan, based on Software Transactional Memory:
http://morepypy.blogspot.com/2011/06/global-interpreter-lock-or-how-to-kill.html
Microsoft's experiment to use STM in .NET failed though. And Linux got
rid of the BKL without STM.
