Re: Odd behavior regarding a list

2009-03-26 Thread Rhodri James
On Thu, 26 Mar 2009 17:01:40 -, Edd Barrett wrote: On Mar 26, 4:21 pm, Steven D'Aprano wrote: A few more comments, based on your code. >    def __classdef_integer(self): Double-underscore name mangling is often more trouble than it is worth. Unless you really need it, not just think you

Re: Odd behavior regarding a list

2009-03-26 Thread Edd Barrett
Hi there, First of all, thanks to everyone for replying. This has been a great help. On Mar 26, 4:21 pm, Steven D'Aprano wrote: > On Thu, 26 Mar 2009 08:36:49 -0700, Edd Barrett wrote: > > My question is: why has 'parent_struct_sig' changed? I was under the > > impression the assignment operator

Re: Odd behavior regarding a list

2009-03-26 Thread Steven D'Aprano
On Thu, 26 Mar 2009 08:36:49 -0700, Edd Barrett wrote: > Hi there, > > My first post here, so hello :) Hello and welcome. Let me comment on a few things out of order. > My question is: why has 'parent_struct_sig' changed? I was under the > impression the assignment operator copies, not referen

Re: Odd behavior regarding a list

2009-03-26 Thread Dave Angel
But you didn't do an assignment, you did an append. Append modifies the object, which is referenced by both parent_struct_sig and this_cdata["struct-sig"] If you're sure you want a *copy* of the list before the modifications, you might do something like parent_struct_sig = \

Re: Odd behavior regarding a list

2009-03-26 Thread Albert Hopkins
On Thu, 2009-03-26 at 08:36 -0700, Edd Barrett wrote: > Hi there, > > My first post here, so hello :) > > Just a little background, I am writing my dissertation, which is a JIT > compiler based upon LLVM and it's python bindings, along with the > aperiot LL(1) parser. > > I have some code here,