search

sgk / python-on-a-chip

Automatically exported from code.google.com/p/python-on-a-chip
0 stars 0 forks source link

Add support for Python 2.6 bytecodes #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Add support for Python 2.6 bytecodes.

Original issue reported on code.google.com by dwhall...@gmail.com on 16 Apr 2009 at 7:27

GoogleCodeExporter commented 9 years ago 
At PyCon 2009, the BDFL asked that everybody work toward the transition to 
Python 3.0.  
For this reason, this issue will be skipped in favor of issue #14 which is to 
support 
Python 3.0 bytecodes (and compiler).

Original comment by dwhall...@gmail.com on 9 Sep 2009 at 7:59

GoogleCodeExporter commented 9 years ago 
Since issue #14 is shelved, this issue is re-instated.

Original comment by dwhall...@gmail.com on 14 Dec 2009 at 8:53

GoogleCodeExporter commented 9 years ago 
Issue 3 has been merged into this issue.

Original comment by dwhall...@gmail.com on 14 Dec 2009 at 9:13

GoogleCodeExporter commented 9 years ago 
The only new bytecodes in Python 2.6 are *_FLOOR_DIVIDE and STORE_MAP.

Original comment by dwhall...@gmail.com on 14 Dec 2009 at 9:14

GoogleCodeExporter commented 9 years ago 
There are 3 bytecodes in Python 2.6 that are not yet implemented: 
BINARY_TRUE_DIVIDE, 
INPLACE_TRUE_DIVIDE and STORE_MAP.  I was able to implement all three easily (I 
used 
the patch from issue #3), but could not generate test code that yielded the 
desired 
bytecodes.  So the bytecodes are untested.  I am going to check-in these 
untested 
bytecodes because there is no way for the Python 2.6 compiler to generate these 
bytecodes.  The "from __future__ import" device is needed to enable generation 
of these 
bytecodes, but is not supported.

Original comment by dwhall...@gmail.com on 15 Dec 2009 at 4:20

GoogleCodeExporter commented 9 years ago 
Created system test t213, but the test is unable to generate the new bytecodes, 
so all 
test cases are commented out.

Ran tests using python 2.6, all tests pass.

Mainlined directly, see r394.

Original comment by dwhall...@gmail.com on 15 Dec 2009 at 4:23

GoogleCodeExporter commented 9 years ago 
Changing Milestone-r10 to Milestone-r09

Original comment by dwhall...@gmail.com on 7 Mar 2010 at 6:26

GoogleCodeExporter commented 9 years ago 
Changed r09 to R09

Original comment by dwhall...@gmail.com on 12 Mar 2010 at 8:22

GoogleCodeExporter commented 9 years ago

Original comment by dwhall...@gmail.com on 13 Mar 2010 at 1:30