From parsing a class to code object to class to mappingproxy to object (oh my!)

I have been mimicking basic Python object constructs successfully until I started trying to handle methods as well in my hand-written interpreter. At that point, I wasn't sure where to stage all the methods before they get shuffled over to an actual instance of an object. I'm having to slap this

Re: Syntax for one-line "nonymous" functions in "declaration style"

On dim., Mar 31, 2019 at 6:00 PM, [email protected] wrote: On Sat, Mar 30, 2019, 5:32 AM Alexey Muranov wrote: On ven., Mar 29, 2019 at 4:51 PM, [email protected] wrote: > > There could perhaps be a special case for lambda expressions such > that, > when the

Re: Syntax for one-line "nonymous" functions in "declaration style"

On Sun, Mar 31, 2019 at 1:09 PM Alexey Muranov wrote: > > On dim., Mar 31, 2019 at 6:00 PM, [email protected] wrote: > > On Sat, Mar 30, 2019, 5:32 AM Alexey Muranov > > > > wrote: > > > >> > >> On ven., Mar 29, 2019 at 4:51 PM, [email protected] > >> wrote: > >> > > >

Re: From parsing a class to code object to class to mappingproxy to object (oh my!)

[email protected] wrote: What is the plumbing taking the result of that code object over to this proxy? I'm assuming __build_class__ runs that code object and then starts looking for new names and see to create this. Is this mapping proxy the important thing for carrying the method declar