Le 08/25/2010 05:32 PM, Éric Araujo a écrit :
> I think that the most important release is docs.python.org/2.6,
> regardless of python.org/OS-specific downloadable doc packages.
>
> If people do like haypo and use the most recent docs instead of the
> version-specific ones, there’s indeed no need
Le 10/08/2010 05:25 PM, Tarek Ziadé a écrit :
> On Fri, Oct 8, 2010 at 5:53 PM, Toshio Kuratomi wrote:
>> On Fri, Oct 08, 2010 at 05:12:44PM +0200, Antoine Pitrou wrote:
> ...
pysetup is shorter
>
> Let's use pysetup !
+1 on pysetup. Reusing the well known "setup" and adding py as a prefix
w
Le 10/08/2010 04:31 PM, Jon Ribbens a écrit :
> On Fri, Oct 08, 2010 at 11:04:35AM -0400, Toshio Kuratomi wrote:
>> In the larger universe of programs, it might make for more intuitive
>> remembering of the command to use a prefix (either py or python) though.
>>
>> python-setup is a lot like pyth
Hi python-devs,
I'm currently working on distutils2, and I'm trying to stop having
different informations in different places. This means using the
bugs.python.org bugtracker, instead of some weird TODO-lists in the
bitbucket wiki.
Two requests then:
* Is it possible to give me the rights to edi
Le 13/02/2011 15:40, Terry Reedy a écrit :
> Do you meant that Tarek supports or approves of this?
> (Co-opt means something rather different in English.)
Sorry, I mean that Tarek approves that :-)
___
Python-Dev mailing list
Python-Dev@python.org
http://
Le 13/02/2011 16:12, Éric Araujo a écrit :
> Hi,
>
> I’ve wanted to move our TODO wiki page to the bug tracker for months,
> thanks for doing it! Auto-nosy is useful to catch new bugs; for
> existing bugs, instead of adding yourself manually to each one and
> trigger not-so-useful email, a tracke
Le 13/02/2011 23:16, Antoine Pitrou a écrit :
> On Sun, 13 Feb 2011 14:47:01 +
> Alexis Métaireau wrote:
>>
>> * Is it possible to give me the rights to edit the reports for the
>> distutils2 component ?
>
> Done. Actually, you have general developer rights, si
Hi folks,
I have this in my mind since a long time, but I didn't talked about that
on this list, was only writing on distutils@ or another list we had for
distutils2 (the fellowship of packaging).
AFAIK, we're almost good about packaging in python 3.3, but there is
still something that keeps
On 20/06/2012 14:53, Nick Coghlan wrote:
3.4 PEP: Standard library package downloader (pysetup)
--
# Amongst other things, this needs to have a really good security
story (refusing to install unsigned packages by default, etc)
packaging.depgraph — Depende
On 20/06/2012 13:31, Tarek Ziadé wrote:
packaging.metadata is the implementation of all metadata versions.
standalone too.
packaging.pypi is the PyPI crawler, and has fairly advanced features.
I defer to Alexis to tell us
is it's completely stable
packaging.pypi is functionally working but
Le mer. 20 juin 2012 15:28:56 CEST, Nick Coghlan a écrit :
There would be two main parts to such a PEP:
- defining the command line interface and capabilities (pysetup)
- defining the programmatic API (packaging.pypi and the dependency
graph management)
Okay. I don't think that the command line h
Le mer. 20 juin 2012 18:45:23 CEST, Paul Moore a écrit :
Thanks - as you say, it's not so much the actual problem as the
principle of what the packaging API offers that matters here. Although
it does make a good point - to what extent do the packaging APIs draw
on existing experience like that of
On 20/06/2012 17:29, Paul Moore wrote:
I wasn't aware of this - I've had a look and my first thought is that
the documentation needs completing. At the moment, there's a lot that
isn't documented, and we should avoid getting into the same situation
as with distutils where people have to use undo
Hi Carl,
Thanks for clarifying this.
This means that indeed we have the same goals. I'll have a closer look
at the internal pip APIs, as they are probably really useful and already
used in production environment :)
___
Python-Dev mailing list
Python
14 matches
Mail list logo
