>> Over the last several years, various people have reported
>> experimenting with CPython's bytecodes. I wonder if it would be
>> helpful to have a respository of the results, in one place, for new
>> experimenters and curious people to peruse.
Brett> Wouldn't hurt. Adding
Brett C. wrote:
Terry Reedy wrote:
"Brett C." <[EMAIL PROTECTED]> wrote
Over the last several years, various people have reported
experimenting with CPython's bytecodes. I wonder if it would be
helpful to have a respository of the results, in one place, for new
experimenters and curious peo
Terry Reedy wrote:
"Brett C." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
At to the title, bytecodes are a property of the CPython implementation,
not of Python itself. Since I think the distinction is quite important to
maintain, I would insert the missing 'C' and everywhere e
Scott David Daniels wrote:
Brett C. wrote:
A few things can be done to make sure that development goes smoothly when
experimenting with Python's bytecode. One is to delete all .py(c|o|w)
Don't you mean ".pyc or .pyo (remember such files in zips as well)"
.pyw is normal python source.
Yeah, my bad
"Brett C." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
At to the title, bytecodes are a property of the CPython implementation,
not of Python itself. Since I think the distinction is quite important to
maintain, I would insert the missing 'C' and everywhere else as
appropriat
Brett C. wrote:
A few things can be done to make sure that development goes smoothly when
experimenting with Python's bytecode. One is to delete all .py(c|o|w)
Don't you mean ".pyc or .pyo (remember such files in zips as well)"
.pyw is normal python source.
-- Scott David Daniels
[EMAIL PROTECTED
