Hi Guido,
Guido van Rossum wrote:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon david.l...@preisshare.net wrote:
So the packages on CPAN are typically of a higher quality, simply
because they've been machine checked. I like that.
Speaking purely on hearsay, I don't believe that. In
Guido van Rossum gu...@python.org writes:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon david.l...@preisshare.net wrote:
So the packages on CPAN are typically of a higher quality, simply
because they've been machine checked. I like that.
Speaking purely on hearsay, I don't believe that. In
I love how this created a flurry of speculation on what people who say
Python doens't have a CPAN mean. Wouldn't it be easer to *ask* them?
:-)
Just-wondering-ly
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
2009/11/7 Kaelin Colclasure kae...@acm.org:
Since I bootstrapped the environment I used to learn Python with
easy_install, I naturally went straight to the easy_install docs to learn
how to give back. I wasn't even aware of this separate thing called
distutils until I read about it in the
On Nov 6, 2009, at 12:53 PM, Guido van Rossum wrote:
I just found this comment on my blog. People have told me this in
person too, so I believe it is real pain (even if the solution may be
elusive and the suggested solutions may not work). But I don't know
how to improve the world. Is the work
On Sat, Nov 7, 2009 at 5:07 AM, David Lyon david.l...@preisshare.net wrote:
On Sat, 7 Nov 2009 02:19:02 +0100, Tarek Ziadé ziade.ta...@gmail.com
wrote:
I unfortunately don't have all the time I wish I had to work on this
more.
We all know that.
It needs somebody new to take on the
2009/11/7 Glyph Lefkowitz gl...@twistedmatrix.com:
One project that would help a lot is just a easy python setup
documentation project that describes, as simply as possible, in large fonts,
how to get a working Python setup that adheres to a few conventions.
[...]
+1 Strong conventions would
David Lyon wrote:
Even if you implement PyPI + PEP 381 + PEP 381 tomorrow I promise
you that you won't be anywhere close to CPAN.
It's a much more serious challenge than perphaps you realise..
I keep reading and I keep hearing you and others saying this, but as
someone who has never used
On Sat, Nov 7, 2009 at 6:04 AM, Jeff Rush j...@taupro.com wrote:
BTW at the recent pyTexas regional conference we had a good group
discussion about packaging, with people offering analysis from the Perl,
Java, Ruby and Haskell communities. It seems each language still only
covers part of the
David Cournapeau schrieb:
Hi Guido,
Guido van Rossum wrote:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon david.l...@preisshare.net wrote:
So the packages on CPAN are typically of a higher quality, simply
because they've been machine checked. I like that.
Speaking purely on
Tarek Ziadé schrieb:
For the documentation part I am afraid it will be messy for the end
users trying to package apps in Python *until* all PEPs
have made it into Python.
Although, as Ian Bicking says: we could write today some kind of
all-in-one tutorial so end-users can work out without
la, 2009-11-07 kello 00:14 +0200, Alex Grönholm kirjoitti:
[clip: problems in distributing scientific Python packages]
I for one did not understand the problem. What does CPAN have that
PyPI
doesn't?
It is natural for packages (distributions, in distutils terms) to
have
dependencies on
Hi Jeff,
On Sat, 07 Nov 2009 06:04:15 -0600, Jeff Rush j...@taupro.com wrote:
I keep reading and I keep hearing you and others saying this, but as
someone who has never used CPAN, I'm not seeing the large number of
specific implementable tasks that CPAN clearly has and PyPI clearly does
On Sat, 7 Nov 2009 06:53:17 -0600, Brad Allen bradallen...@gmail.com
wrote:
During that conversation Walker mentioned that he thought that Java's
Maven packaging system had been really successful with the idea of
having a metadata file stored outside each package. That made it
easier for the
As Ian suggested, and since others thinks its a good idea, I suggest
that we start writing a python packaging guide using
reStructuredText and DVCS,
explaining how to handle packaging today. (with *all* existing tools)
When it's done, we could add it in python's Doc/ with the help of Georg.
I
On Nov 7, 2009, at 3:20 AM, Ben Finney wrote:
Guido van Rossum gu...@python.org writes:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon
david.l...@preisshare.net wrote:
I think buildbot-style test runs for PyPI packages would raise average
package quality on PyPI.
Please excuse the
Hi Tarek,
On Sat, 7 Nov 2009 12:12:44 +0100, Tarek Ziadé ziade.ta...@gmail.com
wrote:
You don't understand at all what is going on I think.
I guess so.
.. it means that we can take
more help from more people (and that includes you of course).
I really do accept that.
What's hard for me
On Sat, Nov 7, 2009 at 3:46 PM, David Lyon david.l...@preisshare.net wrote:
[..]
.. it means that we can take
more help from more people (and that includes you of course).
I really do accept that.
What's hard for me to understand exactly is what you will actually allow
me to do.
Gosh. I
On Nov 7, 2009, at 10:08 AM, Jesse Noller wrote:
On Sat, Nov 7, 2009 at 9:30 AM, sstein...@gmail.com sstein...@gmail.com
wrote:
On Nov 7, 2009, at 3:20 AM, Ben Finney wrote:
Guido van Rossum gu...@python.org writes:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon david.l...@preisshare.net
Andreas Jung kirjoitti:
Am 06.11.09 18:53, schrieb Guido van Rossum:
I just found this comment on my blog. People have told me this in
person too, so I believe it is real pain (even if the solution may be
elusive and the suggested solutions may not work). But I don't know
how to improve the
On Sat, Nov 7, 2009 at 3:57 PM, Andreas Jung li...@zopyx.com wrote:
[..]
- supports too much different versioning schemas. Both
schema supported by setuptools and the one proposed
by Tarek in some PEP are totally over-engineered.
A simple and *enforced* versioning schema is what
I
At 03:57 PM 11/7/2009 +0100, Andreas Jung wrote:
- supports too much different versioning schemas. Both
schema supported by setuptools and the one proposed
by Tarek in some PEP are totally over-engineered.
A simple and *enforced* versioning schema is what
I want to see.
- no more
On Sat, Nov 7, 2009 at 9:30 AM, sstein...@gmail.com sstein...@gmail.com wrote:
On Nov 7, 2009, at 3:20 AM, Ben Finney wrote:
Guido van Rossum gu...@python.org writes:
On Fri, Nov 6, 2009 at 2:52 PM, David Lyon david.l...@preisshare.net
wrote:
I think buildbot-style test runs for PyPI
Am 07.11.09 16:37, schrieb Tarek Ziadé:
On Sat, Nov 7, 2009 at 3:57 PM, Andreas Jung li...@zopyx.com wrote:
[..]
- supports too much different versioning schemas. Both
schema supported by setuptools and the one proposed
by Tarek in some PEP are totally over-engineered.
A simple
On Sat, 7 Nov 2009 16:08:46 +0100, Tarek Ziadé ziade.ta...@gmail.com
wrote:
Gosh. I am not your boss, and I am not telling you what to do.
otoh you're the boss of distutils. So you can direct people to
work on certain things to help you along. That would have kept
me much quieter with work.
On 03:56 pm, li...@zopyx.com wrote:
Am 07.11.09 16:37, schrieb Tarek Ziad�:
On Sat, Nov 7, 2009 at 3:57 PM, Andreas Jung li...@zopyx.com wrote:
[..]
- supports too much different versioning schemas. Both
schema supported by setuptools and the one proposed
by Tarek in some PEP are totally
On Sat, Nov 7, 2009 at 4:56 PM, Andreas Jung li...@zopyx.com wrote:
[..]
Do we need/want development on PyPI? At least not me.
MAJOR.MINOR.MICRO.PICO + |a-c]1..N
should be good enough.
PEP 386 is about providing the version scheme so we can compare versions
in Distutils when we want to know
On Nov 7, 2009, at 12:39 AM, Lennart Regebro wrote:
2009/11/7 Kaelin Colclasure kae...@acm.org:
Since I bootstrapped the environment I used to learn Python with
easy_install, I naturally went straight to the easy_install docs to
learn
how to give back. I wasn't even aware of this separate
Am 07.11.09 17:13, schrieb Tarek Ziadé:
On Sat, Nov 7, 2009 at 4:56 PM, Andreas Jung li...@zopyx.com wrote:
[..]
Do we need/want development on PyPI? At least not me.
MAJOR.MINOR.MICRO.PICO + |a-c]1..N
should be good enough.
PEP 386 is about providing the version scheme so we can
On Nov 7, 2009, at 6:57 AM, Andreas Jung wrote:
- no more external hosting of packages. If people
want their packages listed on Pypi, they should
be required to upload their packages on PyPI
(no more issues with non-available external server,
no more issues with mirroring external
One other really nice thing about the Perl packaging ecosystem is that
their standard library is packaged!
If there is a bug found in the Perl standard library, it's trivial to
upgrade it to a newer release with a bug fix. For example, the recent
little distutils snafu would have been a
On Nov 7, 2009, at 3:32 PM, Jannis Leidel wrote:
Oh, intriguing idea, has moving distutils out of Python core been
considered before?
To be clear, I'm not suggesting moving anything in or out of the
standard library. Just taking what's in the standard library and
packaging it up,
32 matches
Mail list logo
