Greg Ewing wrote:
> If it's okay to use a silly name for the whole
> project, why not for part of its infrastructure?
because it's difficult enough to do a Python elevator pitch as it is ?
(why is a package index so different from things like "documentation"
and "source" and "installer" and "bu
Greg Ewing schrieb:
>> If they also created a new sub-command for build,
>> you would have to make your get_sub_command implementation
>> return them both.
>
> If these sub-commands really are independent,
> why can't I just add one to a list somewhere?
> Then it would be no problem at all for dif
Martin v. Löwis wrote:
> If they also created a new sub-command for build,
> you would have to make your get_sub_command implementation
> return them both.
If these sub-commands really are independent,
why can't I just add one to a list somewhere?
Then it would be no problem at all for different
Fredrik Lundh wrote:
> using a "silly name" for the project, software, and even for the URL is one
> thing. using it to describe an important part of the infrastructure is
> another
> thing.
If it's okay to use a silly name for the whole
project, why not for part of its infrastructure?
--
Greg
I like the PyPR -- "piper" or "pie-per" -- suggestion. Good sound,
reasonable acronym, fairly straightforward pronunciation.
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 17, 2006, at 4:28 PM, Terry Reedy wrote:
> Pie/Pi/Py/Pyeshop -- pun intended
>
> Package index (pi) shop
> Python extension/expansion (pye) shop
> Python index of extensions (pie) shop
>
> Take your pick of acronyms, but pie is yummy in about a
On Tue, Oct 17, 2006 at 04:28:50PM -0400, Terry Reedy wrote:
> Pie/Pi/Py/Pyeshop -- pun intended
>
> Package index (pi) shop
> Python extension/expansion (pye) shop
> Python index of extensions (pie) shop
Peggy - Python eggs repositorY ;) Or just PER.
Oleg.
--
Oleg Broytmann
"Greg Ewing" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Fred L. Drake, Jr. wrote:
>> The "Cheese Shop" name may reflect the
>> proper cultural bias toward Monty Python, but it's a sure way to
>> alienate
>> people by presenting the hard work of the community under a completely
Perhaps it should be Python Package Repository (PYPR).
Or even the Py'd Pypr.
Like other package repositories it would sing you a nice song at first
and then when the versioning trouble hits you'll feel like you're
drowning.
Paul Prescod
On 10/17/06, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 17, 2006, at 1:54 PM, Fred L. Drake, Jr. wrote:
> I seem to recall Richard Jones saying he pronounces it "pippy",
> which I never
> could understand based on the spelling.
>
> So, the biggest problem "PyPI" is that no one can agree on how to
On Tuesday 17 October 2006 05:00, Nick Coghlan wrote:
> I must say I was surprised people found potential confusion between PyPy
> and PyPI, though. I'd always pronounced the latter as Py-Pea-Eye (and it
> was a tool for finding useful Python packages, so the other meaning of PI
> fit, too)
I
> At some point we're going to run out of all the really well-known Monty
> Python sketches, at which point people will either come to their senses,
> or we are going to see abominations like open source projects named
> "dead bishop" or something.
Cf. "crunchy frog", a really cool application con
Greg Ewing schrieb:
> Not sure exactly what you mean by a "sub-command".
> If you mean a subclass of the class that implements
> the "build" command, that's far too heavyweight.
distutils has a special concept called a "subcommand"
(apparently, people creating such packages have an
intuition for c
Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Barry Warsaw wrote:
>
> > Cheese Shop seems fine to me (and not just 'cause I came up with it). You
> > /need/ a little humor and levity in a software project or it just gets
> > boring.
>
> using a "silly name" for the project, software, and even for t
Barry Warsaw wrote:
> Cheese Shop seems fine to me (and not just 'cause I came up with
> it). You /need/ a little humor and levity in a software project or
> it just gets boring.
using a "silly name" for the project, software, and even for the URL is one
thing. using it to describe an important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 16, 2006, at 9:28 PM, Fred L. Drake, Jr. wrote:
> Which is really, really, REALLY sad. The "Cheese Shop" name may
> reflect the
> proper cultural bias toward Monty Python, but it's a sure way to
> alienate
> people by presenting the hard w
On 10/17/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
> How do you pronounce PyPI, btw? Is it "pie-pie" or
> "pie-pee-eye"? (And don't tell me it's actually
> pronounced "pippy" -- acronyms with non-obvious
> pronunciations are a minor peeve of mine. People
> are going to pronounce it the way they thi
Greg Ewing wrote:
> Talin wrote:
>> Cheeseshop may be overly cute, however it has at least this mnemonic
>> benefit is that it suggests a "shop",
>
> I actually quite like Cheese Shop too, and I'd be
> perfectly happy for it to remain.
I became reconciled to the name when I realized it could be
> Which is really, really, REALLY sad. The "Cheese Shop" name may reflect
> the
> proper cultural bias toward Monty Python, but it's a sure way to alienate
> people by presenting the hard work of the community under a completely
> silly
> name that communicates nothing about what it's about.
Isn
Fred L. Drake, Jr. wrote:
> Perhaps my recall of history is lacking, but I'd say PyPy is too easily
> confused with PyPI; wasn't PyPI around first, at least as a moniker?
That may be so. But I like PyPy as a name for what it
is better than PyPI, so if one of them had to go, I
wouldn't want to lo
20 matches
Mail list logo
