On Mon, Oct 3, 2016 at 9:58 AM, Cem Karan wrote:
>> To execute your own code, look at types.FunctionType and
>> types.CodeType, particularly the latter's 'codestring' argument
>> (stored as the co_code attribute). Be careful: you can easily crash
>> CPython if you mess this
On Oct 1, 2016, at 7:34 PM, breamore...@gmail.com wrote:
> On Saturday, October 1, 2016 at 11:57:17 PM UTC+1, Cem Karan wrote:
>> Hi all, I've all of a sudden gotten interested in the CPython interpreter,
>> and started trying to understand how it ingests and runs byte code. I found
>>
On Oct 1, 2016, at 8:30 PM, Ned Batchelder wrote:
> On Saturday, October 1, 2016 at 7:48:09 PM UTC-4, Cem Karan wrote:
>> Cool, thank you! Quick experimentation suggests that I don't need to worry
>> about marking anything for garbage collection, correct? The next
On Oct 1, 2016, at 7:56 PM, Chris Angelico wrote:
> On Sun, Oct 2, 2016 at 10:47 AM, Cem Karan wrote:
>> Cool, thank you! Quick experimentation suggests that I don't need to worry
>> about marking anything for garbage collection, correct? The next
I kind of got the feeling that was so from reading the docs in the source code.
Too bad! :(
Cem
On Oct 1, 2016, at 7:53 PM, Paul Rubin wrote:
> Cem Karan writes:
>> how do I create a stream of byte codes that can be interpreted by
>> CPython
On Saturday, October 1, 2016 at 11:57:17 PM UTC+1, Cem Karan wrote:
> Hi all, I've all of a sudden gotten interested in the CPython interpreter,
> and started trying to understand how it ingests and runs byte code. I found
> Include/opcode.h in the python sources, and I found some basic
On Saturday, October 1, 2016 at 7:48:09 PM UTC-4, Cem Karan wrote:
> Cool, thank you! Quick experimentation suggests that I don't need to worry
> about marking anything for garbage collection, correct? The next question
> is, how do I create a stream of byte codes that can be interpreted by
On Sun, Oct 2, 2016 at 10:47 AM, Cem Karan wrote:
> Cool, thank you! Quick experimentation suggests that I don't need to worry
> about marking anything for garbage collection, correct? The next question
> is, how do I create a stream of byte codes that can be interpreted
Cem Karan writes:
> how do I create a stream of byte codes that can be interpreted by
> CPython directly?
Basically, study the already existing code and do something similar.
The CPython bytecode isn't standardized like JVM bytecode. It's
designed for the interpreter's
Cool, thank you! Quick experimentation suggests that I don't need to worry
about marking anything for garbage collection, correct? The next question is,
how do I create a stream of byte codes that can be interpreted by CPython
directly? I don't mean 'use the compile module', I mean writing
Cem Karan writes:
> Hi all, I've all of a sudden gotten interested in the CPython
> interpreter, and started trying to understand how it ingests and runs
> byte code.
That sounds like fun!
> Is there something similar to a manual dedicated to python byte code?
The Python
11 matches
Mail list logo