On Wednesday 20 December 2006 19:19, Greg Ewing wrote:
> Noo! Javascript in the Python docs
> would be *insane*.
I can probably be convinced to use Python when it's ubiquitous in
browsers. ;-)
-Fred
--
Fred L. Drake, Jr.
___
Python-3000
On Wednesday 20 December 2006 19:17, Aahz wrote:
> Die, evil scum.
:-)
Actually, I don't think what I had in mind would prevent Lynx users from being
able to access everything in the docs, except the ability to hide the older
version notes. There wouldn't be information that you couldn't acce
On 12/18/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
[SNIP]
Ok, so be it. Let this be a pronouncement -- the only stdlib reorg
we're doing will be (a) deleting silly old stuff; (b) rename modules
that don't conform to the current module/package naming convention,
like StringIO, cPickle or Us
On 12/20/06, Talin <[EMAIL PROTECTED]> wrote:
1) What's the process for editing a PEP after it has been reviewed, but
before its been accepted?
If you are the original author, just edit it. If you are not, either get
the original author to change it or email python-dev/python-3000 your issue
1) What's the process for editing a PEP after it has been reviewed, but
before its been accepted?
I've recently had some requests to make some edits to the PEP. However,
I don't want to do these in "stealth mode", like a congressional staffer
who inserts changes into a bill right before it's vo
Jim Jewett wrote:
> Knowing which i's to rename strikes *me* as tricky,
It shouldn't be too hard if you approach it the
right way. One way would be to temporarily change
the symbol table entry for the loop var when
compiling the loop body and any nested functions
so that it refers to a different
> On Tue, Dec 19, 2006, Fred L. Drake, Jr. wrote:
>>Hmm. I think a little bit of JavaScript would go a long way. ;-)
Noo! Javascript in the Python docs
would be *insane*.
--
Greg
___
Python-3000 mailing list
Python-3000@python.org
http://mail.py
On Tue, Dec 19, 2006, Fred L. Drake, Jr. wrote:
> On Tuesday 19 December 2006 16:47, Terry Reedy wrote:
>>
>> Perhaps for some, but I would expect that docs cluttered with 'New/changed
>> in 3.0' to be just as confusing for others. Perhaps we need two versions
>> of the docs: a Python x.y set and
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
I've written a quick version of PEP 3106, which expresses my ideas
about how the dict methods to access keys, values and items should be
redone.
The text is in svn:
http://svn.python.org/view/peps/trunk/pep-3106.txt?rev=53096&view=markup
On 12/20/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Jim Jewett <[EMAIL PROTECTED]> wrote:
> > [(lambda i=i: i) for i in range(10)]
> > =>
> > [(lambda i=0_i: i) for 0_i in range(10)]
> > The argument to lambda can't be renamed, because it could be called as
> > a keywo
On 12/20/06, Jim Jewett <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 12/20/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> > > I haven't actually tried to implement that, though, and I suspect things
> > > will
> > > get a little tricky when it comes t
Talin wrote:
> 1) values() should be documented as list-like rather than set-like.
> (Or
> better yet bag-like, but Python doesn't have bags. In other words,
> it's
> really an unordered collection of items with no special indexing
> semantics or uniqueness constraint.)
>
> My reasoning is that
On 12/20/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> > I haven't actually tried to implement that, though, and I suspect things
> > will
> > get a little tricky when it comes to dealing with nested scopes like
> > '[(lambda
> > i=i: i)
OK, cool, never mind then. Sorry for being impatient!
On 12/20/06, Tony Lownds <[EMAIL PROTECTED]> wrote:
> I can get the patch clean again and work on the Neal's comments. I'm
> happy
> for the feedback.
>
> Thanks
> -Tony
>
> On Dec 20, 2006, at 9:32 AM, Guido van Rossum wrote:
>
> > Tony Lownds
At Guido's suggestion, a new mailing list has been created named
Python-Ideas (http://mail.python.org/mailman/listinfo/python-ideas). This
list is meant as a place for speculative, pie-in-the-sky language design
ideas to be discussed and honed to the point of practically being a PEP
before being
On 12/20/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:
> No, but I view sys as place to put stuff that influences the running of
> the interpreter and I don't put compile() in that category.
So what about sys.argv, sys.std{in,out,err},
sys.exc_info, etc. etc.? They're not exact
I can get the patch clean again and work on the Neal's comments. I'm
happy
for the feedback.
Thanks
-Tony
On Dec 20, 2006, at 9:32 AM, Guido van Rossum wrote:
> Tony Lownds created the original patch but (probably due to Thomas
> Wouters' recent merge) the patch doesn't apply cleanly any more.
Tony Lownds created the original patch but (probably due to Thomas
Wouters' recent merge) the patch doesn't apply cleanly any more. Tony
hasn't responded on SF yet. Neal Norwitz added a lot of useful
commentary to the SF item too. Perhaps someone can run with this?
--
--Guido van Rossum (home pag
On 12/20/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Georg Brandl wrote:
> > I'll implement it if only someone can point me in the right direction
> > how to do it.
>
> One idea I've had on that front is to persuade the compiler to replace the
> names used for the iteration variables in the sourc
On 12/20/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Looking at a fix Georg just checked in for intern() - is there a way for the
> fixer to indicate to the refactoring tool that a particular module needs to be
> imported if the module being refactored triggers a match on the fix?
Not yet; I rea
Guido van Rossum wrote:
> In the sandbox I've been working on a refactoring tool, which could
> form the basis for a Python 2.x -> 3.0 conversion tool. I'd like to
> invite folks here to give it a try and give me a hand. It certainly
> needs more work, but I think that the basic infrastructure is
Georg Brandl wrote:
> Guido van Rossum schrieb:
>> On 12/19/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
- turning list comprehensions into syntactic sugar for generator
expressions
>>> I'd like to point out that there is already my patch for that, which
>>> implements
>>> set comprehens
Nick Coghlan wrote:
> [1] 'containertools'?, 'collectiontools'?, 'collections.utils'? I suspect a
> BDFL name pronouncement will be needed if we pursue this idea :)
Oops - deleted the idea, but forgot to delete the related footnote. Anyway,
the idea was to move ListMixin and DictMixin into a sin
Guido van Rossum wrote:
> I've written a quick version of PEP 3106, which expresses my ideas
> about how the dict methods to access keys, values and items should be
> redone.
>
> The text is in svn:
> http://svn.python.org/view/peps/trunk/pep-3106.txt?rev=53096&view=markup
>
> At some point it wi
Guido van Rossum wrote:
> I've written a quick version of PEP 3106, which expresses my ideas
> about how the dict methods to access keys, values and items should be
> redone.
>
> The text is in svn:
> http://svn.python.org/view/peps/trunk/pep-3106.txt?rev=53096&view=markup
>
> At some point it wi
Guido van Rossum schrieb:
> On 12/19/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> > - turning list comprehensions into syntactic sugar for generator
>> > expressions
>>
>> I'd like to point out that there is already my patch for that, which
>> implements
>> set comprehensions and list comprehen
Talin wrote:
> 2) Names for d_keys, et al:
>
>-- map_keys_view
>-- map_values_view
>-- map_keys_values_view or map_items_view
I didn't think we were going to attempt to implement
any of these generically. I thought each type would
provide its own implementations tuned to the details
Brett Cannon wrote:
> No, but I view sys as place to put stuff that influences the running of
> the interpreter and I don't put compile() in that category.
So what about sys.argv, sys.std{in,out,err},
sys.exc_info, etc. etc.? They're not exactly
about influencing the running of the interpreter,
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/18/06, Brett Cannon <[EMAIL PROTECTED]> wrote:
> [me]
> > > Well, what do you think of my pronouncement in response to Thomas's
> > > mail (just rename a bunch of things that don't conform to our own
> > > naming standard)? That shoul
On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/19/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > Okay, I updated the patch at SF. While you're at it, in PEP 3100 there's
> > "compile(): put in sys (or perhaps in a module of its own)". I guess that
> > isn't really necessary eithe
30 matches
Mail list logo
