paul@148 | 1 | Shed Skin imposes various restrictions in order to facilitate compilation to
|
paul@148 | 2 | C++:
|
paul@148 | 3 |
|
paul@148 | 4 | http://shedskin.googlecode.com/
|
paul@148 | 5 |
|
paul@148 | 6 | RPython imposes different restrictions in order to facilitate compilation to
|
paul@148 | 7 | other languages:
|
paul@148 | 8 |
|
paul@148 | 9 | http://codespeak.net/pypy/dist/pypy/doc/coding-guide.html#restricted-python
|
paul@148 | 10 |
|
paul@148 | 11 | CapPython limits attribute access in order to facilitate code verification:
|
paul@148 | 12 |
|
paul@148 | 13 | http://mail.python.org/pipermail/python-dev/2008-September/082475.html
|
paul@266 | 14 |
|
paul@266 | 15 | Advocacy for limited module-level initialisation:
|
paul@266 | 16 |
|
paul@266 | 17 | http://plope.com/Members/chrism/import_time_side_effects
|
paul@290 | 18 |
|
paul@290 | 19 | A question about attributes illustrating Python's deficiencies around
|
paul@290 | 20 | compile-time error detection, met with properties dogma despite accessor
|
paul@290 | 21 | methods being genuinely appropriate in various situations:
|
paul@290 | 22 |
|
paul@290 | 23 | http://mail.python.org/pipermail/python-list/2009-November/1227265.html
|
paul@290 | 24 | http://groups.google.com/group/comp.lang.python/browse_frm/thread/c07268689549cf01/
|
paul@297 | 25 |
|
paul@297 | 26 | A discussion of how closures often obscure intent and how the use of classes
|
paul@297 | 27 | and functions is often preferable:
|
paul@297 | 28 |
|
paul@297 | 29 | http://artificialcode.blogspot.com/2009/04/python-functional-programming.html
|