diff options
author | Armin Rigo <arigo@tunes.org> | 2019-02-16 13:19:09 +0100 |
---|---|---|
committer | Armin Rigo <arigo@tunes.org> | 2019-02-16 13:19:09 +0100 |
commit | f33d385d849d44902b2d5bab773531311ac9a10c (patch) | |
tree | de54fe022ce923ee6e89411beab4f118ea79e07b /doc | |
parent | 798b5dfcfd9dfa826e4ed88a80e52043d31bfdab (diff) | |
download | cffi-f33d385d849d44902b2d5bab773531311ac9a10c.tar.gz |
whatsnew
Diffstat (limited to 'doc')
-rw-r--r-- | doc/source/whatsnew.rst | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/source/whatsnew.rst b/doc/source/whatsnew.rst index a716e39..e8feed9 100644 --- a/doc/source/whatsnew.rst +++ b/doc/source/whatsnew.rst @@ -3,6 +3,22 @@ What's New ====================== +v1.12.1 +======= + +* CPython 3 on Windows: we again no longer compile with ``Py_LIMITED_API`` + by default because such modules *still* cannot be used with virtualenv. + The problem is that it doesn't work in CPython <= 3.4, and for + technical reason we can't enable this flag automatically based on the + version of Python. + + Like before, `Issue #350`_ mentions a workaround if you still want + the ``Py_LIMITED_API`` flag and *either* you are not concerned about + virtualenv *or* you are sure your module will not be used on CPython + <= 3.4: pass ``define_macros=[("Py_LIMITED_API", None)]`` to the + ``ffibuilder.set_source()`` call. + + v1.12 ===== |