Guido van Rossum wrote:
> But the >>> prompt is Python's trademark! I always get a warm fuzzy
> feeling when I see it, e.g. in a corner of a slide in a NASA
> presentation.
In fact, there would be another reason to change the prompt in Py3k: to
identify Py3k snippets and tell them from Python 2.
Guido van Rossum wrote:
> But the >>> prompt is Python's trademark!
Maybe you could change it to something like
_/\_/\_P
(That's meant to be an ascii-art python.)
--
Greg
___
Python-3000 mailing list
[email protected]
http://mail.python.org/ma
Aahz wrote:
>> it's a minor issue, but I was wondering if the interpreter prompt could be
>> changed in Py3K. The current prompt is ">>>" which happens to match the
>> standard character used for quotes in e-mails. As a result, intepreter
>> sessions might look funky when copy & pasted inside m
On 11/29/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> But the >>> prompt is Python's trademark! I always get a warm fuzzy
> feeling when I see it, e.g. in a corner of a slide in a NASA
> presentation.
I was using ``py>`` for a while. That still gave me a warm fuzzy
feeling ;-) and seemed to
OK, let's stop this. It's not going to change. The deficiencies of
email shouldn't be dictating the language. If I hear more pleading
I'll have to add it to PEP 3099.
Please read http://yellow.bikeshed.com.
--Guido
On 11/30/06, Steven Bethard <[EMAIL PROTECTED]> wrote:
> On 11/29/06, Guido van R
Guido van Rossum wrote:
> Please read http://yellow.bikeshed.com.
make that
http://gold.bikeshed.com/
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/m
NEITHER, both hard to read due to color intensity...
http://white.bikeshed.com/ ;-O see
>Fredrik Lundh <[EMAIL PROTECTED]> wrote:http://gold.bikeshed.com/
>Guido van Rossum wrote: http://yellow.bikeshed.com/
___
Python-3000 mailing list
Python-3000@pytho
> http://wiki.python.org/moin/AbstractBaseClasses
N! so many baseclasses, who can remember all that?!
now whenever i wish to implement, say, MyFunnyDict, i'll have to
go over the manual, see all the standard interfaces (which may
reach hundreds of classes), and think which interfaces i d
> so no offense in advance.
Sure, no offense taken. I've seen comments like this before on this
list (recently :-). I think both approaches (interface types and duck
typing) are complicated in different ways. But interface types seem
less so, because they provide a place where the user can stop
Bill Janssen wrote:
> So file.readlines() would return an iterable, then?
I wasn't thinking of having a file.readlines(), just
a stand-alone function. I'd like to see the file
object's interface made quite minimal in Py3k.
--
Greg
___
Python-3000 mailin
Giovanni Bajo wrote:
> In fact, there would be another reason to change the prompt in Py3k: to
> identify Py3k snippets and tell them from Python 2.x snippets.
P3>
--
Greg
___
Python-3000 mailing list
[email protected]
http://mail.python.org/
> Bill Janssen wrote:
> > So file.readlines() would return an iterable, then?
>
> I wasn't thinking of having a file.readlines(), just
> a stand-alone function. I'd like to see the file
> object's interface made quite minimal in Py3k.
>
> --
> Greg
Where would the standalone function live? How
I've updated the page to reflect more of Jim Jewett's comments. And
to reflect more of the underlying "special methods". "Container", for
instance, now has "get" (for __getattr__), as well as "len" (for
__len__).
By the way, all these interfaces are already in Python; they just
aren't written do
13 matches
Mail list logo
