Kaydet (Commit) 5697c4b6 authored tarafından Serhiy Storchaka's avatar Serhiy Storchaka

Comment fixes extracted from patch by Demur Rumed.

üst 0db9016a
...@@ -130,10 +130,6 @@ _code_type = type(_write_atomic.__code__) ...@@ -130,10 +130,6 @@ _code_type = type(_write_atomic.__code__)
# a .pyc file in text mode the magic number will be wrong; also, the # a .pyc file in text mode the magic number will be wrong; also, the
# Apple MPW compiler swaps their values, botching string constants. # Apple MPW compiler swaps their values, botching string constants.
# #
# The magic numbers must be spaced apart at least 2 values, as the
# -U interpeter flag will cause MAGIC+1 being used. They have been
# odd numbers for some time now.
#
# There were a variety of old schemes for setting the magic number. # There were a variety of old schemes for setting the magic number.
# The current working scheme is to increment the previous value by # The current working scheme is to increment the previous value by
# 10. # 10.
......
...@@ -2132,7 +2132,7 @@ _Py_CheckFunctionResult(PyObject *func, PyObject *result, const char *where) ...@@ -2132,7 +2132,7 @@ _Py_CheckFunctionResult(PyObject *func, PyObject *result, const char *where)
"%s returned NULL without setting an error", "%s returned NULL without setting an error",
where); where);
#ifdef Py_DEBUG #ifdef Py_DEBUG
/* Ensure that the bug is catched in debug mode */ /* Ensure that the bug is caught in debug mode */
Py_FatalError("a function returned NULL without setting an error"); Py_FatalError("a function returned NULL without setting an error");
#endif #endif
return NULL; return NULL;
......
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment