What nobody still fails to explain in this discussion is what CPAN
is and Why Python doesn't already have it.
There is just a lot of CPAN is great! And Python needs CPAN but
noone can come up with one single thing that CPAN does that Python
doens't have, or explain why CPAN is so great, where PyPI
On Sat, Dec 19, 2009 at 11:05 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Sat, Dec 19, 2009 at 10:12 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
On Fri, Dec 18, 2009 at 03:41:48PM +0100, Tarek Ziadé wrote:
The remaining point I can see is about : Repository-URL,
On Mon, Dec 21, 2009 at 12:14 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
[..]
We believe that having PEP 376 and PEP 345 accepted will be a major
improvement for the Python packaging eco-system.
s/PEP 376/PEP 386
___
Distutils-SIG maillist -
On Mon, Dec 21, 2009 at 11:13:31AM +0100, Lennart Regebro wrote:
What nobody still fails to explain in this discussion is what CPAN
is and Why Python doesn't already have it.
There is just a lot of CPAN is great! And Python needs CPAN but
noone can come up with one single thing that CPAN does
On Mon, Dec 21, 2009 at 12:42, David Robins pyt...@davidrobins.net wrote:
1. Module documentation - the perldoc is extracted, formatted as HTML,
and is available for browsing (e.g., search.cpan.org - perhaps this is
part of the sugar described by Steffen but it tastes delicious). The
same
devyan parmar, on 2009-12-18:
Hi,
I am using buildout for my project development as well as for deployment.
which makes process easy and help in repeatability.
but facing one problem while choosing particular versions of eggs while
running buildout.
i have eggified my python packages and
On Mon, Dec 21, 2009 at 7:13 PM, Lennart Regebro rege...@gmail.com wrote:
What nobody still fails to explain in this discussion is what CPAN
is and Why Python doesn't already have it.
That's not the right question to ask. The problem is not much a
feature problem as much as a fundamental
On Mon, Dec 21, 2009 at 11:48 PM, David Cournapeau courn...@gmail.com wrote:
On Mon, Dec 21, 2009 at 7:13 PM, Lennart Regebro rege...@gmail.com wrote:
What nobody still fails to explain in this discussion is what CPAN
is and Why Python doesn't already have it.
That's not the right question to
On Dec 21, 2009, at 5:48 PM, David Cournapeau wrote:
On Mon, Dec 21, 2009 at 7:13 PM, Lennart Regebro rege...@gmail.com wrote:
What nobody still fails to explain in this discussion is what CPAN
is and Why Python doesn't already have it.
That's not the right question to ask. The problem is
On Tue, 22 Dec 2009 07:48:55 +0900, David Cournapeau courn...@gmail.com
wrote:
(cpan) ... is not much a
feature problem as much as a fundamental implementation and state of
mind.
Yes. Their state of mind is make it simple and make it work across
the board for everything for everyone.
On Tue, Dec 22, 2009 at 9:04 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Mon, Dec 21, 2009 at 11:48 PM, David Cournapeau courn...@gmail.com wrote:
On Mon, Dec 21, 2009 at 7:13 PM, Lennart Regebro rege...@gmail.com wrote:
What nobody still fails to explain in this discussion is what CPAN
is
Hi,
I wonder if there is any interest in the current distribute effort to
specify some low-level commonalities outside the distutils code for
interoperation. In particular, I had two things in mind:
1 Formally specifying the egg format (and versioning it !) - or is
egg format outside distribute
Just use buildout...
On Tue, 22 Dec 2009 10:24:07 +0900, David Cournapeau courn...@gmail.com
wrote:
Hi,
I wonder if there is any interest in the current distribute effort to
specify some low-level commonalities outside the distutils code for
interoperation. In particular, I had two things
Hi!
I have old/new problem, once mentioned in 2004 at this same mailing
list ( http://mail.python.org/pipermail/distutils-sig/2004-March/003807.html
) but surely that implementation is bad... But the problem persists, I
use SWIG and had to Google all over to only find out build order
cannot be
On Tue, Dec 22, 2009 at 2:07 AM, David Cournapeau courn...@gmail.com wrote:
[..]
The metadata, as defined in PEP 314,
are not thrown away by Distutils, but properly uploaded at PyPI.
But there is much more than what PEP 314 defines.
Then that's not the metadata as defined in python
On Tue, Dec 22, 2009 at 10:50 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Two things:
1/ you get warnings if you try to build a distribution with missing metadata
and there's now a command in 2.7 called check so you can set a
strict control
on client side
This is nice, I missed this
On Tue, Dec 22, 2009 at 7:16 AM, Jari Pennanen jari.penna...@gmail.com wrote:
Hi!
I have old/new problem, once mentioned in 2004 at this same mailing
list ( http://mail.python.org/pipermail/distutils-sig/2004-March/003807.html
) but surely that implementation is bad... But the problem
On Tue, Dec 22, 2009 at 2:24 AM, David Cournapeau courn...@gmail.com wrote:
Hi,
I wonder if there is any interest in the current distribute effort to
specify some low-level commonalities outside the distutils code for
interoperation. In particular, I had two things in mind:
1 Formally
On Tue, Dec 22, 2009 at 2:58 AM, David Cournapeau courn...@gmail.com wrote:
On Tue, Dec 22, 2009 at 10:50 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Two things:
1/ you get warnings if you try to build a distribution with missing metadata
and there's now a command in 2.7 called check so
At 10:24 AM 12/22/2009 +0900, David Cournapeau wrote:
1 Formally specifying the egg format (and versioning it !) - or is
egg format outside distribute goal ?
FYI: http://peak.telecommunity.com/DevCenter/EggFormats
___
Distutils-SIG maillist -
On Tue, Dec 22, 2009 at 11:42 AM, P.J. Eby p...@telecommunity.com wrote:
At 10:24 AM 12/22/2009 +0900, David Cournapeau wrote:
1 Formally specifying the egg format (and versioning it !) - or is
egg format outside distribute goal ?
FYI: http://peak.telecommunity.com/DevCenter/EggFormats
I
On Tue, Dec 22, 2009 at 11:06 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
If you are referring to the installation format, Distribute wants to
drop any extra format in the future and stick with a unique, standard
format described in PEP 376 to avoid having an heterogeneous
site-packages.
On Mon, Dec 21, 2009 at 23:48, David Cournapeau courn...@gmail.com wrote:
mind. Reliable packaging requires explicit handling, where the whole
python stack for packaging relies a lot on implicit behavior.
Can you give examples of this implicit behaviour?
- distutils (and most tools on top)
23 matches
Mail list logo
