in now, but you should be able to find it in the archive
with this subject and a date of 2006-03-08.
On Fri, 2006-03-10 at 12:46 +1300, Greg Ewing wrote:
> Steven Elliott wrote:
> > One way of handling it is to
> > alter STORE_ATTR (op code for assigning to mod.str) to always che
ook into python-ideas.
--
-------
| Steven Elliott | [EMAIL PROTECTED] |
---
___
Python-Dev ma
;`On Thu, 2007-02-22 at 01:26 +0100, Giovanni Bajo wrote:
> On 20/02/2007 16.07, Steven Elliott wrote:
>
> > I'm finally getting back into this. I'd like to take one more shot at
> > it with a revised version of what I proposed before.
> >
> > For th
lt builtin would just
create global variables.
Perhaps what I'm suggesting isn't feasible for reasons that have already
been discussed. But it seems like it should be possible to make "while
True" as efficient as "while 1".
--
----
On Thu, 2006-03-09 at 12:00 +, Paul Moore wrote:
> On 3/9/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> > Steven Elliott wrote:
> > > I'm interested in how builtins could be more efficient. I've read over
> > > some of the PEPs having to do with m
On Fri, 2006-03-10 at 12:46 +1300, Greg Ewing wrote:
> Steven Elliott wrote:
> > One way of handling it is to
> > alter STORE_ATTR (op code for assigning to mod.str) to always check to
> > see if the key being assigned is one of the default builtins. If it is,
> > then
On Thu, 2006-03-09 at 08:51 -0800, Raymond Hettinger wrote:
> [Steven Elliott]
> > As you probably know each access of a builtin requires two hash table
> > lookups. First, the builtin is not found in the list of globals. It is
> > then found in the list of builtins.
>
&
Hello All,
I am new to this list, but I have been lurking around getting a feel for the
environment and processes. I had some discussion yesterday about the
developer documentation as well, since it’s what I do professionally. I am a
technical writer but also work in the web development arena (us
If we can recruit a bunch of somebodies who *do* care, then the wiki
> would be much more useful. But I still don't want to edit the
> dev docs there, if I have a choice :) There's a reason I stopped
> updating the wiki as soon as I moved to a code repository.
>
>
I think that there are plent
