[issue25296] Simple End-of-life guide covering all unsupported versions

Nick Coghlan added the comment: Adding Georg directly to the nosy, as I think this kind of structural question falls under his domain as the docs lead :) -- nosy: +georg.brandl ___ Python tracker

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

David Edelsohn added the comment: As we have seen with similar issues on other targets, this likely is due to the random order of tests. In another case, the timezone was not being restored properly by GLIBC. Another test is leaving the process in a state that somehow evokes this failure

[issue25296] Simple End-of-life guide covering all unsupported versions

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue25296] Simple End-of-life guide covering all unsupported versions

STINNER Victor added the comment: Davey Shafik added the comment: > We (PHP) also have a more visual guide at > http://php.net/supported-versions.php which updates dynamically to show the > current status. Great job! It's much easier to see the status with the summary in a single picture.

[issue25295] functools.lru_cache raises KeyError

Serhiy Storchaka added the comment: I don't know what was the actual cause of the error and if issue24483 fixed it or mask. -- ___ Python tracker ___

[issue25294] Absolute imports fail in some cases where relative imports would work

Changes by Berker Peksag : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

Stefan Krah added the comment: If you have time, you could use an explicit seed (and gdb): # test_email segfault: ./python -m test -j 1 -u all -W --randseed 5634141 -- ___ Python tracker

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

Stefan Krah added the comment: And the segfaults are apparently somewhat random. This is beginning to look like an issue unrelated to decimal that was perhaps recently introduced (in which case "hg bisect" would be the fastest way to debug).

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

STINNER Victor added the comment: I suggest to isolate tests using -j1: see my issue #25285. (Currently, -j1 doesn't use subprocesses.) -- ___ Python tracker

[issue19006] UnitTest docs should have a single list of assertions

Changes by Nicholas H.Tollervey : -- nosy: +kushal.das, ntoll ___ Python tracker ___ ___

[issue25297] max_help_position is not works in argparse library

Alexander added the comment: Problem also described on http://stackoverflow.com/questions/3215/ -- ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Ezio Melotti added the comment: I like that, in fact I used the same format in my talk "The development process of Python": http://wolfprojects.altervista.org/talks/development-process-of-python-2011/ (slides 20/21). The main problem is where to put all this though. --

[issue24848] Warts in UTF-7 error handling

STINNER Victor added the comment: http://buildbot.python.org/all/builders/x86%20XP-4%202.7/builds/3431/steps/test/logs/stdio == FAIL: test_errors (test.test_codecs.UTF7Test)

[issue23640] int.from_bytes() is broken for subclasses

ashutosh added the comment: hi i am ashutosh. I am running kubuntu 14.04. before applying the patch. It failed in 2 test i.e test___all__ test_re After applying patch. It again gave me 2 error test___all__ test_re So,it worked for me. -- nosy: +singh_jug

[issue25297] max_help_position is not works in argparse library

New submission from Alexander: Hi colleagues I have the code (max_help_position is 2000): formatter_class=lambda prog: argparse.HelpFormatter(prog, max_help_position=2000) parser = argparse.ArgumentParser(formatter_class=formatter_class) subparsers = parser.add_subparsers(title="Commands",

[issue24483] Avoid repeated hash calculation in C implementation of functools.lru_cache()

STINNER Victor added the comment: > New changeset 3f4c319a822f by Serhiy Storchaka in branch '3.5': > Issue #24483: C implementation of functools.lru_cache() now calculates key's > https://hg.python.org/cpython/rev/3f4c319a822f I didn't follow this issue, but I like the change. Good job :)

[issue25278] Unexpected socket exception on SFTP 'STOR' command

Eric V. Smith added the comment: You'll need to reproduce this in a smaller piece of code that demonstrates the problem. The code you've included is very large, and imports libraries we don't have access to. Otherwise, we can't reproduce it and we can't help. --

[issue25295] functools.lru_cache raises KeyError

Serhiy Storchaka added the comment: Issue24483 fixes this issue. -- dependencies: +Avoid repeated hash calculation in C implementation of functools.lru_cache() ___ Python tracker

[issue16802] fileno argument to socket.socket() undocumented

Bar Harel added the comment: Here you go. -- nosy: +bar.harel Added file: http://bugs.python.org/file40656/Issue16802_rev2.patch ___ Python tracker ___

[issue25276] test_decimal sometimes crash on PPC64 AIX 3.x

Stefan Krah added the comment: I've checked: test_decimal does not require abnormal amounts of memory or stack. On Linux/x86 a stack size of 256 (default 8192) is sufficient, and memory requirements aren't that high. We assumed that there is some memory limit on the buildbot, since in a later

[issue25295] functools.lru_cache raises KeyError

Changes by Serhiy Storchaka : -- nosy: +rhettinger, serhiy.storchaka type: -> behavior versions: +Python 3.6 ___ Python tracker ___

[issue19884] Importing readline produces erroneous output

Yogesh Joshi added the comment: I tried applying this patch and its failing and throwing the following error: patching file Lib/test/test_readline.py Hunk #1 FAILED at 1. Hunk #2 FAILED at 43. 2 out of 2 hunks FAILED -- saving rejects to file Lib/test/test_readline.py.rej patching file

[issue25296] Simple End-of-life guide covering all unsupported versions

Davey Shafik added the comment: We (PHP) also have a more visual guide at http://php.net/supported-versions.php which updates dynamically to show the current status. It shows the current status (EOL, Security only, Active) of releases from PHP 5.3, which is still the default for many LTS

[issue25298] Add lock and rlock weakref tests

Changes by Nir Soffer : -- components: Tests files: 0001-Add-lock-rlock-weakref-tests.patch keywords: patch nosy: nirs priority: normal severity: normal status: open title: Add lock and rlock weakref tests versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6 Added

[issue24483] Avoid repeated hash calculation in C implementation of functools.lru_cache()

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

New submission from A. Skrobov: Python 2.7.3 (default, Dec 18 2014, 19:10:20) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from argparse import ArgumentParser >>> parser = ArgumentParser() >>> parser.add_argument("--foo", help="foo",

[issue24657] CGIHTTPServer module discard continuous '/' letters from params given by GET method.

Xiang Zhang added the comment: Yes, there seems to still exist some defects not conforming to the specification. I would like to investigate it. Maybe I can propose a patch for it. -- ___ Python tracker

[issue25298] Add lock and rlock weakref tests

New submission from Nir Soffer: Same patch works also for 2.7 -- ___ Python tracker ___ ___ Python-bugs-list

[issue24848] Warts in UTF-7 error handling

Roundup Robot added the comment: New changeset 3c13567ea642 by Serhiy Storchaka in branch '3.4': Issue #24848: Fixed bugs in UTF-7 decoding of misformed data: https://hg.python.org/cpython/rev/3c13567ea642 New changeset a61fa2b08f87 by Serhiy Storchaka in branch '3.5': Issue #24848: Fixed bugs

[issue23640] int.from_bytes() is broken for subclasses

Yogesh Joshi added the comment: I applied patch to module and ran all the tested on Mac Os El Captain, only 4 tests were failing with or without applying patch, following are the tests failing: test___all__ test_calendar test_re test_socket -- nosy: +iyogeshjoshi

[issue25125] "Edit with IDLE" does not work for shortcuts

Terry J. Reedy added the comment: Putting them under the current 'Open with >' would also be alright. (It currently lists Notepad, Wordpad, and Py launcher for Windows (console), which I presume means run with default for Py. What I was requesting is that the version be included with the

[issue24483] Avoid repeated hash calculation in C implementation of functools.lru_cache()

Roundup Robot added the comment: New changeset 3f4c319a822f by Serhiy Storchaka in branch '3.5': Issue #24483: C implementation of functools.lru_cache() now calculates key's https://hg.python.org/cpython/rev/3f4c319a822f New changeset 5758b85627c9 by Serhiy Storchaka in branch 'default': Issue

[issue25294] Absolute imports fail in some cases where relative imports would work

Changes by J Richard Snape : -- nosy: +J Richard Snape ___ Python tracker ___ ___

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Changes by Florin Papa : Added file: http://bugs.python.org/file40658/mpx_enable_2_7.patch ___ Python tracker ___

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

New submission from Florin Papa: Hi all, My name is Florin Papa and I work in the Server Languages Optimizations Team at Intel Corporation. I would like to submit a patch that enables the use of the Intel MPX (Memory Protection Extensions) feature on Python default and 2.7. Invalid memory

[issue25296] Simple End-of-life guide covering all unsupported versions

R. David Murray added the comment: It seems to me a link to this version independent info could logically appear on the docs front page. I think we ought to add the devguide there already, for instance. The 'Meta information' section seems perfectly appropriate...even though all the docs

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list

[issue25296] Simple End-of-life guide covering all unsupported versions

Georg Brandl added the comment: It should also be linked from the downloads page. -- ___ Python tracker ___

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

R. David Murray added the comment: Oops, sorry, I missed the fact that you were pointing out a doc issue. -- resolution: out of date -> stage: resolved -> needs patch status: closed -> open ___ Python tracker

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Florin Papa added the comment: > Why not enablind the option by default if GCC 5.1 or newer is detected? Is > there a risk of breaking third-party extensions? > Should we pass the MPX compiler options to third-party extensions by way? On a processor that does not support MPX technology, MPX

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

paul j3 added the comment: A related issue is http://bugs.python.org/issue24754 argparse add_argument with action="store_true", type=bool should not crash In this case the user specified a parameter that the 'store_true' subclass did not accept. In both cases, 'parser.add_argument' does

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

R. David Murray added the comment: I think your second to last choice (catch the error) is the only practical solution. It is also probably the best, since we need to support user-written action routines. -- ___ Python tracker

[issue25297] max_help_position is not works in argparse library

Changes by paul j3 : -- nosy: +paul.j3 ___ Python tracker ___ ___ Python-bugs-list

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Stefan Krah added the comment: In principle adding the option is fine, but do we have a buildbot with a Skylake processor? We have lots of options that are untested and that break periodically. -- nosy: +zach.ware ___ Python tracker

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

A. Skrobov added the comment: Thank you for confirming that the mismatch between the documentation and the behaviour is preserved in Python 3! Adding it to the list of affected versions. -- versions: +Python 3.5 ___ Python tracker

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

R. David Murray added the comment: I think Intel will make sure we do have one. Florin: how does one determine if a processor supports mxp? I don't know if the mac mini running the ICC buildbot is new enough to have a Skylake processor, but I suppose there's at least some chance it does.

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

R. David Murray added the comment: To clarify this for other readers: the issue here is that the arguments to add_argument are passed through the action routine, which in this case is store_const, and store_const is the one that requires 'const' be specified...which isn't made clear by either

[issue25302] Memory Leaks with Address Sanitizer

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

[issue25097] test_logging may fail with 'Access is denied' when pywin32 is installed

Vinay Sajip added the comment: I'm not able to build on Windows at the moment, unfortunately - did the change actually work for you? -- ___ Python tracker

[issue24870] Optimize ascii and latin1 decoder with surrogateescape and surrogatepass error handlers

STINNER Victor added the comment: I created issue #25301: "Optimize UTF-8 decoder with error handlers". -- ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Georg Brandl added the comment: > It seems to me a link to this version independent info could logically appear > on the docs front page. Yes, that sounds good. I do like the PHP graph of versions too... -- ___ Python tracker

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

STINNER Victor added the comment: Why not enablind the option by default if GCC 5.1 or newer is detected? Is there a risk of breaking third-party extensions? Should we pass the MPX compiler options to third-party extensions by way? I'm not sure that it's ok to add such change to Python 2.7.

[issue25296] Simple End-of-life guide covering all unsupported versions

Carol Willing added the comment: And that would be EOL (end of life) not EOF. More coffee please... -- ___ Python tracker ___

[issue25296] Simple End-of-life guide covering all unsupported versions

Carol Willing added the comment: +1 to adding the EOF info to the Docs front page and a link from the downloads page. Also, +1 to David's suggestion to adding the devguide as well to the front page. In the future, it would be nice to add the devguide to the CPython repo instead of having it

[issue25290] csv.reader: minor docstring typo

Roundup Robot added the comment: New changeset 3940f480ea16 by Berker Peksag in branch '3.4': Issue #25290: Fix typo in csv.reader() docstring https://hg.python.org/cpython/rev/3940f480ea16 New changeset 3b565295eba0 by Berker Peksag in branch '3.5': Issue #25290: Fix typo in csv.reader()

[issue25290] csv.reader: minor docstring typo

Roundup Robot added the comment: New changeset ceff1babf66e by Berker Peksag in branch '2.7': Issue #25290: Fix typo in csv.reader() docstring https://hg.python.org/cpython/rev/ceff1babf66e -- ___ Python tracker

[issue25301] Optimize UTF-8 decoder with error handlers

New submission from STINNER Victor: The issue #24870 optimized the ASCII decoder with error handlers: New changeset 3c430259873e by Victor Stinner in branch 'default': Issue #24870: Optimize the ASCII decoder for error handlers: surrogateescape, https://hg.python.org/cpython/rev/3c430259873e

[issue25295] functools.lru_cache raises KeyError

Peter Brady added the comment: As a sanity check I removed the stored hashvalue in Raymond Hettinger's backported lru_cache (which we use to support 2.6-3.2) and end up with errors as well. So it seems like 24483 is the appropriate fix to restore the old behavior. Thanks for looking into

[issue25302] Memory Leaks with Address Sanitizer

New submission from Matt Clarkson: I have the following `main.cpp` ``` #include int main() { Py_Initialize(); if (!Py_IsInitialized()) return 1; Py_Finalize(); return 0; } ``` Compiled with on Arch Linux 4.2.1 gcc 5.2.0 python 3.4.3: ``` g++ -fsanitize=address main.cpp -o

[issue25290] csv.reader: minor docstring typo

Berker Peksag added the comment: Thanks for the patch, Johannes! I forgot to update 2.7 docs, but should be OK now. -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +berker.peksag, docs@python resolution: -> fixed stage: -> resolved status: open -> closed

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

R. David Murray added the comment: Yes, the python2 TypeErrors for mimatched arguments are sub-optimal. This has been fixed in python3: >>> parser.add_argument('--foo', help="foo", action='store_const') Traceback (most recent call last): File "", line 1, in File

[issue25299] TypeError: __init__() takes at least 4 arguments (4 given)

R. David Murray added the comment: Hmm. After looking at the code, it may also be desirable to improve that error message at the argparse level, since there's a bit of not-immediately-obvious indirection going on there. -- ___ Python tracker

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

R. David Murray added the comment: Well, since it is arguably security related, I think that pushes it toward the "yes" side. And yes, I think we could end up "breaking" third party code, as well as python (thus the need for a buildbot), but that may not be a bad thing in this case (that

[issue25295] functools.lru_cache raises KeyError

Aaron Meurer added the comment: Does this mean that some SymPy object is giving different hash values on successive calls to hash()? We definitely need to look into this on the SymPy side. -- ___ Python tracker

[issue12006] strptime should implement %G, %V and %u directives

Alexander Belopolsky added the comment: My bad. In this case, maybe Erik can review your latest patch? -- ___ Python tracker ___

[issue22080] Add windows_helper module helper

Changes by eryksun : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden versions: +Python 3.6 ___ Python tracker ___

[issue24848] Warts in UTF-7 error handling

Serhiy Storchaka added the comment: Have no ideas why tests are failed and only on this buildbot. -- ___ Python tracker ___

[issue25297] max_help_position is not works in argparse library

paul j3 added the comment: My testing shows that it's a problem with the subparsers listing. When regular arguments are long, 'max_help_position' works (within limits allowed by 'width'). -- ___ Python tracker

[issue25293] Hooking Thread/Process instantiation in concurrent.futures.

Changes by Yury Selivanov : -- nosy: +yselivanov ___ Python tracker ___ ___

[issue16802] fileno argument to socket.socket() undocumented

Guido van Rossum added the comment: Patch looks good. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue12006] strptime should implement %G, %V and %u directives

Alexander Belopolsky added the comment: > Also please let me know if this is not the proper way to respond to the code > review! I believe Rietveld gives you a "done" button on each reviewer comment. If all you do is to take the reviewer suggestion, you can just press it. Responding with an

[issue12006] strptime should implement %G, %V and %u directives

Changes by Ashley Anderson : Added file: http://bugs.python.org/file40660/issue12006_10_complete.patch ___ Python tracker ___

[issue25266] mako benchmark not working in Python 3.6

Roundup Robot added the comment: New changeset 85edb638dce6 by Brett Cannon in branch 'default': Issue #25266: the mako benchmark does not work in Python 3.6. https://hg.python.org/benchmarks/rev/85edb638dce6 -- nosy: +python-dev ___ Python tracker

[issue25266] mako benchmark not working in Python 3.6

Brett Cannon added the comment: Thanks for the patch! -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue25258] HtmlParser doesn't handle void element tags correctly

Chenyun Yang added the comment: the example you give for is a different case. , are void elements which are allowed to have no close tag; without is a browser implementation detail, most browser autocompletes . Without the parser calls the handle_endtag(), the client code which uses

[issue25266] mako benchmark not working in Python 3.6

Brett Cannon added the comment: Sorry about that. Confusion of last name with Claudiu Popa from pylint. -- ___ Python tracker ___

[issue25266] mako benchmark not working in Python 3.6

Florin Papa added the comment: It's OK. I just saw one of Claudiu Popa's issues and figured we have similar last names. -- ___ Python tracker ___

[issue25266] mako benchmark not working in Python 3.6

Florin Papa added the comment: No problem. The name is Florin Papa :) -- ___ Python tracker ___ ___

[issue25258] HtmlParser doesn't handle void element tags correctly

Chenyun Yang added the comment: Correct for previous comment, consistent -> not consistent On Fri, Oct 2, 2015 at 1:16 PM, Chenyun Yang wrote: > > Chenyun Yang added the comment: > > I am fine with either handle_startendtag or handle_starttag, > > The issue is that the

[issue25300] Enable Intel MPX (Memory protection Extensions) feature

Florin Papa added the comment: Hi David, If you are not sure about MPX hardware support, you can find out the processor model with the following commands: Linux - cat /proc/cpuinfo | grep model Mac - sysctl -n machdep.cpu.brand_string If the processor code is one of the following -

[issue25258] HtmlParser doesn't handle void element tags correctly

Ezio Melotti added the comment: Note that HTMLParser tries to follow the HTML5 specs, and for this case they say [0]: "Set the self-closing flag of the current tag token. Switch to the data state. Emit the current tag token." So it seems that for , only the (and not the closing ) should be

[issue25258] HtmlParser doesn't handle void element tags correctly

Chenyun Yang added the comment: I am fine with either handle_startendtag or handle_starttag, The issue is that the behavior is consistent for the two equally valid syntax ( and are handled differently); this inconsistent cannot be fixed from the inherited class as (handle_* calls are

[issue7897] Support parametrized tests in unittest

Changes by Alexander Belopolsky : -- versions: +Python 3.6 -Python 3.5 ___ Python tracker ___

[issue20910] Make sleep configurable in tests

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue20964] Add support.check_time_delta()

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue22323] Rewrite PyUnicode_AsWideChar() and PyUnicode_AsWideCharString(): don't cache the result

Changes by STINNER Victor : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue22324] Use PyUnicode_AsWideCharString() instead of PyUnicode_AsUnicode()

Changes by STINNER Victor : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue17548] unittest.mock: test_create_autospec_unbound_methods is skipped

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue12939] Add new io.FileIO using the native Windows API

STINNER Victor added the comment: Lack of interest, I'm not convinced that it's *really* needed. We survived 8 years with the current io module in Python 3, it's probably enough. I close the issue. -- resolution: -> out of date status: open -> closed

[issue10967] move regrtest over to using more unittest infrastructure

STINNER Victor added the comment: This issue was opened 4 years ago and has no activity since 2 years :-/ Even if yes, it would be nice to enhance regrtest and unittest, this issue doesn't propose any concrete plan with a concrete patch. I understand that the current situation is not perfect

[issue22444] Floor divide should return int

Changes by Alexander Belopolsky : -- resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue762963] timemodule.c: Python loses current timezone

Changes by Alexander Belopolsky : -- resolution: -> out of date status: open -> closed superseder: -> Time zone-capable variant of time.localtime ___ Python tracker

[issue25287] test_crypt fails on OpenBSD

Roundup Robot added the comment: New changeset 4da7edbf78d4 by Victor Stinner in branch 'default': Issue #25287: Don't add crypt.METHOD_CRYPT to crypt.methods if it's not https://hg.python.org/cpython/rev/4da7edbf78d4 -- nosy: +python-dev ___ Python

[issue19519] Parser: don't transcode input string to UTF-8 if it is already encoded to UTF-8

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue22806] regrtest: add switch -c to run only modified tests

STINNER Victor added the comment: I'm now closing this issue because Antoine, Serhiy and me dislike the idea. > An alternate suggestion would be to allow filenames like > "Lib/test/test_foo.py" as arguments to regrtest. This sounds like a better plan. Please open a new issue if you still need

[issue13466] new timezones

Alexander Belopolsky added the comment: Since nobody responded, I am closing this issue. -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue25297] max_help_position is not works in argparse library

paul j3 added the comment: There's a bug in the HelpFormatter.add_argument method. It does not take into account the extra indentation of subactions (sub parsers) when calculating self._action_max_length. The corrected method and a test case is in the attached file. class

[issue13305] datetime.strftime("%Y") not consistent for years < 1000

Alexander Belopolsky added the comment: Can someone recap the status of this issue? It is classified as a documentation bug, but I don't see a clear statement of what is wrong with the documentation. -- versions: +Python 3.6 -Python 3.3 ___ Python

  1   2   >