On Monday, May 23, 2016 at 2:17:07 AM UTC-4, Pete Forman wrote:
> rocky writes:
>
> > I'm looking for a good name for a relatively new project I'll put on pypy.
> >
> > I've been working on a module to disassemble Python bytecode from many
> > versions of Python. (Right now 2.3 .. 3.5 bytecode, l
Rustom Mody writes:
> On Monday, May 23, 2016 at 1:38:41 PM UTC+5:30, rocky wrote:
>> On Monday, May 23, 2016 at 2:17:07 AM UTC-4, Pete Forman wrote:
>> > rocky writes:
>> >
>> > > I'm looking for a good name for a relatively new project I'll put
>> > > on pypy.
>> > >
>> > > I've been working o
On Monday, May 23, 2016 at 1:38:41 PM UTC+5:30, rocky wrote:
> On Monday, May 23, 2016 at 2:17:07 AM UTC-4, Pete Forman wrote:
> > rocky writes:
> >
> > > I'm looking for a good name for a relatively new project I'll put on pypy.
> > >
> > > I've been working on a module to disassemble Python byt
On Monday, May 23, 2016 at 2:17:07 AM UTC-4, Pete Forman wrote:
> rocky writes:
>
> > I'm looking for a good name for a relatively new project I'll put on pypy.
> >
> > I've been working on a module to disassemble Python bytecode from many
> > versions of Python. (Right now 2.3 .. 3.5 bytecode, l
rocky writes:
> I'm looking for a good name for a relatively new project I'll put on pypy.
>
> I've been working on a module to disassemble Python bytecode from many
> versions of Python. (Right now 2.3 .. 3.5 bytecode, largely works.)
>
> Of course, in order to do that you also need routines to