Remove traces of division_warning left over from Python 2 (#10998)
This commit is contained in:
parent
79fe2a3462
commit
be3bd57ba2
|
@ -232,8 +232,6 @@ always available.
|
|||
+==============================+==========================================+
|
||||
| :const:`debug` | -d |
|
||||
+------------------------------+------------------------------------------+
|
||||
| :const:`division_warning` | -Q |
|
||||
+------------------------------+------------------------------------------+
|
||||
| :const:`inspect` | -i |
|
||||
+------------------------------+------------------------------------------+
|
||||
| :const:`interactive` | -i |
|
||||
|
|
|
@ -133,3 +133,7 @@ that may require changes to your code:
|
|||
``import site`` will not add site-specific paths to the module search
|
||||
paths. In previous versions, it did. See changeset for doc changes in
|
||||
various files. Contributed by Carl Meyer with editions by Éric Araujo.
|
||||
|
||||
.. Issue #10998: -Q command-line flags are related artifacts have been
|
||||
removed. Code checking sys.flags.division_warning will need updating.
|
||||
Contributed by Éric Araujo.
|
||||
|
|
|
@ -16,7 +16,6 @@ PyAPI_DATA(int) Py_BytesWarningFlag;
|
|||
PyAPI_DATA(int) Py_UseClassExceptionsFlag;
|
||||
PyAPI_DATA(int) Py_FrozenFlag;
|
||||
PyAPI_DATA(int) Py_IgnoreEnvironmentFlag;
|
||||
PyAPI_DATA(int) Py_DivisionWarningFlag;
|
||||
PyAPI_DATA(int) Py_DontWriteBytecodeFlag;
|
||||
PyAPI_DATA(int) Py_NoUserSiteDirectory;
|
||||
PyAPI_DATA(int) Py_UnbufferedStdioFlag;
|
||||
|
|
|
@ -31,12 +31,6 @@ class CmdLineTest(unittest.TestCase):
|
|||
self.verify_valid_flag('-O')
|
||||
self.verify_valid_flag('-OO')
|
||||
|
||||
def test_q(self):
|
||||
self.verify_valid_flag('-Qold')
|
||||
self.verify_valid_flag('-Qnew')
|
||||
self.verify_valid_flag('-Qwarn')
|
||||
self.verify_valid_flag('-Qwarnall')
|
||||
|
||||
def test_site_flag(self):
|
||||
self.verify_valid_flag('-S')
|
||||
|
||||
|
|
|
@ -501,7 +501,7 @@ class SysModuleTest(unittest.TestCase):
|
|||
|
||||
def test_sys_flags(self):
|
||||
self.assertTrue(sys.flags)
|
||||
attrs = ("debug", "division_warning",
|
||||
attrs = ("debug",
|
||||
"inspect", "interactive", "optimize", "dont_write_bytecode",
|
||||
"no_user_site", "no_site", "ignore_environment", "verbose",
|
||||
"bytes_warning", "quiet")
|
||||
|
|
|
@ -10,6 +10,9 @@ What's New in Python 3.3 Alpha 1?
|
|||
Core and Builtins
|
||||
-----------------
|
||||
|
||||
- Issue #10998: Remove mentions of -Q, sys.flags.division_warning and
|
||||
Py_DivisionWarningFlag left over from Python 2.
|
||||
|
||||
- Issue #11244: Remove an unnecessary peepholer check that was preventing
|
||||
negative zeros from being constant-folded properly.
|
||||
|
||||
|
|
|
@ -37,10 +37,6 @@ python \- an interpreted, interactive, object-oriented programming language
|
|||
.B \-O0
|
||||
]
|
||||
[
|
||||
.B -Q
|
||||
.I argument
|
||||
]
|
||||
[
|
||||
.B \-s
|
||||
]
|
||||
[
|
||||
|
@ -152,15 +148,6 @@ Discard docstrings in addition to the \fB-O\fP optimizations.
|
|||
Do not print the version and copyright messages. These messages are
|
||||
also suppressed in non-interactive mode.
|
||||
.TP
|
||||
.BI "\-Q " argument
|
||||
Division control; see PEP 238. The argument must be one of "old" (the
|
||||
default, int/int and long/long return an int or long), "new" (new
|
||||
division semantics, i.e. int/int and long/long returns a float),
|
||||
"warn" (old division semantics with a warning for int/int and
|
||||
long/long), or "warnall" (old division semantics with a warning for
|
||||
all use of the division operator). For a use of "warnall", see the
|
||||
Tools/scripts/fixdiv.py script.
|
||||
.TP
|
||||
.B \-s
|
||||
Don't add user site directory to sys.path.
|
||||
.TP
|
||||
|
|
|
@ -29,8 +29,6 @@ _Py_GetRefTotal(void)
|
|||
}
|
||||
#endif /* Py_REF_DEBUG */
|
||||
|
||||
int Py_DivisionWarningFlag;
|
||||
|
||||
/* Object allocation routines used by NEWOBJ and NEWVAROBJ macros.
|
||||
These are used by the individual routines for object creation.
|
||||
Do not call them otherwise, they do not initialize the object! */
|
||||
|
|
|
@ -1312,7 +1312,6 @@ static PyTypeObject FlagsType;
|
|||
|
||||
static PyStructSequence_Field flags_fields[] = {
|
||||
{"debug", "-d"},
|
||||
{"division_warning", "-Q"},
|
||||
{"inspect", "-i"},
|
||||
{"interactive", "-i"},
|
||||
{"optimize", "-O or -OO"},
|
||||
|
@ -1336,9 +1335,9 @@ static PyStructSequence_Desc flags_desc = {
|
|||
flags__doc__, /* doc */
|
||||
flags_fields, /* fields */
|
||||
#ifdef RISCOS
|
||||
13
|
||||
#else
|
||||
12
|
||||
#else
|
||||
11
|
||||
#endif
|
||||
};
|
||||
|
||||
|
@ -1356,7 +1355,6 @@ make_flags(void)
|
|||
PyStructSequence_SET_ITEM(seq, pos++, PyLong_FromLong(flag))
|
||||
|
||||
SetFlag(Py_DebugFlag);
|
||||
SetFlag(Py_DivisionWarningFlag);
|
||||
SetFlag(Py_InspectFlag);
|
||||
SetFlag(Py_InteractiveFlag);
|
||||
SetFlag(Py_OptimizeFlag);
|
||||
|
|
Loading…
Reference in New Issue