Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whatsnew.rst: Fix typos discovered by codespell #97

Merged
merged 1 commit into from
Jul 25, 2024
Merged

whatsnew.rst: Fix typos discovered by codespell #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/source/whatsnew.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ v1.14

As a workaround that works on all versions of cffi, you can write
``lib.myfunc(ffi.new("float[]", [large list]))``, which is
equivalent but explicity builds the intermediate array as a regular
equivalent but explicitly builds the intermediate array as a regular
Python object on the heap.

* fixed a memory leak inside ``ffi.getwinerror()`` on CPython 3.x.
Expand Down Expand Up @@ -252,7 +252,7 @@ v1.12
keyword or by calling the new ``ffi.release()``.

* Windows, CPython 3.x: cffi modules are linked with ``python3.dll``
again. This makes them independant on the exact CPython version,
again. This makes them independent on the exact CPython version,
like they are on other platforms. **It requires virtualenv 16.0.0.**

* Accept an expression like ``ffi.new("int[4]", p)`` if ``p`` is itself
Expand Down Expand Up @@ -520,7 +520,7 @@ v1.9
the new file descriptor is only closed when the GC reclaims the Python
file object---and not at the earlier time when you call ``close()``,
which only closes the original file descriptor. If this is an issue,
you should avoid this automatic convertion of Python file objects:
you should avoid this automatic conversion of Python file objects:
instead, explicitly manipulate file descriptors and call ``fdopen()``
from C (...via cffi).

Expand Down
Loading