[issue29149] SSL.py recursion limit crash

Sumner Hearth added the comment: Attached a simpler version of the code with same error using only eventlet. -- Added file: http://bugs.python.org/file46136/crash_simple.py ___ Python tracker

[issue17301] An in-place version of many bytearray methods is needed

INADA Naoki added the comment: I prefer ".inplace_translate" to ".mtranslate", but I'm not sure about it's worth enough to add it to bytearray. In last year, I proposed adding `bytes.frombuffer()` constructor to avoid unnecessary memory copy.

[issue29149] SSL.py recursion limit crash

Sumner Hearth added the comment: Recursion crash disappears in eventlet 0.17.4 -- ___ Python tracker ___ ___

[issue28768] Warning: implicit declaration of function '_setmode'

Masayuki Yamamoto added the comment: Building 2.7 is for testing purposes. It is used to judge whether it is a problem (specifically for Cygwin-specific) originated in the old version. _setmode is an important function for setting input and output of CPython, so in Cygwin I feel annoying that

[issue29149] SSL.py recursion limit crash

New submission from Sumner Hearth: Error in python 3.6 ssl.py: [...] File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 737, in __init__ self._context.verify_mode = cert_reqs File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",

[issue29147] registry value to be cleared when python is uninstalled

Steve Dower added the comment: Interesting. I don't suppose you could find all the log files in your %TEMP% directory, put them in a zip file and attach them here? There may be some clue as to why this happened - it's certainly meant to clean everything up when you uninstall (except for

[issue16026] csv.DictReader argument names documented incorrectly

Berker Peksag added the comment: Welcome and thanks for the patch, Greg. csv.rst-patch looks good to me. I will commit it this week if there are no objections. Documentation updates can go into all active branches so I'm adding 3.5 and 3.6 back (we can pass 2.7 at this point since this is a

[issue29147] registry value to be cleared when python is uninstalled

jha.amit added the comment: The start menu shortcuts and the files in installation path "C:\Program Files\Python35" are also present. The thing should go when python3.5 is uninstalled. This can be solved when newer version of python, i.e., python 3.6 is installed/uninstalled. During this

[issue29148] Inheritance behaviour ambiguos

Xiang Zhang added the comment: It seems you are surprised `super(C, self).foo2()` works but it is actually how super() and class.__mro__ works. :-) So not a bug. You could learn more about it but sorry I don't have any good reference for you. :-( -- nosy: +xiang.zhang resolution: ->

[issue17301] An in-place version of many bytearray methods is needed

Changes by irdb : -- nosy: +irdb ___ Python tracker ___ ___ Python-bugs-list mailing

[issue29148] Inheritance behaviour ambiguos

New submission from Yugansh Marwah: Inheritance property behaves ambiguously on inheriting multiple inheritance over a class It even calls the function of un-inherited class code is attached below kindly run it and tell me the exact behavior of the same. -- components: Tests files:

[issue29134] contextlib doc bug

Senthil Kumaran added the comment: I am going to vote for "not a bug" here. From the context is it understood that the `ContextBaseClass` is to be provided by the user. > Existing context managers that already have a base class can be extended by > using ContextDecorator as a mixin class:

[issue29147] registry value to be cleared when python is uninstalled

New submission from jha.amit: I have installed python 3.5 on Windows and then uninstalled it. THe registry value HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\3.5 is still present. This is solved in python 3.6. So the work to be done here is: if there was any previous version of python

[issue29145] failing overflow checks in replace_*

Benjamin Peterson added the comment: Does that mean it no longer respects -fwrapv? -- nosy: +benjamin.peterson ___ Python tracker ___

[issue16026] csv.DictReader argument names documented incorrectly

Greg Bengeult added the comment: Here's a revised patch file for Python 3.7. This is my first ever submission to an open source project, so please be gentle. -- nosy: +gbengeult versions: -Python 2.7, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file46132/csv.rst-patch

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

Changes by R. David Murray : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue28180] sys.getfilesystemencoding() should default to utf-8

INADA Naoki added the comment: I read PEP 538 but I can't understand why just using UTF-8 when locale is C like macOS is bad idea. -- ___ Python tracker

[issue22417] PEP 476: verify HTTPS certificates by default

Carlos Alberto Lopez Perez added the comment: The python 2.7 documentation for urrlib still has a big warning notice at the top saying: """ Warning When opening HTTPS URLs, it does not attempt to validate the server certificate. Use at your own risk! """ ^^

[issue20608] 'SyntaxError: invalid token' is unfriendly

John Parejko added the comment: I had filed issue 29146 but eventually found this, which has patches to fix the exception messages. Could someone please look at this and get it incorporated into python? -- ___ Python tracker

[issue20608] 'SyntaxError: invalid token' is unfriendly

Changes by John Parejko : -- nosy: +John Parejko ___ Python tracker ___ ___

[issue29146] Confusing "invalid token" exception when integers have leading zero

Berker Peksag added the comment: Thanks for finding the duplicate. I'm closing this as a duplicate of issue 20608. -- components: -2to3 (2.x to 3.x conversion tool), Documentation nosy: +berker.peksag -docs@python resolution: -> duplicate stage: -> resolved status: open -> closed

[issue20608] 'SyntaxError: invalid token' is unfriendly

Changes by Berker Peksag : -- versions: +Python 3.7 -Python 3.5 ___ Python tracker ___

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

STINNER Victor added the comment: unitttest.patch: my attempt to write an unit test, but I was bitten by the datetime.timestamp() bug. -- Added file: http://bugs.python.org/file46131/unittest.patch ___ Python tracker

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

STINNER Victor added the comment: Oh, datetime.datetime.timestamp() also has a bug for values close to 0001-01-01 (year 1), at least in my timezone (CET). $ ./python -c 'import datetime; datetime.datetime.min.timestamp()' python: /home/haypo/prog/python/default/Modules/_datetimemodule.c:251:

[issue29133] Minor inaccuracy in shlex.shlex punctuation_chars example

Evan added the comment: Second patch looks good, thanks. Do you also want to doctest that? -- ___ Python tracker ___

[issue29140] time_hash() reads the wrong bytes to get microseconds

STINNER Victor added the comment: Note: I found this bug while working on the issue #29100. -- ___ Python tracker ___

[issue29140] time_hash() reads the wrong bytes to get microseconds

Roundup Robot added the comment: New changeset 72e48ff7b169 by Victor Stinner in branch '3.6': Issue #29140: Fix hash(datetime.time) https://hg.python.org/cpython/rev/72e48ff7b169 -- nosy: +python-dev ___ Python tracker

[issue29140] time_hash() reads the wrong bytes to get microseconds

STINNER Victor added the comment: I used attached check.patch to check if macros are misused in other functions. Hopefully, only time_hash() has bugs. I don't think that it's worth it to apply check.patch, I dislike such complex macro. -- Added file:

[issue28961] unittest.mock._Call ignores `name` parameter

STINNER Victor added the comment: The latest patch (Jiajun Huang, 2017-01-03 14:34) LGTM. -- ___ Python tracker ___

[issue29141] error in 2to3

Brett Cannon added the comment: To help you work around this you can simplify your original code such that you don't trigger the issue: dict((key, val) for key, val in docs_uploaded_at.iteritems() if len(val) == 3) and [x for x in registered if x.phone not in with_transaction_mobile]

[issue27961] remove support for platforms without "long long"

Petr Viktorin added the comment: The backwards compatibility is not as strong as it could be: previously, HAVE_LONG_LONG was defined to 1; now it's defined but empty. At least that's the case on Fedora. Found in the Python plugin for GCC: https://bugzilla.redhat.com/show_bug.cgi?id=1409009

[issue29146] Confusing "invalid token" exception when integers have leading zero

John Parejko added the comment: Ah, I finally found a related issue, and it looks like it has patches! https://bugs.python.org/issue20608 If someone could check that over and merge it, that would be wonderful! -- ___ Python tracker

[issue29146] Confusing "invalid token" exception when integers have leading zero

New submission from John Parejko: As described in PEP-3127, the "leading-zeros" formatting for octal was removed from python 3. This is a good thing(tm), but the recommendation of that PEP to improve the error message of the raised exception[1] was apparently never implemented. I just ran

[issue26228] pty.spawn hangs on FreeBSD 9.3, 10.x

Martin Panter added the comment: Behaviour change in Free BSD as I understand. Nothing changed in Python, but perhaps older versions of Free BSD behaved like Linux and raised EIO (or another errno; it is not clear). -- ___ Python tracker

[issue28961] unittest.mock._Call ignores `name` parameter

Berker Peksag added the comment: The patch looks good to me. There are some styling issues in the test code (e.g. no need to add trailing spaces after commas in some cases), but I can take care of them before committing the patch :) Thanks! -- ___

[issue29145] failing overflow checks in replace_*

New submission from jan matejek: Related to http://bugs.python.org/issue1621 and http://bugs.python.org/issue27473 GCC 6 optimizes away broken overflow checks. This leads to segfaults on test_replace_overflow, at least for strings and bytearrays. -- components: Interpreter Core

[issue29144] Implicit namespace packages in Python 3.6

Changes by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___

[issue29144] Implicit namespace packages in Python 3.6

New submission from Lumír Balhar: Hello. I've found a really strange difference between Python 3.5 and 3.6 related to namespace packages and I cannot find any note in changelogs. I've created a simple bash script which can reproduce my issue using virtual environments:

[issue29076] Py 3.6 Mac installer doesn't update "python3" shell command

Elias Zamaria added the comment: Ned, that sounds plausible. I think I started using fish after I installed Python 3.5, but before I installed Python 3.6. -- ___ Python tracker

[issue28518] execute("begin immediate") throwing OperationalError

Aviv Palivoda added the comment: Yes. If a transaction is open you will need to explicitly commit before doing vacuum. I am not sure if that was intentional or not. From quick look in the sqlite source code there are few things that cannot happen from a transaction: 1. VACUUM 2. ATTACH 3.

[issue29143] Logger should ignore propagate property for disabled handlers.

Oleg Serov added the comment: > 1. I have some random logging configuration with some logging handlers that > have "propagate = True" Read as: 1. I have some random logging configuration with some logging handlers that have "propagate = False" --

[issue29143] Logger should ignore propagate property for disabled handlers.

New submission from Oleg Serov: Looks like if I have a logger handler with propagate = False and it is disabled, the "propagate" is still in affect. I am considering this is a bug, because: 1. I have some random logging configuration with some logging handlers that have "propagate = True" 2.

[issue29133] Minor inaccuracy in shlex.shlex punctuation_chars example

Marco Buttu added the comment: Yes, you are right. Here is a patch. -- Added file: http://bugs.python.org/file46128/issue29133_2nd.patch ___ Python tracker

[issue29139] operator.concat/iconcat could only work if left operand is a sequence

Xiang Zhang added the comment: Actually this issue was discussed when import the pure Python implementation in #16694. There seems once an effort checking also the right operand but was later removed, but I couldn't understand why (though there is an explanation, but it's more about why

[issue29104] Left bracket remains in format string result when '\' preceeds it

Serhiy Storchaka added the comment: Updated patch adds a warning. -- Added file: http://bugs.python.org/file46127/fstring_backslash_2.patch ___ Python tracker

[issue29104] Left bracket remains in format string result when '\' preceeds it

STINNER Victor added the comment: > There is no issue with f'\\{10}'. There is an issue with f'\{10}'. Hum, I'm not sure that my previous comment is explicit: I suggest to raise a syntax error on f'\{10}' (or emit a warning, and raise an error in 3.7 if you insist ;-)). --

[issue29104] Left bracket remains in format string result when '\' preceeds it

Serhiy Storchaka added the comment: > f'\\N{AMPERSAND}': reading a local variable looks like a typo or a security > vulnerability, rather than a nice feature. This can look as a typo, but how would you write this if this is not a typo? f'\\N{AMPERSAND}' is legitimate syntax, and it would be

[issue29139] operator.concat/iconcat could only work if left operand is a sequence

STINNER Victor added the comment: > More like a implementation detail for me. IMHO it's a deliberate choice that the operator module behaves differently for concat() and add(). -- ___ Python tracker

[issue28180] sys.getfilesystemencoding() should default to utf-8

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

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

Claudio Freire added the comment: Nice ideas, will give them a try -- ___ Python tracker ___ ___

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

Jeroen Demeyer added the comment: If you are on POSIX, you could also use cysignals to get a traceback (simply import cysignals, which will install a handler for fatal signals like SIGSEGV). -- ___ Python tracker

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

STINNER Victor added the comment: > The crash (the one we're experiencing) still happens with 2.7.13. But at this > point it's not clear whether it's a Python bug or a Cython bug, as jdemeyer's > patch doesn't fix it. We're having a hard time getting accurate backtraces to > actually debug

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

Claudio Freire added the comment: The crash (the one we're experiencing) still happens with 2.7.13. But at this point it's not clear whether it's a Python bug or a Cython bug, as jdemeyer's patch doesn't fix it. We're having a hard time getting accurate backtraces to actually debug this

[issue28682] Bytes support in os.fwalk()

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

[issue27671] FAQ: len() is still function for good reason.

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

[issue28961] unittest.mock._Call ignores `name` parameter

Jiajun Huang added the comment: sorry about that, fixed. -- Added file: http://bugs.python.org/file46126/mock.patch ___ Python tracker ___

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

STINNER Victor added the comment: Claudio: "We're currently testing to try and reproduce the segfaults on 2.7.13, after that I'll try jdemeyer's patch and report the results." Cool! Keep us in touch ;-) -- ___ Python tracker

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

STINNER Victor added the comment: descr_ref-2.patch: patch rebased on the 2.7 branch. -- Added file: http://bugs.python.org/file46125/descr_ref-2.patch ___ Python tracker

[issue25750] tp_descr_get(self, obj, type) is called without owning a reference to "self"

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

[issue29092] Sync os.stat's doc and doc string

STINNER Victor added the comment: Ignore my comment, I was thinking to something else (recent os.scandir change on Windows). -- ___ Python tracker ___

[issue29092] Sync os.stat's doc and doc string

STINNER Victor added the comment: It's a recent change, before path type was always str. -- nosy: +haypo, serhiy.storchaka ___ Python tracker ___

[issue28969] lru_cache is not threadsafe

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

[issue29090] PySerial crash on Windows XP and Python 3.4

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed title: python34.dll crash -> PySerial crash on Windows XP and Python 3.4 ___ Python tracker

[issue29090] python34.dll crash

STINNER Victor added the comment: > OS is Windows XP SP3 Oh wow, that's old! XP is not more supported by Python, but it's no more supported by Microsoft neither. A crash can have various reasons. Usually, it's a buffer overflow or a race condition "somewhere". You should try to collect more

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

Changes by STINNER Victor : -- title: Signal Handlers reliably cause UnboundLocalErrors -> unicode_concatenate() optimization is not signal-safe (not atomic) versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.3, Python 3.4

[issue28983] Windows: Python 3.5.2 won't install on my computer

Changes by STINNER Victor : -- title: Python 3.5.2 won't install on my computer -> Windows: Python 3.5.2 won't install on my computer ___ Python tracker

[issue28768] Warning: implicit declaration of function '_setmode'

STINNER Victor added the comment: Masayuki Yamamoto: Do you consider that Python 2.7 should be fixed as well? What is your use case for compiling Python 2.7 on Windows using Cygwin? -- ___ Python tracker

[issue29142] urllib: no_proxy variable values with leading dot not properly handled

New submission from Thomas Loetzer: Hi, the fix for issue 26864 changed the behavior of urllib for no_proxy values with a leading dot to no longer match anything. This seems to be caused by always adding an additional dot between the hostname being checked and the entry. Example: no_proxy =

[issue28961] unittest.mock._Call ignores `name` parameter

STINNER Victor added the comment: Please remove "import ipdb; ipdb.set_trace() # TODO remove it" before posting patches ;-) -- nosy: +haypo ___ Python tracker

[issue29140] time_hash() reads the wrong bytes to get microseconds

Changes by STINNER Victor : -- keywords: +3.6regression ___ Python tracker ___ ___

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

Changes by STINNER Victor : -- title: datetime.fromtimestamp() does crash for very small or very big timestamp -> datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6 ___ Python tracker

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

Changes by STINNER Victor : -- keywords: +3.6regression ___ Python tracker ___ ___

[issue29100] datetime.fromtimestamp() does crash for very small or very big timestamp

STINNER Victor added the comment: Attached datetime_check_args.patch fixes the issue: move argument checks into time(), date() and datetime() constructors of the _datetime module. The patch requires the fix of the issue #29140 (time_hash bug), otherwise unit tests fail. This issue is a

[issue29141] error in 2to3

New submission from Sandeep Srinivasa: docs_uploaded_at = dict(filter(lambda (x,y):True if len(y) == 3 else False,docs_uploaded_at.iteritems())) produces docs_uploaded_at = dict([x_y for x_y in iter(docs_uploaded_at.items()) if True if len(x_y[1]) == 3 else False])

[issue29140] time_hash() reads the wrong bytes to get microseconds

New submission from STINNER Victor: When the time is folded, time_hash() uses DATE_xxx() macros, instead of TIME_xxx() macros, and so reads microseconds from the wrong bytes. Bug introduced by the implementation of the PEP 495 (Local Time Disambiguation). #define

[issue27200] make doctest in CPython has failures

Ezio Melotti added the comment: > The +SKIP option and the testsetup and teardown directives are not visible in > the output. So feel free to use them when needed :) > But as you can see in issue28860, I was asked to add it. Before going > on, I think we should have a clear policy about it.

[issue28845] Clean up known issues for AIX

Michael Felt added the comment: I request that you review issue27435 - in particular msg284557 - as I feel ctypes implementation for AIX is broken - at least as far as the supporting routines are concerned. When you know the "magic" one can call ctypes.CDLL() and it 'works'.

[issue29104] Left bracket remains in format string result when '\' preceeds it

STINNER Victor added the comment: The PEP 498 should be updated to define the expected behaviour of f'\{5}': https://www.python.org/dev/peps/pep-0498/#escape-sequences +self.assertEqual(f'\{6*7}', '\\42') +self.assertEqual(f'\\{6*7}', '\\42') +

[issue29117] dir() should include dunder attributes of the unbound method

Changes by Xiang Zhang : -- nosy: +xiang.zhang ___ Python tracker ___ ___ Python-bugs-list

[issue27435] ctypes library loading and AIX - also for 2.7.X (and later)

Michael Felt added the comment: Again, I would like to draw attention to this issue - BECAUSE - it is possible to use ctypes.CDLL() ASIS, on AIX - however, ctypes.util.find_library() always seems to fail (i.e., returns None even when a .so file exists) When the library names are hard-coded,

[issue29028] Use-After-Free in PyString_FromStringAndSize() of stringobject.c

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

[issue27867] various issues due to misuse of PySlice_GetIndicesEx

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

[issue29097] datetime.fromtimestamp(t) when 0 <= t <= 86399 fails on Python 3.6

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

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

John Hagen added the comment: I'm completely fine with closing this issue. Thanks for the help everyone. If someone else doesn't close it in a couple days, I'll do it. -- ___ Python tracker

[issue28911] Clarify the behaviour of assert_called_once_with

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

[issue29063] Fixed timemodule compile warnings.

STINNER Victor added the comment: Not checking for integer overflow is more likely to hide bugs. Handling time is an hard problem, see a recent funny (or not) story from Cloudfare with the latest leap second added at midnight the 2016-12-31:

[issue29063] Fixed timemodule compile warnings.

STINNER Victor added the comment: The warning was introduced by a recent change: changeset: 103680:a96101dd105c user:Alexander Belopolsky date:Sun Sep 11 22:55:16 2016 -0400 files: Doc/library/time.rst Misc/NEWS Modules/timemodule.c

[issue29063] Fixed timemodule compile warnings.

STINNER Victor added the comment: Downcasting to int doesn't seem good to me. gmtoff_time_t.patch uses time_t instead of an int to store gmtoff. It raises an OverflowError if the value doesn't fit into a C long (at least max is at least 2^31). I guess that the issue only impacts Windows, I

[issue29070] Integration tests for pty.spawn on Linux and all other platforms

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

[issue26228] pty.spawn hangs on FreeBSD 9.3, 10.x

STINNER Victor added the comment: > That used to be true in FBSD, but then someone fixed (?) it, and now the > master side simply returns EOF when read-from. Is it a behaviour change in a new version of Python? Or a change in FreeBSD? I don't understand. --

[issue26228] pty.spawn hangs on FreeBSD 9.3, 10.x

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

[issue29054] pty.py: pty.spawn hangs after client disconnect over nc (netcat)

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

[issue29020] email: collapse_rfc2231_value has inconsistent unquoting

Changes by STINNER Victor : -- title: collapse_rfc2231_value has inconsistent unquoting -> email: collapse_rfc2231_value has inconsistent unquoting ___ Python tracker

[issue29053] mailbox: Implement >From_ decoding on input from mbox

Changes by STINNER Victor : -- title: Implement >From_ decoding on input from mbox -> mailbox: Implement >From_ decoding on input from mbox ___ Python tracker

[issue28945] email: get_boundary (and get_filename) invokes unquote twice

Changes by STINNER Victor : -- title: get_boundary (and get_filename) invokes unquote twice -> email: get_boundary (and get_filename) invokes unquote twice ___ Python tracker

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

STINNER Victor added the comment: This issue is not a bug in Python, but a bug in the author's code. I suggest to close the issue, since enough clues have been provided to fix the author's issue. -- nosy: +haypo ___ Python tracker

[issue28845] Clean up known issues for AIX

Michael Felt added the comment: FWIW: just build python-2.7.13 using xlC - and ncurses-6.0 installed. root@x064:[/data/prj/python/python2-2.7.13] root@x064:[/data/prj/python/python2-2.7.13]./python Python 2.7.13 (default, Jan 3 2017, 11:16:59) [C] on aix5 Type "help", "copyright", "credits" or

[issue29139] operator.concat/iconcat could only work if left operand is a sequence

Xiang Zhang added the comment: > You can use operator.add() if you need to fall back to a __radd__ of the > right operand. IMHO for sequences when defining __add__, __radd__, there is no difference between addition and concatenation, just as

[issue27200] make doctest in CPython has failures

Marco Buttu added the comment: Hi Ezio, thanks for your time :) The +SKIP option and the testsetup and teardown directives are not visible in the output. The only extra code in the output is sorted(). I agree with you about the use of sorted(), and I think we do not have to add extra code

[issue29134] contextlib doc bug

Changes by SilentGhost : -- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: -> patch review type: -> behavior versions: +Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

  1   2   >