summaryrefslogtreecommitdiff
path: root/c/test_c.py
Commit message (Collapse)AuthorAgeFilesLines
* Replace py.test usage with pytest, explicitly require py for testspy.testMiro Hrončok2022-11-111-194/+193
| | | | | | | pytest 7.2+ no longer depends on py. It ships py.path and py.error only. See https://docs.pytest.org/en/7.2.x/changelog.html#deprecations The tests use py.code as well, hence we declare and document a test dependency on py.
* Adjust tests for a last minute Python 3.11 change in the traceback formatpython3.11.0b4Miro Hrončok2022-07-151-33/+2
| | | | | See https://github.com/python/cpython/issues/93883 and https://github.com/python/cpython/pull/93994
* musllinux test updates and wheels, py3.11 beta wheelsMatt Davis2022-06-291-2/+13
|
* tweak the test for pypy, where we get an extra null byte after a plain 'char'Armin Rigo2022-06-081-1/+1
|
* dump version to 1.15.1Armin Rigo2022-06-081-1/+1
|
* issue #535Armin Rigo2022-06-081-0/+27
| | | | | Give a warning when we ask a ffi.buffer() that can be proven to overflow. Might help with the confusion on that issue #535.
* apply patch from Tomáš on PR 111adapt-tests-for-python3.11Armin Rigo2022-02-011-1/+46
|
* Backed out changeset: e184bbd523d6Armin Rigo2022-02-011-7/+0
|
* Adapt tests for Python 3.11Tomáš Hrnčiar2022-01-241-0/+7
| | | | Fix broken tests, Python 3.11 brings in enhanced error locations in tracebacks.
* Bump version to 1.15.0Matt Davis2021-10-121-1/+1
|
* Bump version to 1.15.0rc2Matt Davis2021-10-041-1/+1
|
* Bump version to 1.15.0rc1Matt Davis2021-09-171-1/+1
|
* Bump version to 1.14.6Armin Rigo2021-06-201-1/+1
|
* fix tests for py.test running on CPython v3.10.0b3Armin Rigo2021-06-201-0/+2
|
* fix for fdc0cbcdb65f on pre-3.10 pythonsArmin Rigo2021-06-201-2/+2
|
* fix a test that fails in the 3.10 alphas and will start failing on pypy soonfix-attribute-error-test-3.10Carl Friedrich Bolz-Tereick2021-04-241-2/+4
| | | | once I merge that feature: AttributeError is printing extra information
* #492Armin Rigo2021-02-191-1/+39
| | | | | | Python 3.8 adds support for sys.unraisablehook(), but also a new _PyErr_WriteUnraisableMsg() that calls it and is slightly more flexible in displaying the error message. Use that
* Bump version to 1.14.5 and add whatsnew entryArmin Rigo2021-02-111-1/+1
|
* add some more testsArmin Rigo2020-12-211-0/+5
|
* A test that passes on CPython but fails on PyPyArmin Rigo2020-12-211-0/+9
|
* bump version to 1.14.4Armin Rigo2020-11-241-1/+1
|
* Issue #475Armin Rigo2020-10-141-1/+1
| | | | | Fix a crash that can occur only if there is an error when building a callback (in very rare cases), or in debug mode.
* py3Armin Rigo2020-10-141-2/+2
|
* explicit test of unaligned pointer reads/writesArmin Rigo2020-09-231-0/+21
|
* bump version to 1.14.3Armin Rigo2020-09-151-1/+1
|
* this test is fragile on a non-translated pypy, skip itArmin Rigo2020-09-031-2/+2
|
* let the test run directly on pypy tooArmin Rigo2020-08-301-11/+11
|
* bump version number to 1.14.2Armin Rigo2020-08-151-1/+1
|
* bump version number to 1.14.1Armin Rigo2020-07-261-1/+1
|
* hack around until I make recent pytest versions happyArmin Rigo2020-07-171-4/+9
|
* Systematically expose all types on the _cffi_backend moduleArmin Rigo2020-05-281-7/+38
| | | | | under their correct name. This name starts with '__' if it is supposed to be non-portable and not guaranteed.
* Issue #447Armin Rigo2020-05-201-1/+8
| | | | | | | Fix the name of some types to be exactly the name under which they are exposed. Put underscores in front of the CDataXxx type names and a docstring that explains why.
* Bump version number to 1.14.0Armin Rigo2020-02-071-1/+1
|
* update version to 1.13.2Armin Rigo2019-11-031-1/+1
|
* bump version to 1.13.1Armin Rigo2019-10-211-1/+1
|
* Issue 421: integer overflow when computing structure sizes in bits and there ↵Armin Rigo2019-09-291-0/+8
| | | | are more than sys.maxint bits
* Give a RuntimeError when we try to call a null function pointer, similar to howArmin Rigo2019-08-171-0/+7
| | | | we get a RuntimeError when trying to read or write through a null pointer.
* bump version number to 1.13Armin Rigo2019-06-031-1/+1
|
* on py.py, bytearray buffers are not emulated well enoughArmin Rigo2019-06-031-4/+6
|
* Simplify the implementation, cut down the explanations, and allowArmin Rigo2019-06-031-35/+27
| | | | | | accessing multiple items instead of just one in from_buffer("type *"), trading off security for the realisation that it makes sense to access multiple items in some cases (unlike after ffi.new()).
* Support for from_buffer("type *")Armin Rigo2019-05-261-7/+84
|
* bump version to 1.12.3Armin Rigo2019-04-111-1/+1
|
* Two more casesArmin Rigo2019-04-021-0/+4
|
* improve the test on py2.7Armin Rigo2019-04-021-0/+2
|
* Shut down a warning from recent CPython versions: int() shouldArmin Rigo2019-04-021-0/+5
| | | | always return an int, not a bool
* Fix deprecated uses of pytest.raises()Ronan Lamy2019-03-121-103/+196
|
* Add an extra test directly here, for pypyArmin Rigo2019-03-111-0/+9
|
* bump version number to 1.12.2Armin Rigo2019-02-261-1/+1
|
* bump version number to 1.12.1Armin Rigo2019-02-161-1/+1
|
* Implement ffi.from_buffer("foo[]", x)Armin Rigo2019-01-071-0/+58
| | | | | Also contains some improvements to the documentation about other recent additions