Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b45b9fe

Browse files
author
Skip Montanaro
committed
fix a couple nits related to my understanding of ReST. Use of
``void (*)(PyObject *)`` isn't quite the same as void (*)(PyObject \*) but I gather ``...`` is preferable stylistically in most cases than ... \*...
1 parent d20b665 commit b45b9fe

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

Misc/NEWS.help

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,8 @@ The changes required fell into the following categories:
3434
* In a few places asterisks needed to be escaped which would otherwise have
3535
been interpreted as beginning blocks of italic or bold text, e.g.:
3636

37-
- The type of tp_free has been changed from "void (*)(PyObject \*)"
38-
to "void (*)(void \*)".
37+
- The type of tp_free has been changed from "``void (*)(PyObject *)``"
38+
to "``void (*)(void *)``".
3939

4040
Note that only the asterisks preceded by whitespace needed to be escaped.
4141

@@ -52,7 +52,7 @@ The changes required fell into the following categories:
5252
- Note that PyLong_AsDouble can fail! This has always been true,
5353
but no callers checked for it. It's more likely to fail now,
5454
because overflow errors are properly detected now. The proper way
55-
to check: ::
55+
to check::
5656

5757
double x = PyLong_AsDouble(some_long_object);
5858
if (x == -1.0 && PyErr_Occurred()) {

0 commit comments

Comments
 (0)