Mailman 3 November 2017 - Python-Dev

Reminder: 12 weeks to 3.7 feature code cutoff
by Ned Deily Nov. 13, 2017

Nov. 13, 2017

Happy belated Halloween to those who celebrate it; I hope it wasn't too scary! Also possibly scary: we have just a little over 12 weeks remaining until Python 3.7's feature code cutoff, 2018-01-29. Those 12 weeks include a number of traditional holidays around the world so, if you are planning on writing another PEP for 3.7 or working on getting an existing one approved or getting feature code reviewed, please plan accordingly. If you have something in the pipeline, please either let me know or, when implemented, add the feature to PEP 537, the 3.7 Release Schedule PEP. As you may recall, the release schedule calls for 4 alpha preview releases prior to the feature code cutoff with the first beta release. We have already produced the first two alphas. Reviewing the schedule recently, I realized that I had "front-loaded" the alphas, leaving a bigger gap between the final alphas and the first beta. So I have adjusted the schedule a bit, pushing alpha 3 and 4 out. The new dates are: - 3.7.0 alpha 3: 2017-11-27 (was 2017-11-13) - 3.7.0 alpha 4: 2018-01-08 (was 2017-12-18) - 3.7.0 beta 1: 2018-01-29 (feature freeze - unchanged) I hope the new dates give you a little bit more time to get your bits finished and get a little bit of exposure prior to the feature freeze. Considering how quickly and positively it has been adopted, 3.6 is going to be a tough act to follow. But we can do it again. Thank you all for your ongoing efforts! --Ned -- Ned Deily nad(a)python.org -- []

25 56

Analog of PEP 448 for dicts (unpacking in assignment with dict rhs)
by Ben Usman Nov. 12, 2017

Nov. 12, 2017

The following works now: seq = [1, 2] d = {'c': 3, 'a': 1, 'b': 2} (el1, el2) = *seq el1, el2 = *seq head, *tail = *seq seq_new = (*seq, *tail) dict_new = {**d, **{'c': 4}} def f(arg1, arg2, a, b, c): pass f(*seq, **d) It seems like dict unpacking syntax would not be fully coherent with list unpacking syntax without something like: {b, a, **other} = **d Because iterables have both syntax for function call unpacking and "rhs in assignment unpacking" and dict has only function call unpacking syntax. I was not able to find any PEPs that suggest this (search keywords: "PEP 445 dicts", "dictionary unpacking assignment", checked PEP-0), however, let me know if I am wrong. The main use-case, in my understating, is getting shortcuts to elements of a dictionary if they are going to be used more then ones later in the scope. A made-up example is using a config to initiate a bunch of things with many config arguments with long names that have overlap in keywords used in initialization. One should either write long calls like start_a(config['parameter1'], config['parameter2'], config['parameter3'], config['parameter4']) start_b(config['parameter3'], config['parameter2'], config['parameter3'], config['parameter4']) many times or use a list-comprehension solution mentioned above. It becomes even worse (in terms of readability) with nested structures. start_b(config['group2']['parameter3'], config['parameter2'], config['parameter3'], config['group2']['parameter3']) ## Rationale Right now this problem is often solved using [list] comprehensions, but this is somewhat verbose: a, b = (d[k] for k in ['a', 'b']) or direct per-instance assignment (looks simple for with single-character keys, but often becomes very verbose with real-world long key names) a = d['a'] b = d['b'] Alternatively one could have a very basic method\function get_n() or __getitem__() accepting more then a single argument a, b = d.get_n('a', 'b') a, b = get_n(d, 'a', 'b') a, b = d['a', 'b'] All these approaches require verbose double-mentioning of same key. It becomes even worse if you have nested structures of dictionaries. ## Concerns and questions: 0. This is the most troubling part, imho, other questions are more like common thoughts. It seems (to put it mildly) weird that execution flow depends on names of local variables. For example, one can not easily refactor these variable names. However, same is true for dictionary keys anyway: you can not suddenly decide and refactor your code to expect dictionaries with keys 'c' and 'd' whereas your entire system still expects you to use dictionaries with keys 'a' and 'b'. A counter-objection is that this specific scenario is usually handled with record\struct-like classes with fixed members rather then dicts, so this is not an issue. Quite a few languages (closure and javascript to name a few) seem to have this feature now and it seems like they did not suffer too much from refactoring hell. This does not mean that their approach is good, just that it is "manageable". 1. This line seems coherent with sequence syntax, but redundant: {b, a, **other} = **d and the following use of "throwaway" variable just looks poor visually {b, a, **_} = **d could it be less verbose like this {b, a} = **d but it is not very coherent with lists behavior. E.g. what if that line did not raise something like "ValueError: Too many keys to unpack, got an unexpected keyword argument 'c'". 2. Unpacking in other contexts {self.a, b, **other} = **d should it be interpreted as self.a, b = d['a'], d['b'] or self.a, b = d['self.a'], d['b'] probably the first, but what I am saying is that these name-extracting rules should be strictly specified and it might not be trivial. --- Ben

6 8

Re: [Python-Dev] Analog of PEP 448 for dicts (unpacking in assignment with dict rhs)
by Koos Zevenhoven Nov. 11, 2017

Nov. 11, 2017

Oops, forgot to reply to the list. On Nov 12, 2017 03:35, "Koos Zevenhoven" <k7hoven(a)gmail.com> wrote: On Nov 12, 2017 02:12, "Joao S. O. Bueno" <jsbueno(a)python.org.br> wrote: Ben, I have a small package which enables one to do: with MapGetter(my_dictionary): from my_dictionary import a, b, parameter3 If this interests you, contributions so it can get hardenned for mainstram acceptance are welcome. https://github.com/jsbueno/extradict Your VersionDict in fact has some similarities to what I have thought of implementing using the PEP 555 machinery, but it is also a bit different. Interesting... -- Koos (mobile) On 11 November 2017 at 04:26, Ben Usman <bigobangux(a)gmail.com> wrote: > Got it, thank you. I'll go and check it out! > > On Nov 11, 2017 01:22, "Jelle Zijlstra" <jelle.zijlstra(a)gmail.com> wrote: >> >> >> >> 2017-11-10 19:53 GMT-08:00 Ben Usman <bigobangux(a)gmail.com>: >>> >>> The following works now: >>> >>> seq = [1, 2] >>> d = {'c': 3, 'a': 1, 'b': 2} >>> >>> (el1, el2) = *seq >>> el1, el2 = *seq >>> head, *tail = *seq >>> >>> seq_new = (*seq, *tail) >>> dict_new = {**d, **{'c': 4}} >>> >>> def f(arg1, arg2, a, b, c): >>> pass >>> >>> f(*seq, **d) >>> >>> It seems like dict unpacking syntax would not be fully coherent with >>> list unpacking syntax without something like: >>> >>> {b, a, **other} = **d >>> >>> Because iterables have both syntax for function call unpacking and >>> "rhs in assignment unpacking" and dict has only function call >>> unpacking syntax. >>> >>> I was not able to find any PEPs that suggest this (search keywords: >>> "PEP 445 dicts", "dictionary unpacking assignment", checked PEP-0), >>> however, let me know if I am wrong. >>> >> It was discussed at great length on Python-ideas about a year ago. There >> is a thread called "Unpacking a dict" from May 2016. >> >>> >>> The main use-case, in my understating, is getting shortcuts to >>> elements of a dictionary if they are going to be used more then >>> ones later in the scope. A made-up example is using a config to >>> initiate a bunch of things with many config arguments with long >>> names that have overlap in keywords used in initialization. >>> >>> One should either write long calls like >>> >>> start_a(config['parameter1'], config['parameter2'], >>> config['parameter3'], config['parameter4']) >>> >>> start_b(config['parameter3'], config['parameter2'], >>> config['parameter3'], config['parameter4']) >>> >>> many times or use a list-comprehension solution mentioned above. >>> >>> It becomes even worse (in terms of readability) with nested structures. >>> >>> start_b(config['group2']['parameter3'], config['parameter2'], >>> config['parameter3'], config['group2']['parameter3']) >>> >>> >>> ## Rationale >>> >>> Right now this problem is often solved using [list] comprehensions, >>> but this is somewhat verbose: >>> >>> a, b = (d[k] for k in ['a', 'b']) >>> >>> or direct per-instance assignment (looks simple for with >>> single-character keys, but often becomes very verbose with >>> real-world long key names) >>> >>> a = d['a'] >>> b = d['b'] >>> >>> Alternatively one could have a very basic method\function >>> get_n() or __getitem__() accepting more then a single argument >>> >>> a, b = d.get_n('a', 'b') >>> a, b = get_n(d, 'a', 'b') >>> a, b = d['a', 'b'] >>> >>> All these approaches require verbose double-mentioning of same >>> key. It becomes even worse if you have nested structures >>> of dictionaries. >>> >>> ## Concerns and questions: >>> >>> 0. This is the most troubling part, imho, other questions >>> are more like common thoughts. It seems (to put it mildly) >>> weird that execution flow depends on names of local variables. >>> >>> For example, one can not easily refactor these variable names. However, >>> same is true for dictionary keys anyway: you can not suddenly decide >>> and refactor your code to expect dictionaries with keys 'c' and >>> 'd' whereas your entire system still expects you to use dictionaries >>> with keys 'a' and 'b'. A counter-objection is that this specific >>> scenario is usually handled with record\struct-like classes with >>> fixed members rather then dicts, so this is not an issue. >>> >>> Quite a few languages (closure and javascript to name a few) seem >>> to have this feature now and it seems like they did not suffer too >>> much from refactoring hell. This does not mean that their approach >>> is good, just that it is "manageable". >>> >>> 1. This line seems coherent with sequence syntax, but redundant: >>> {b, a, **other} = **d >>> >>> and the following use of "throwaway" variable just looks poor visually >>> {b, a, **_} = **d >>> >>> could it be less verbose like this >>> {b, a} = **d >>> >>> but it is not very coherent with lists behavior. >>> >>> E.g. what if that line did not raise something like "ValueError: >>> Too many keys to unpack, got an unexpected keyword argument 'c'". >>> >>> 2. Unpacking in other contexts >>> >>> {self.a, b, **other} = **d >>> >>> should it be interpreted as >>> self.a, b = d['a'], d['b'] >>> >>> or >>> >>> self.a, b = d['self.a'], d['b'] >>> >>> probably the first, but what I am saying is that these name-extracting >>> rules should be strictly specified and it might not be trivial. >>> >>> --- >>> Ben >>> >>> _______________________________________________ >>> Python-Dev mailing list >>> Python-Dev(a)python.org >>> https://mail.python.org/mailman/listinfo/python-dev >>> Unsubscribe: >>> https://mail.python.org/mailman/options/python-dev/jelle. zijlstra%40gmail.com >>> >> > > _______________________________________________ > Python-Dev mailing list > Python-Dev(a)python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/jsbueno%40python.org.br > _______________________________________________ Python-Dev mailing list Python-Dev(a)python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/k7hoven% 40gmail.com

2 1

Python 3.6.3 venv FAILURE
by Larry Chen Nov. 10, 2017

Nov. 10, 2017

Upgraded from 3.6.1 to 3.6.3; but got an error when trying to create my virtual environment. [larrchen@rslab239 Larry]$ /opt/python3.6.3/bin/python3.6 -m venv /u/larrchen/work2/SAN/Users/Larry/rslab239_myENV_363 Error: Command '['/u/larrchen/work2/SAN/Users/Larry/rslab239_myENV_363/bin/python3.6', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1. [larrchen@rslab239 Larry]$ Regards, Larry Chen

2 1

Proposal: go back to enabling DeprecationWarning by default
by Nick Coghlan Nov. 10, 2017

Nov. 10, 2017

On the 12-weeks-to-3.7-feature-freeze thread, Jose Bueno & I both mistakenly though the async/await deprecation warnings were missing from 3.6. They weren't missing, we'd just both forgotten those warnings were off by default (7 years after the change to the default settings in 2.7 & 3.2). So my proposal is simple (and not really new): let's revert back to the way things were in 2.6 and earlier, with DeprecationWarning being visible by default, and app devs having to silence it explicitly during application startup (before they start importing third party modules) if they don't want their users seeing it when running on the latest Python version (e.g. this would be suitable for open source apps that get integrated into Linux distros and use the system Python there). This will also restore the previously clear semantic and behavioural different between PendingDeprecationWarning (hidden by default) and DeprecationWarning (visible by default). As part of this though, I'd suggest amending the documentation for DeprecationWarning [1] to specifically cover how to turn it off programmatically (`warnings.simplefilter("ignore", DeprecationWarning)`), at the command line (`python -W ignore::DeprecationWarning ...`), and via the environment (`PYTHONWARNINGS=ignore::DeprecationWarning`). (Structurally, I'd probably put that at the end of the warnings listing as a short introduction to warnings management, with links out to the relevant sections of the documentation, and just use DeprecationWarning as the specific example) Cheers, Nick. [1] https://docs.python.org/3/library/exceptions.html#DeprecationWarning -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

23 61

Summary of Python tracker Issues
by Python tracker Nov. 10, 2017

Nov. 10, 2017

ACTIVITY SUMMARY (2017-11-03 - 2017-11-10) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 6247 ( -8) closed 37507 (+76) total 43754 (+68) Open issues with patches: 2404 Issues opened (44) ================== #10049: Add a "no-op" (null) context manager to contextlib https://bugs.python.org/issue10049 reopened by ncoghlan #31486: calling a _json.Encoder object raises a SystemError in case ob https://bugs.python.org/issue31486 reopened by serhiy.storchaka #31937: Add the term "dunder" to the glossary https://bugs.python.org/issue31937 opened by brett.cannon #31938: Convert selectmodule.c to Argument Clinic https://bugs.python.org/issue31938 opened by taleinat #31939: Support return annotation in signature for Argument Clinic https://bugs.python.org/issue31939 opened by haypo #31940: copystat on symlinks fails for alpine -- faulty lchmod impleme https://bugs.python.org/issue31940 opened by Anthony Sottile #31942: Document that support of start and stop parameters in the Sequ https://bugs.python.org/issue31942 opened by serhiy.storchaka #31943: Add asyncio.Handle.cancelled() method https://bugs.python.org/issue31943 opened by decaz #31946: mailbox.MH.add loses status info from other formats https://bugs.python.org/issue31946 opened by shai #31947: names=None case is not handled by EnumMeta._create_ method https://bugs.python.org/issue31947 opened by anentropic #31948: [EASY] Broken MSDN links in msilib docs https://bugs.python.org/issue31948 opened by berker.peksag #31949: Bugs in PyTraceBack_Print() https://bugs.python.org/issue31949 opened by serhiy.storchaka #31951: import curses is broken on windows https://bugs.python.org/issue31951 opened by joe m2 #31954: Don't prevent dict optimization by coupling with OrderedDict https://bugs.python.org/issue31954 opened by serhiy.storchaka #31956: Add start and stop parameters to the array.index() https://bugs.python.org/issue31956 opened by niki.spahiev #31958: UUID versions are not validated to lie in the documented range https://bugs.python.org/issue31958 opened by David MacIver #31961: subprocess._execute_child doesn't accept a single PathLike arg https://bugs.python.org/issue31961 opened by Roy Williams #31962: test_importlib double free or corruption https://bugs.python.org/issue31962 opened by DNSGeek #31964: [3.4][3.5] pyexpat: compilaton of libexpat fails with: ISO C90 https://bugs.python.org/issue31964 opened by haypo #31966: [EASY C][Windows] print('hello\n', end='', flush=True) raises https://bugs.python.org/issue31966 opened by Guillaume Aldebert #31967: [Windows] test_distutils: fatal error LNK1158: cannot run 'rc. https://bugs.python.org/issue31967 opened by haypo #31968: exec(): method's default arguments from dict-inherited globals https://bugs.python.org/issue31968 opened by Ilya Polyakovskiy #31971: idle_test: failures on x86 Windows7 3.x https://bugs.python.org/issue31971 opened by haypo #31972: Inherited docstrings for pathlib classes are confusing https://bugs.python.org/issue31972 opened by eric.araujo #31973: Incomplete DeprecationWarning for async/await keywords https://bugs.python.org/issue31973 opened by barry #31975: Add a default filter for DeprecationWarning in __main__ https://bugs.python.org/issue31975 opened by ncoghlan #31976: Segfault when closing BufferedWriter from a different thread https://bugs.python.org/issue31976 opened by benfogle #31978: make it simpler to round fractions https://bugs.python.org/issue31978 opened by wolma #31979: Simplify converting non-ASCII strings to int, float and comple https://bugs.python.org/issue31979 opened by serhiy.storchaka #31982: 8.3. collections — Container datatypes https://bugs.python.org/issue31982 opened by Sasha Kacanski #31983: Officially add Py_SETREF and Py_XSETREF https://bugs.python.org/issue31983 opened by serhiy.storchaka #31984: startswith and endswith leak implementation details https://bugs.python.org/issue31984 opened by Ronan.Lamy #31985: Deprecate openfp() in aifc, sunau and wave https://bugs.python.org/issue31985 opened by brian.curtin #31986: [2.7] test_urllib2net.test_sites_no_connection_close() randoml https://bugs.python.org/issue31986 opened by haypo #31988: Saving bytearray to binary plist file doesn't work https://bugs.python.org/issue31988 opened by serhiy.storchaka #31990: Pickling deadlocks in thread with python -m https://bugs.python.org/issue31990 opened by Werner Smidt #31991: Race condition in wait with timeout for multiprocessing.Event https://bugs.python.org/issue31991 opened by tomMoral #31993: pickle.dump allocates unnecessary temporary bytes / str https://bugs.python.org/issue31993 opened by Olivier.Grisel #31994: json encoder exception could be better https://bugs.python.org/issue31994 opened by Jason Hihn #31995: Set operations documentation error https://bugs.python.org/issue31995 opened by Alexander Mentis #31997: SSL lib does not handle trailing dot (period) in hostname or c https://bugs.python.org/issue31997 opened by samiam #32001: @lru_cache needs to be called with () https://bugs.python.org/issue32001 opened by ataraxy #32002: test_c_locale_coercion fails when the default LC_CTYPE != "C" https://bugs.python.org/issue32002 opened by erik.bray #32003: multiprocessing.Array("b", 1), multiprocessing.Array("c",1 ) https://bugs.python.org/issue32003 opened by snwokenk Most recent 15 issues with no replies (15) ========================================== #32003: multiprocessing.Array("b", 1), multiprocessing.Array("c",1 ) https://bugs.python.org/issue32003 #31995: Set operations documentation error https://bugs.python.org/issue31995 #31994: json encoder exception could be better https://bugs.python.org/issue31994 #31991: Race condition in wait with timeout for multiprocessing.Event https://bugs.python.org/issue31991 #31990: Pickling deadlocks in thread with python -m https://bugs.python.org/issue31990 #31988: Saving bytearray to binary plist file doesn't work https://bugs.python.org/issue31988 #31986: [2.7] test_urllib2net.test_sites_no_connection_close() randoml https://bugs.python.org/issue31986 #31979: Simplify converting non-ASCII strings to int, float and comple https://bugs.python.org/issue31979 #31976: Segfault when closing BufferedWriter from a different thread https://bugs.python.org/issue31976 #31973: Incomplete DeprecationWarning for async/await keywords https://bugs.python.org/issue31973 #31972: Inherited docstrings for pathlib classes are confusing https://bugs.python.org/issue31972 #31962: test_importlib double free or corruption https://bugs.python.org/issue31962 #31948: [EASY] Broken MSDN links in msilib docs https://bugs.python.org/issue31948 #31947: names=None case is not handled by EnumMeta._create_ method https://bugs.python.org/issue31947 #31946: mailbox.MH.add loses status info from other formats https://bugs.python.org/issue31946 Most recent 15 issues waiting for review (15) ============================================= #32002: test_c_locale_coercion fails when the default LC_CTYPE != "C" https://bugs.python.org/issue32002 #31997: SSL lib does not handle trailing dot (period) in hostname or c https://bugs.python.org/issue31997 #31993: pickle.dump allocates unnecessary temporary bytes / str https://bugs.python.org/issue31993 #31985: Deprecate openfp() in aifc, sunau and wave https://bugs.python.org/issue31985 #31979: Simplify converting non-ASCII strings to int, float and comple https://bugs.python.org/issue31979 #31978: make it simpler to round fractions https://bugs.python.org/issue31978 #31976: Segfault when closing BufferedWriter from a different thread https://bugs.python.org/issue31976 #31971: idle_test: failures on x86 Windows7 3.x https://bugs.python.org/issue31971 #31968: exec(): method's default arguments from dict-inherited globals https://bugs.python.org/issue31968 #31961: subprocess._execute_child doesn't accept a single PathLike arg https://bugs.python.org/issue31961 #31954: Don't prevent dict optimization by coupling with OrderedDict https://bugs.python.org/issue31954 #31949: Bugs in PyTraceBack_Print() https://bugs.python.org/issue31949 #31942: Document that support of start and stop parameters in the Sequ https://bugs.python.org/issue31942 #31940: copystat on symlinks fails for alpine -- faulty lchmod impleme https://bugs.python.org/issue31940 #31938: Convert selectmodule.c to Argument Clinic https://bugs.python.org/issue31938 Top 10 most discussed issues (10) ================================= #31993: pickle.dump allocates unnecessary temporary bytes / str https://bugs.python.org/issue31993 17 msgs #31415: Add -X option to show import time https://bugs.python.org/issue31415 15 msgs #31975: Add a default filter for DeprecationWarning in __main__ https://bugs.python.org/issue31975 13 msgs #31939: Support return annotation in signature for Argument Clinic https://bugs.python.org/issue31939 10 msgs #31978: make it simpler to round fractions https://bugs.python.org/issue31978 10 msgs #31937: Add the term "dunder" to the glossary https://bugs.python.org/issue31937 9 msgs #30952: [Windows] include Math extension in SQlite https://bugs.python.org/issue30952 7 msgs #31984: startswith and endswith leak implementation details https://bugs.python.org/issue31984 7 msgs #31966: [EASY C][Windows] print('hello\n', end='', flush=True) raises https://bugs.python.org/issue31966 6 msgs #31985: Deprecate openfp() in aifc, sunau and wave https://bugs.python.org/issue31985 6 msgs Issues closed (63) ================== #17852: Built-in module _io can lose data from buffered files at exit https://bugs.python.org/issue17852 closed by nascheme #18669: curses.chgat() moves cursor, documentation says it shouldn't https://bugs.python.org/issue18669 closed by serhiy.storchaka #20486: msilib: can't close opened database https://bugs.python.org/issue20486 closed by berker.peksag #21423: concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor shou https://bugs.python.org/issue21423 closed by pitrou #21457: NetBSD curses support improvements https://bugs.python.org/issue21457 closed by serhiy.storchaka #21790: Change blocksize in http.client to the value of resource.getpa https://bugs.python.org/issue21790 closed by berker.peksag #21862: cProfile command-line should accept "-m module_name" as an alt https://bugs.python.org/issue21862 closed by pitrou #28340: [py2] TextIOWrapper.tell extremely slow https://bugs.python.org/issue28340 closed by haypo #28564: shutil.rmtree is inefficient due to listdir() instead of scand https://bugs.python.org/issue28564 closed by serhiy.storchaka #28706: msvc9compiler does not find a vcvarsall.bat of Visual C++ for https://bugs.python.org/issue28706 closed by skrah #28907: test_pydoc fails if build is in sub-directory https://bugs.python.org/issue28907 closed by nascheme #28997: test_readline.test_nonascii fails on Android https://bugs.python.org/issue28997 closed by xdegaye #29179: Py_UNUSED is not documented https://bugs.python.org/issue29179 closed by haypo #30057: signal.signal should check tripped signals https://bugs.python.org/issue30057 closed by pitrou #31222: datetime.py implementation of .replace inconsistent with C imp https://bugs.python.org/issue31222 closed by haypo #31271: an assertion failure in io.TextIOWrapper.write https://bugs.python.org/issue31271 closed by haypo #31523: Windows build file fixes https://bugs.python.org/issue31523 closed by steve.dower #31530: Python 2.7 readahead feature of file objects is not thread saf https://bugs.python.org/issue31530 closed by serhiy.storchaka #31609: PCbuild\clean.bat fails if the path contains whitespaces https://bugs.python.org/issue31609 closed by steve.dower #31668: "fixFirefoxAnchorBug" function in doctools.js causes navigatin https://bugs.python.org/issue31668 closed by berker.peksag #31678: Incorrect C Function name for timedelta https://bugs.python.org/issue31678 closed by berker.peksag #31764: sqlite3.Cursor.close() crashes in case the Cursor object is un https://bugs.python.org/issue31764 closed by haypo #31770: crash and refleaks when calling sqlite3.Cursor.__init__() more https://bugs.python.org/issue31770 closed by haypo #31793: Allow to specialize smart quotes in documentation translations https://bugs.python.org/issue31793 closed by inada.naoki #31843: sqlite3.connect() should accept PathLike objects https://bugs.python.org/issue31843 closed by haypo #31884: [Windows] subprocess set priority on windows https://bugs.python.org/issue31884 closed by haypo #31889: difflib SequenceMatcher ratio() still have unpredictable behav https://bugs.python.org/issue31889 closed by tim.peters #31895: Native hijri calendar support https://bugs.python.org/issue31895 closed by terry.reedy #31896: In function define class inherit ctypes.structure, and using c https://bugs.python.org/issue31896 closed by berker.peksag #31910: test_socket.test_create_connection() failed with EADDRNOTAVAIL https://bugs.python.org/issue31910 closed by haypo #31921: Bring together logic for entering/leaving a frame in frameobje https://bugs.python.org/issue31921 closed by pdox #31923: Misspelled "loading" in Doc/includes/sqlite3/load_extension.py https://bugs.python.org/issue31923 closed by berker.peksag #31924: Fix test_curses on NetBSD 8 https://bugs.python.org/issue31924 closed by serhiy.storchaka #31927: Fix compiling the socket module on NetBSD 8 and other issues https://bugs.python.org/issue31927 closed by serhiy.storchaka #31932: setup.py cannot find vcversall.bat on MSWin 8.1 if installed i https://bugs.python.org/issue31932 closed by steve.dower #31933: some Blake2 parameters are encoded backwards on big-endian pla https://bugs.python.org/issue31933 closed by christian.heimes #31934: Failure to build out of source from a not clean source https://bugs.python.org/issue31934 closed by haypo #31936: "5. The import system" grammatical error https://bugs.python.org/issue31936 closed by barry #31941: ImportError: DLL Load Failure: The specified module cannot be https://bugs.python.org/issue31941 closed by r.david.murray #31944: Windows Apps and Features items only have "Uninstall" https://bugs.python.org/issue31944 closed by steve.dower #31945: Configurable blocksize in HTTP(S)Connection https://bugs.python.org/issue31945 closed by haypo #31950: Default event loop policy doc lacks precision https://bugs.python.org/issue31950 closed by pitrou #31952: Weird behavior on tupple item assignment https://bugs.python.org/issue31952 closed by ebarry #31953: Dedicated place for security announcements? https://bugs.python.org/issue31953 closed by Mariatta #31955: distutils C compiler: set_executables() incorrectly parse valu https://bugs.python.org/issue31955 closed by haypo #31957: [Windows] PCbuild error: A numeric comparison was attempted https://bugs.python.org/issue31957 closed by haypo #31959: Directory at `TemporaryDirectory().name` does not exist https://bugs.python.org/issue31959 closed by serhiy.storchaka #31960: Protection against using a Future with another loop only works https://bugs.python.org/issue31960 closed by pitrou #31963: AMD64 Debian PGO 3.x buildbot: compilation failed with an inte https://bugs.python.org/issue31963 closed by gregory.p.smith #31965: Incorrect documentation for multiprocessing.connection.{Client https://bugs.python.org/issue31965 closed by pitrou #31969: re.groups() is not checking the arguments https://bugs.python.org/issue31969 closed by serhiy.storchaka #31970: asyncio debug mode is very slow https://bugs.python.org/issue31970 closed by pitrou #31974: Cursor misbahavior with Tkinter 3.6.1/tk 8.5 Text on Mac Sierr https://bugs.python.org/issue31974 closed by ned.deily #31977: threading.Condition can not work with threading.Semaphore https://bugs.python.org/issue31977 closed by pitrou #31980: Special case log(x, 2), log(x, 10) and pow(2, x) https://bugs.python.org/issue31980 closed by serhiy.storchaka #31981: os.mkdirs does not exist on 2.7.5+ https://bugs.python.org/issue31981 closed by serhiy.storchaka #31987: Ctypes Packing Bitfields Incorrectly - GCC both Linux and Cygw https://bugs.python.org/issue31987 closed by berker.peksag #31989: setattr on a property gives a very unhelpful exception https://bugs.python.org/issue31989 closed by r.david.murray #31992: Make iteration over dict_items yield namedtuples https://bugs.python.org/issue31992 closed by r.david.murray #31996: `setuptools.setup` parameter `py_modules` is undocumented https://bugs.python.org/issue31996 closed by berker.peksag #31998: test_zipapp failed when the zlib module is not available https://bugs.python.org/issue31998 closed by serhiy.storchaka #31999: test_venv failed when the zlib module is not available https://bugs.python.org/issue31999 closed by serhiy.storchaka #32000: test_undecodable_filename in test_httpservers failed on Mac OS https://bugs.python.org/issue32000 closed by serhiy.storchaka

1 0

Add Py_SETREF and Py_XSETREF to the stable C API
by Serhiy Storchaka Nov. 10, 2017

Nov. 10, 2017

Macros Py_SETREF and Py_XSETREF were introduced in 3.6 and backported to all maintained versions ([1] and [2]). Despite their names they are private. I think that they are enough stable now and would be helpful in third-party code. Are there any objections against adding them to the stable C API? [3] [1] https://bugs.python.org/issue20440 [2] https://bugs.python.org/issue26200 [3] https://bugs.python.org/issue31983

6 12

OrderedDict(kwargs) optimization?
by Wes Turner Nov. 9, 2017

Nov. 9, 2017

On Wednesday, November 8, 2017, Guido van Rossum <guido(a)python.org> wrote: > It seems there must be at least two threads for each topic worth > discussing at all. Therefore I feel compelled to point to > https://mail.python.org/pipermail/python-dev/2017-November/150381.html, > where I state my own conclusion about dict order. > > . > > Finally: the dict type should not be endowed with other parts of the > OrderedDict API, not should other API changes to dict be considered. > Is there an opportunity to support a fast cast to OrderedDict from 3.6 dict? Can it just copy .keys() into the OrderedDict linked list?Or is there more overhead to the transition? That'd be great for preserving kwargs' order after a pop() or a del? def func(**kwargs): kwargs = OrderedDict(kwargs) arg2 = kwargs.pop('arg2') >

2 2

PEP 484: difference between tuple and ()
by Jean-Patrick Francoia Nov. 8, 2017

Nov. 8, 2017

This is my first post on this list, so please don't kill me if I ask it in the wrong place, or if the question is stupid. I asked this question on Stack Overflow already: https://stackoverflow.com/questions/47163048/python-annotations-difference-… In very short, which form is correct ? |deffunc()->Tuple[int,int] ||| || But this requires to import the typing module. Or this (doesn't crash): |deffunc()->(int,int): | || ||

2 1

Reminder: PEP 479's __future__ about to become the default behavior
by Lukasz Langa Nov. 7, 2017

Nov. 7, 2017

This is according to https://www.python.org/dev/peps/pep-0479/#transition-plan <https://www.python.org/dev/peps/pep-0479/#transition-plan> but looking at Objects/genobject.c that hasn't been implemented yet. Is this as simple as removing the `else` clause here? https://github.com/python/cpython/blob/master/Objects/genobject.c#L277-L298 <https://github.com/python/cpython/blob/master/Objects/genobject.c#L277-L298> - Ł

2 1