Patch / Bug Summary
___
Patches : 408 open ( -9) / 3585 closed (+20) / 3993 total (+11)
Bugs: 968 open ( +8) / 6505 closed ( +7) / 7473 total (+15)
RFE : 267 open ( +1) / 251 closed ( +0) / 518 total ( +1)
New / Reopened Patches
__
Handle re
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 those of you that did not see the original thread it was about ways
> that accessing builtins could be more efficien
Josiah Carlson wrote:
> Somewhere in the back of my mind something is telling me - if you can
> get a tuple with attributes based on __slots__, you just duplicate the
> references as both an attribute AND in the standard tuple PyObject*
> array,
It should be possible to start with a tuple subclas
"Steven Bethard" <[EMAIL PROTECTED]> wrote:
[snip]
> In short, for object construction and attribute access, the Record
> class is faster (because __init__ is a simple list of assignments and
> attribute access is through C-level slots). For unpacking and
> iteration, the NamedTuple factory is fa
As Steve said, this is the wrong place to be asking for help about
this. We have *nothing* to do with mailing lists or Mailman.
Please read Steve's email again and follow the link in it. The people
on this list cannot help you with what you are asking for.
-Brett
On 2/21/07, Juan Carlos Suarez
On 2/20/07, Steven Bethard <[EMAIL PROTECTED]> wrote:
> Declare a simple class for your type and you're ready to go::
>
> >>> class Point(Record):
> ... __slots__ = 'x', 'y'
> ...
> >>> Point(3, 4)
> Point(x=3, y=4)
Here's a brief comparison between Raymond's NamedTuple fac
Fredrik Lundh schrieb:
>> My suspicion is that building Python for an 64-bit address space is
>> still a somewhat academic exercise.
>
> arbitrary 64-bit systems, perhaps. the first Python system I ever built was
> deployed
> on an LP64 system back in 1995. it's still running, and is still bein
On Tue, 2007-02-20 at 07:48 -0800, Guido van Rossum wrote:
> If this is not a replay of an old message, please move the discussion
> to python-ideas.
It's a modified version of an old idea, so I wasn't sure where to post
it since previously it was discussed here. I'll look into python-ideas.
--
Guido van Rossum wrote:
> My suspicion is that building Python for an 64-bit address space is
> still a somewhat academic exercise.
arbitrary 64-bit systems, perhaps. the first Python system I ever built was
deployed
on an LP64 system back in 1995. it's still running, and is still being
maint
Hello Steve Holden, I'm already registered and I want to be a list
administrator, where to go? How to do this? I need to have my own mail
address to administer my mailing list, do you understand me? I've been
trying to do this and I'm lost, I don't know where exactly to go, to which
address to
Michele Simionato gmail.com> writes:
> Finally I did some timing of code like this::
>
> from itertools import imap
> Point = namedtuple('Point x y'.split())
>
> lst = [(i, i*i) for i in range(500)]
>
> def with_imap():
> for _ in imap(Point, lst):
> pass
>
> def with_star()
Larry Hastings <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> > one thing to note with your method - you can't guarantee the order
> > of the attributes as they are being displayed.
> >
> Actually, my record type *can*; see the hack using the __names__ field.
> It won't preserve that
12 matches
Mail list logo
