Editing Python/Harmattan/Performance Considerations for Python Apps
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 34: | Line 34: | ||
Do these work with Arm? | Do these work with Arm? | ||
- | ==== | + | ==== Shedskin ==== |
- | + | ||
- | + | Converts a restricted subset of python into C++ | |
- | + | ||
- | + | ?? | |
- | + | ||
==== Delegating to C with CTypes/SWIG ==== | ==== Delegating to C with CTypes/SWIG ==== | ||
Line 168: | Line 167: | ||
The standard response of "it depends". For a graphical application not doing too much processing a user will probably not notice it is written in Python. Compare that to an experiment by epage in writing a GST video filter in Python that at best ran at 2 seconds per frame. | The standard response of "it depends". For a graphical application not doing too much processing a user will probably not notice it is written in Python. Compare that to an experiment by epage in writing a GST video filter in Python that at best ran at 2 seconds per frame. | ||
- | |||
- | |||
- | |||
- | |||
[[Category:Python]] | [[Category:Python]] |
Learn more about Contributing to the wiki.