Tarek,
> Your proposal is a partial alternative to PEP 390, and is a quite
> interesting work to dig in, and the SIG is discussing it,
> but a very important point about it is that it does a lot more. It's a
> new *building* system on its own, and does not limit itself to
> describing metadata fi
On Thu, Nov 5, 2009 at 15:55, David Lyon wrote:
>
> Tarek, Guido,
>
> Forgive my grumpy tone..
>
> Looking positive, if we now have a rough consensus that the PEPS might
> represent some 300+ lines of code... then good - lets get started, that's
> all that I meant. I'm glad above all, that you not
2009/11/6 David Lyon :
[..]
> Here are the references to the discussions from distutils-sig. In these
> references you'll see that my interaction with the list was not grumpy
> but was entirely positive. I feel that I got a fair hearing on distutils
> list and I had a number of supporters to my pro
Tarek, Guido,
Forgive my grumpy tone..
Looking positive, if we now have a rough consensus that the PEPS might
represent some 300+ lines of code... then good - lets get started, that's
all that I meant. I'm glad above all, that you noticed that part foremost.
If it's a simple case that alternati
David, you have an attitude problem. Your contributions (the post
below is just an example) don't sound healthy to me -- you just
complain and whine and denigrate Tarek's work. In a previous post you
claimed to have had a particular idea first (it doesn't matter which
idea) and you managed to make
On Thu, Nov 5, 2009 at 11:29 PM, David Lyon wrote:
[...]
>
> But if you put all these PEPs together, implementing all the new features
> can't come to more than 300 lines of code...
>
> Since we hardly got anywhere on them in 2009, it will be interesting to
> see how much of it gets done in 2010.
On 2009-11-05 16:29 PM, David Lyon wrote:
But I've been on the list for some twelve months asking for work
to help out with, and haven't been assigned a single task to do
yet.
Seriously, if you won't allocate work out to people then how can
it get done?
With rare exceptions, open source proje
On Thu, 5 Nov 2009 11:35:41 +0100, Tarek Ziadé
wrote:
> PEP 376 is working on a default, unified, *installation* format, that
> tries to gather the good ideas of Pip, Setuptools etc.. and propose a
> unified format for our site-packages. This new standard will come with
> APIs in pkgutil to be abl
On Wed, 4 Nov 2009 17:40:35 -0500, Fred Drake wrote:
> The packaging story is in such bad shape that it needs the work
> regardless, and keeping it to Python 3 would significantly reduce the
> set of potential volunteers.
Well I guess that is a 'marketing decision'. Not a coding issue.
Actually
On Wed, Nov 4, 2009 at 5:16 PM, David Lyon wrote:
> I would even go so far as to use the python 3 as a carrot for
> the new work.
The packaging story is in such bad shape that it needs the work
regardless, and keeping it to Python 3 would significantly reduce the
set of potential volunteers.
> i
On Wed, 4 Nov 2009 13:29:35 +0100, Tarek Ziadé
wrote:
> I've started to refactor the code in a module I have called
> "sysconfig", reusing distutils/sysconfig, distutils/command/install
> and site code.
>
> This "sysconfig" module should provide at the end very useful APIs to
> query the current
On Wed, Oct 28, 2009 at 7:05 PM, Tarek Ziadé wrote:
> Ok then I'll work on a patch for that change and start an issue about it soon.
As I expected, being able to provide all those paths pulls a lot of
other stuffs out of distutils.
In fact, almost all the APIs that are located in distutils/sysco
M.-A. Lemburg wrote:
> +1
On Oct 28, 2009, at 7:02 AM, Michael Foord wrote:
> Also +1. It seems like this would make things easier for the alternative
> implementations.
On Wed, Oct 28, 2009 at 3:30 PM, sstein...@gmail.com
wrote:
> +1
Ok then I'll work on a patch for that change and start an i
On Oct 28, 2009, at 7:02 AM, Michael Foord wrote:
M.-A. Lemburg wrote:
Tarek Ziadé wrote:
Hello,
Since the addition of PEP 370, (per-user site packages), site.py and
distutils/command/install.py are *both* providing the various
installation directories for Python,
depending on the system an
M.-A. Lemburg wrote:
Tarek Ziadé wrote:
Hello,
Since the addition of PEP 370, (per-user site packages), site.py and
distutils/command/install.py are *both* providing the various
installation directories for Python,
depending on the system and the Python version.
We have also started to disc
Tarek Ziadé wrote:
> Hello,
>
> Since the addition of PEP 370, (per-user site packages), site.py and
> distutils/command/install.py are *both* providing the various
> installation directories for Python,
> depending on the system and the Python version.
>
> We have also started to discuss lately
Hello,
Since the addition of PEP 370, (per-user site packages), site.py and
distutils/command/install.py are *both* providing the various
installation directories for Python,
depending on the system and the Python version.
We have also started to discuss lately in various Mailing Lists the
additi
17 matches
Mail list logo
