| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Maybe it's clearer this way, with an API that matches the intent rather | Armin Rigo | 2016-01-09 | 1 | -3/+3 |
| | | | | | than how the implementation piggy-backs on ``extern "Python"`` | ||||
| * | py3 compat | Armin Rigo | 2016-01-08 | 1 | -1/+1 |
| | | |||||
| * | In-progress: fix tests to attempt to use distutils also for compiling | Armin Rigo | 2016-01-07 | 1 | -1/+2 |
| | | | | | the executable | ||||
| * | Stop running the embedding_init_code() code as if it was part of the | Armin Rigo | 2016-01-07 | 1 | -0/+2 |
| | | | | | | | | extension module. Instead, be explicit and require a "from xx import ffi" line. This is clearer because it is the same line needed at the start of other modules, if the logic becomes too large for this single triple-quoted string. | ||||
| * | Pseudo-tests that print some performance numbers for calling an embedded | Armin Rigo | 2016-01-02 | 1 | -0/+18 |
| "extern Python" function in a loop, with or without threads. | |||||
