summaryrefslogtreecommitdiff
path: root/testing/embedding
Commit message (Collapse)AuthorAgeFilesLines
* Windows: when a CFFI embedding attempt fails, attempt toArmin Rigo2017-06-161-0/+8
| | | | | | open a non-modal MessageBox() in addition to sending the detailed error to stderr... because stderr is likely to go nowhere, in case of non-console applications.
* Basic "does not crash" test for the error logic in _cffi_initialize_pythonArmin Rigo2017-06-162-0/+24
|
* Re-add this hack, removed in 51f1337c9b4c; but this time only in testsArmin Rigo2016-04-211-2/+15
|
* Test and fix for converting empty ffi's in embedding modeArmin Rigo2016-04-152-0/+13
|
* Python 3 compatArmin Rigo2016-03-161-1/+1
|
* Oops, tests fail if we run them one by oneArmin Rigo2016-03-021-2/+7
|
* more pypy tweaksArmin Rigo2016-02-191-23/+31
|
* Pfff, debug=True goes in the way on Windows if you don't explicitlyArmin Rigo2016-02-131-1/+5
| | | | have the debug version of the MS CRT installed first
* prepend dll path on win32mattip2016-02-021-1/+1
|
* allow embedding tests to run on pypy win32mattip2016-01-301-5/+11
|
* Support extensions for pydebug cpythonsStefano Rivera2016-01-171-4/+0
|
* Use os.pathsep instead of directly ':'Armin Rigo2016-01-171-2/+2
|
* Don't blow away PYTHONPATHStefano Rivera2016-01-171-4/+10
| | | | Rather parse it, and prefix our base directory, if necessary.
* Use mutex/condition variables instead of semaphores (for os/x)Armin Rigo2016-01-162-17/+55
|
* more tests passArmin Rigo2016-01-161-1/+1
|
* OS/X: in-progress, one test now passesArmin Rigo2016-01-161-0/+4
|
* fixArmin Rigo2016-01-161-0/+1
|
* Print all commands executed with all detailsArmin Rigo2016-01-161-13/+18
|
* fixes for pypyArmin Rigo2016-01-151-1/+1
|
* tried hard and failed to have the embedding tests run in a debug-mode pythonArmin Rigo2016-01-141-0/+4
|
* improve test, but it is failing under windowsArmin Rigo2016-01-121-2/+2
|
* fixArmin Rigo2016-01-121-2/+2
|
* (untested) trying to have the multithreaded tests run on windowsArmin Rigo2016-01-127-9/+68
|
* use declspec(dllimport/dllexport) on windowsArmin Rigo2016-01-122-3/+11
|
* Skip this test on windowsArmin Rigo2016-01-121-0/+5
|
* two tests pass on windows! progressArmin Rigo2016-01-121-4/+3
|
* Test and fixArmin Rigo2016-01-121-0/+4
|
* Maybe it's clearer this way, with an API that matches the intent ratherArmin Rigo2016-01-096-18/+18
| | | | than how the implementation piggy-backs on ``extern "Python"``
* Give up testing windows: it kinda seems to work but I really, really,Armin Rigo2016-01-081-0/+4
| | | | | really don't manage to make the tests pass. Call for help (we can be optimistic)
* tryArmin Rigo2016-01-081-1/+1
|
* tryArmin Rigo2016-01-081-1/+4
|
* fixArmin Rigo2016-01-081-1/+1
|
* trying win fixArmin Rigo2016-01-081-1/+8
|
* py3 compatArmin Rigo2016-01-087-8/+20
|
* Py3 fixArmin Rigo2016-01-081-1/+3
|
* Py3 fixes. Skip the embedding tests if linking with -lpython%d.%dArmin Rigo2016-01-087-21/+40
| | | | fails (likely, the Python was not compiled with --enable-shared)
* fixArmin Rigo2016-01-081-1/+6
|
* In-progress: fix tests to attempt to use distutils also for compilingArmin Rigo2016-01-0711-93/+76
| | | | the executable
* Allow platform-specific hacks to invoke the compilerArmin Rigo2016-01-074-16/+38
|
* Generalize a bitArmin Rigo2016-01-071-6/+16
|
* Stop running the embedding_init_code() code as if it was part of theArmin Rigo2016-01-076-3/+8
| | | | | | | 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.
* merge headsArmin Rigo2016-01-061-0/+7
|\
| * Check that the module is present in sys.modules at this point,Armin Rigo2016-01-061-0/+7
| | | | | | | | and that it is re-importable
* | Write a line when we run the final executable tooArmin Rigo2016-01-041-0/+1
|/
* updatesArmin Rigo2016-01-021-1/+1
|
* A test checking that thread-local values are saved, even thoughArmin Rigo2016-01-024-1/+85
| | | | there is no underlying official Python thread
* Pseudo-tests that print some performance numbers for calling an embeddedArmin Rigo2016-01-023-0/+151
| | | | "extern Python" function in a loop, with or without threads.
* We need fflush(stdout) here, for a possibly bad reason: cpython 2.xArmin Rigo2016-01-024-0/+4
| | | | | writes to stdout, so it gets in the correct order, but pypy (and likely cpython 3.x) writes directly to the file descriptor
* in-progress: a comment about eggs, and hacks to run the tests on pypy (some ↵Armin Rigo2016-01-021-3/+22
| | | | failures so far)
* fixesArmin Rigo2016-01-011-1/+1
|
View Lorry Controller Status