Mailman 3 March 2016 - Python-Dev

Adding a Pip GUI to IDLE and idlelib (GSOC project)
by Terry Reedy April 1, 2016

April 1, 2016

Summary: There are two prospective Google Summer of Code (GSOC) students applying to work on writing a gui interface to the basic pip functions needed by beginners. I expect Google to accept their proposals. Before I commit to mentoring a student (sometime in April), I would like to be sure, by addressing any objections now, that I will be able to commit the code when ready (August or before). Long version: In February 2015, Raymond Hettinger opened tracker issue "IDLE to provide menu options for using PIP" https://bugs.python.org/issue23551#msg236906 The menu options would presumably open dialog boxes defined in a new module such as idlelib.pipgui. Raymond gave a list of 9 features he thought would be useful to pip beginners. Donald Stufft (pip maintainer) answered that he already wanted someone to write a pip gui, to be put somewhere, and that he would give advice on interfacing (which he has). I answered that I had also had a vague idea of a pip gui, and thought it should be a stand-alone window invoked by a single IDLE menu item, just as turtledemo can be now. Instead of multiple dialogs (for multiple IDLE menu items), there could be, for instance, multiple tabs in a ttk.Notebook. Some pages might implement more than 1 of the features on Raymond's list. Last September, I did some proof-of-concept experiments and changed the title to "IDLE to provide menu link to PIP gui". In January, when Terri Oda requested Core Python GSOC project ideas, I suggested the pip gui project. I believe Raymond's list can easily be programmed in the time alloted. I also volunteered to help mentor. Since then, two students have submitted competent prototypes (on the tracker issue above) that show that they can write a basic tkinter app and revise in response to reviews. My current plan is to add idlelib/pipgui.py (or perhaps pip.py) to 3.5 and 3.6. The file will be structured so that it can either be run as a separate process ('python -m idlelib.pipgui' either at a console or in a subprocess call) or imported into a running process. IDLE would currently use a subprocess call, but if IDLE is restructured into a single-window, multi-tab application, it might switch to using an import. I would document the new IDLE menu entry in the current IDLE page. Separately from the pip gui project, I plan, at some point, to add a new 'idlelib' section that documents public entry points to generally useful idlelib components. If I do that before next August, I would add an entry for pipgui (which would say that details of the GUI are subject to change). Possible objections: 1. One might argue that if pipgui is written so as to not depend on IDLE, then it, like turtledemo, should be located elsewhere, possibly in Tools/scrips. I would answer that managing packages, unlike running turtle demos, *is* an IDE function. 2. One might argue that adding a new module with a public entry point, in a maintenance release, somehow abuses the license granted by PEP434, in a way that declaring a public interface in an existing module would not. If this is sustained, I could not document the new module for 3.5. Thoughts? -- Terry Jan Reedy

3 3

The next major Python version will be Python 8
by Victor Stinner April 1, 2016

April 1, 2016

Hi, Python 3 becomes more and more popular and is close to a dangerous point where it can become popular that Python 2. The PSF decided that it's time to elaborate a new secret plan to ensure that Python users suffer again with a new major release breaking all their legacy code. The PSF is happy to announce that the new Python release will be Python 8! Why the version 8? It's just to be greater than Perl 6 and PHP 7, but it's also a mnemonic for PEP 8. By the way, each minor release will now multiply the version by 2. With Python 8 released in 2016 and one release every two years, we will beat Firefox 44 in 2022 (Python 64) and Windows 2003 in 2032 (Python 2048). A major release requires a major change to justify a version bump: the new killer feature is that it's no longer possible to import a module which does not respect the PEP 8. It ensures that all your code is pure. Example: $ python8 -c 'import keyword' Lib/keyword.py:16:1: E122 continuation line missing indentation or outdented Lib/keyword.py:16:1: E265 block comment should start with '# ' Lib/keyword.py:50:1: E122 continuation line missing indentation or outdented (...) ImportError: no pep8, no glory Good news: since *no* module of the current standard library of Python 3 respect the PEP 8, the standard library will be simplified to one unique module, which is new in Python 8: pep8. The standard library will move to the Python Cheeseshop (PyPI), to reply to an old and popular request. DON'T PANIC! You are still able to import your legacy code into Python 8, you just have to rename all your modules to add a "_noqa" suffix to the filename. For example, rename utils.py to utils_noqa.py. A side effect is that you have to update all imports. For example, replace "import django" with "import django_noqa". After a study of the PSF, it's a best option to split again the Python community and make sure that all users are angry. The plan is that in 10 years, at least 50% of the 77,000 packages on the Python cheeseshop will be updated to get the "_noqa" tag. After 2020, the PSF will start to sponsor trolls to harass users of the legacy Python 3 to force them to migrate to Python 8. Python 8 is a work-in-progress (it's still an alpha version), the standard library was not removed yet. Hopefully, trying to import any module of the standard library fails. Don't hesitate to propose more ideas to make Python 8 more incompatible with Python 3! Note: The change is already effective in the default branch of Python: https://hg.python.org/cpython/rev/9aedec2dbc01 Have fun, Victor

7 6

Re: [Python-Dev] The next major Python version will be Python 8
by Chris Angelico March 31, 2016

March 31, 2016

On Fri, Apr 1, 2016 at 8:44 AM, Victor Stinner <victor.stinner(a)gmail.com> wrote: > You should now try Python 8 and try find if a module can still be imported ;-) Okay.... I can fire up interactive Python and 'import this'. But I can't run 'make'. This will be interesting! ChrisA

1 0

Scandir module seeking new maintainer
by Ben Hoyt March 29, 2016

March 29, 2016

Hi folks, I'm not sure if this is the right place to ask, but seeing I was fairly active here when developing scandir and getting it into Python 3.5, so I thought I'd start here. I'm the author and current maintainer of the scandir <https://pypi.python.org/pypi/scandir> module (Python 3.5's os.scandir but for Python 2.x and 3.x before 3.5). But I've taken on a few new non-programming projects and found I don't have time for the little improvements and fixes that are now in CPython's os.scandir and should be backported into the PyPI module. So I'm looking for someone who wants to take over the maintenance of the scandir PyPI module. It wouldn't be much work, as there are only a couple of fairly small issues to fix. Or it might be a good way to start for someone who wants to contribute to a small but useful open source module in the Python ecosystem. Any takers, or suggestions for where I could look further for a maintainer? Thanks, Ben

3 7

Summary of Python tracker Issues
by Python tracker March 25, 2016

March 25, 2016

ACTIVITY SUMMARY (2016-03-18 - 2016-03-25) Python tracker at http://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 5461 ( +2) closed 32938 (+53) total 38399 (+55) Open issues with patches: 2379 Issues opened (32) ================== #20021: "modernize" makeopcodetargets.py http://bugs.python.org/issue20021 reopened by serhiy.storchaka #26589: Add HTTP Response code 451 http://bugs.python.org/issue26589 opened by rhettinger #26591: datetime datetime.time to datetime.time comparison does nothin http://bugs.python.org/issue26591 opened by jason crockett #26597: Document how to cite Python http://bugs.python.org/issue26597 opened by steven.daprano #26600: MagickMock __str__ sometimes returns MagickMock instead of str http://bugs.python.org/issue26600 opened by Stanisław Skonieczny (Uosiu) #26601: Use new madvise()'s MADV_FREE on the private heap http://bugs.python.org/issue26601 opened by StyXman #26602: argparse doc introduction is inappropriately targeted http://bugs.python.org/issue26602 opened by Daniel Stone #26606: logging.baseConfig is missing the encoding parameter http://bugs.python.org/issue26606 opened by janis.slapins #26608: RLock undocumented behavior in case of multiple acquire http://bugs.python.org/issue26608 opened by smbrd #26609: Wrong request target in test_httpservers.py http://bugs.python.org/issue26609 opened by xiang.zhang #26610: test_venv.test_with_pip() fails when ctypes is missing http://bugs.python.org/issue26610 opened by haypo #26612: test_ssl: use context manager (with) to fix ResourceWarning http://bugs.python.org/issue26612 opened by haypo #26615: Missing entry in WRAPPER_ASSIGNMENTS in update_wrapper's doc http://bugs.python.org/issue26615 opened by xiang.zhang #26616: A bug in datetime.astimezone() method http://bugs.python.org/issue26616 opened by belopolsky #26617: Assertion failed in gc with __del__ and weakref http://bugs.python.org/issue26617 opened by guojiahua #26618: _overlapped extension module of asyncio uses deprecated WSAStr http://bugs.python.org/issue26618 opened by haypo #26619: 3.5.1 install fails on Windows Server 2008 R2 64-bit http://bugs.python.org/issue26619 opened by sdmorris #26623: JSON encode: more informative error http://bugs.python.org/issue26623 opened by Mahmoud Lababidi #26624: Windows hangs in call to CRT setlocale() http://bugs.python.org/issue26624 opened by jkloth #26626: test_dbm_gnu http://bugs.python.org/issue26626 opened by ink #26627: IDLE incorrectly labeling error as internal http://bugs.python.org/issue26627 opened by Tadhg McDonald-Jensen #26628: Undefined behavior calling C functions with ctypes.Union argum http://bugs.python.org/issue26628 opened by tilsche #26629: Need an ability to build standard DLLs with distutils http://bugs.python.org/issue26629 opened by Buraddin Ibn-Karlo #26631: Unable to install Python 3.5.1 on Windows 10 - Error 0x8007064 http://bugs.python.org/issue26631 opened by oselljr #26632: __all__ decorator http://bugs.python.org/issue26632 opened by barry #26633: multiprocessing behavior combining daemon with non-daemon chil http://bugs.python.org/issue26633 opened by josh.r #26634: recursive_repr forgets to override __qualname__ of wrapper http://bugs.python.org/issue26634 opened by xiang.zhang #26638: Avoid warnings about missing CLI options when building documen http://bugs.python.org/issue26638 opened by martin.panter #26639: Tools/i18n/pygettext.py: replace deprecated imp module with im http://bugs.python.org/issue26639 opened by haypo #26640: xmlrpc.server imports xmlrpc.client http://bugs.python.org/issue26640 opened by Valentin.Lorentz #26641: doctest doesn't support packages http://bugs.python.org/issue26641 opened by haypo #26642: Replace stdout and stderr with simple standard printers at Pyt http://bugs.python.org/issue26642 opened by haypo Most recent 15 issues with no replies (15) ========================================== #26642: Replace stdout and stderr with simple standard printers at Pyt http://bugs.python.org/issue26642 #26641: doctest doesn't support packages http://bugs.python.org/issue26641 #26639: Tools/i18n/pygettext.py: replace deprecated imp module with im http://bugs.python.org/issue26639 #26638: Avoid warnings about missing CLI options when building documen http://bugs.python.org/issue26638 #26631: Unable to install Python 3.5.1 on Windows 10 - Error 0x8007064 http://bugs.python.org/issue26631 #26629: Need an ability to build standard DLLs with distutils http://bugs.python.org/issue26629 #26626: test_dbm_gnu http://bugs.python.org/issue26626 #26618: _overlapped extension module of asyncio uses deprecated WSAStr http://bugs.python.org/issue26618 #26615: Missing entry in WRAPPER_ASSIGNMENTS in update_wrapper's doc http://bugs.python.org/issue26615 #26609: Wrong request target in test_httpservers.py http://bugs.python.org/issue26609 #26606: logging.baseConfig is missing the encoding parameter http://bugs.python.org/issue26606 #26600: MagickMock __str__ sometimes returns MagickMock instead of str http://bugs.python.org/issue26600 #26589: Add HTTP Response code 451 http://bugs.python.org/issue26589 #26584: pyclbr module needs to be more flexible on loader support http://bugs.python.org/issue26584 #26579: Support pickling slots in subclasses of common classes http://bugs.python.org/issue26579 Most recent 15 issues waiting for review (15) ============================================= #26642: Replace stdout and stderr with simple standard printers at Pyt http://bugs.python.org/issue26642 #26641: doctest doesn't support packages http://bugs.python.org/issue26641 #26639: Tools/i18n/pygettext.py: replace deprecated imp module with im http://bugs.python.org/issue26639 #26638: Avoid warnings about missing CLI options when building documen http://bugs.python.org/issue26638 #26634: recursive_repr forgets to override __qualname__ of wrapper http://bugs.python.org/issue26634 #26623: JSON encode: more informative error http://bugs.python.org/issue26623 #26616: A bug in datetime.astimezone() method http://bugs.python.org/issue26616 #26615: Missing entry in WRAPPER_ASSIGNMENTS in update_wrapper's doc http://bugs.python.org/issue26615 #26612: test_ssl: use context manager (with) to fix ResourceWarning http://bugs.python.org/issue26612 #26609: Wrong request target in test_httpservers.py http://bugs.python.org/issue26609 #26606: logging.baseConfig is missing the encoding parameter http://bugs.python.org/issue26606 #26602: argparse doc introduction is inappropriately targeted http://bugs.python.org/issue26602 #26589: Add HTTP Response code 451 http://bugs.python.org/issue26589 #26587: Possible duplicate entries in sys.path if .pth files are used http://bugs.python.org/issue26587 #26586: Simple enhancement to BaseHTTPRequestHandler http://bugs.python.org/issue26586 Top 10 most discussed issues (10) ================================= #23551: IDLE to provide menu link to PIP gui. http://bugs.python.org/issue23551 15 msgs #25654: test_multiprocessing_spawn ResourceWarning with -Werror http://bugs.python.org/issue25654 14 msgs #19829: _pyio.BufferedReader and _pyio.TextIOWrapper destructor don't http://bugs.python.org/issue19829 10 msgs #26506: hex() documentation: mention "%x" % int http://bugs.python.org/issue26506 10 msgs #26624: Windows hangs in call to CRT setlocale() http://bugs.python.org/issue26624 9 msgs #26585: Use html.escape to replace _quote_html in http.server http://bugs.python.org/issue26585 8 msgs #26632: __all__ decorator http://bugs.python.org/issue26632 8 msgs #26587: Possible duplicate entries in sys.path if .pth files are used http://bugs.python.org/issue26587 7 msgs #23735: Readline not adjusting width after resize with 6.3 http://bugs.python.org/issue23735 6 msgs #10740: sqlite3 module breaks transactions and potentially corrupts da http://bugs.python.org/issue10740 5 msgs Issues closed (52) ================== #10305: Cleanup up ResourceWarnings in multiprocessing http://bugs.python.org/issue10305 closed by haypo #10894: Making stdlib APIs private http://bugs.python.org/issue10894 closed by SilentGhost #10908: Improvements to trace._Ignore http://bugs.python.org/issue10908 closed by SilentGhost #12813: uuid4 is not tested if a uuid4 system routine isn't present http://bugs.python.org/issue12813 closed by berker.peksag #16151: Deferred KeyboardInterrupt in interactive mode http://bugs.python.org/issue16151 closed by serhiy.storchaka #17167: python man page contains $Date$ in page footer http://bugs.python.org/issue17167 closed by python-dev #18787: Misleading error from getspnam function of spwd module http://bugs.python.org/issue18787 closed by berker.peksag #19164: Update uuid.UUID TypeError exception: integer should not be an http://bugs.python.org/issue19164 closed by berker.peksag #19265: Increased test coverage for datetime pickling http://bugs.python.org/issue19265 closed by berker.peksag #21925: ResourceWarning sometimes doesn't display http://bugs.python.org/issue21925 closed by haypo #23723: Provide a way to disable bytecode staleness checks http://bugs.python.org/issue23723 closed by brett.cannon #23848: faulthandler: setup an exception handler on Windows http://bugs.python.org/issue23848 closed by haypo #23857: Make default HTTPS certificate verification setting configurab http://bugs.python.org/issue23857 closed by ncoghlan #24266: raw_input + readline: Ctrl+C during search breaks readline http://bugs.python.org/issue24266 closed by martin.panter #26076: redundant checks in tok_get in Parser\tokenizer.c http://bugs.python.org/issue26076 closed by python-dev #26095: Update porting HOWTO to special-case Python 2 code, not Python http://bugs.python.org/issue26095 closed by brett.cannon #26250: no document for sqlite3.Cursor.connection http://bugs.python.org/issue26250 closed by ezio.melotti #26252: Add an example to importlib docs on setting up an importer http://bugs.python.org/issue26252 closed by brett.cannon #26258: readline module for python 3.x on windows http://bugs.python.org/issue26258 closed by ezio.melotti #26271: freeze.py makefile uses the wrong flags variables http://bugs.python.org/issue26271 closed by brett.cannon #26281: Clear sys.path_importer_cache from importlib.invalidate_caches http://bugs.python.org/issue26281 closed by brett.cannon #26283: zipfile can not handle the path build by os.path.join() http://bugs.python.org/issue26283 closed by ezio.melotti #26396: Create json.JSONType http://bugs.python.org/issue26396 closed by brett.cannon #26525: Documentation of ord(c) easy to misread http://bugs.python.org/issue26525 closed by terry.reedy #26560: Error in assertion in wsgiref.handlers.BaseHandler.start_respo http://bugs.python.org/issue26560 closed by berker.peksag #26567: ResourceWarning: Use tracemalloc to display the traceback wher http://bugs.python.org/issue26567 closed by haypo #26574: replace_interleave can be optimized for single character byte http://bugs.python.org/issue26574 closed by haypo #26581: Double coding cookie http://bugs.python.org/issue26581 closed by serhiy.storchaka #26588: _tracemalloc: add support for multiple address spaces (domains http://bugs.python.org/issue26588 closed by haypo #26590: socket destructor: implement finalizer http://bugs.python.org/issue26590 closed by haypo #26592: _warnings.warn_explicit() should try to import the warnings mo http://bugs.python.org/issue26592 closed by haypo #26593: silly typo in logging cookbook http://bugs.python.org/issue26593 closed by berker.peksag #26594: Tutorial example IndentationError? http://bugs.python.org/issue26594 closed by SilentGhost #26595: Segfault on Pointer operation http://bugs.python.org/issue26595 closed by Emin Ghuliev #26596: numpy.all np.all .all http://bugs.python.org/issue26596 closed by eryksun #26598: Embbedable zip does not import modules in (zip)subdirectory http://bugs.python.org/issue26598 closed by zach.ware #26599: segfault at 24 error 6 in python http://bugs.python.org/issue26599 closed by SilentGhost #26603: os.scandir: implement finalizer (for ResourceWarning) http://bugs.python.org/issue26603 closed by haypo #26604: Add optional source parameter to warnings.warn() http://bugs.python.org/issue26604 closed by haypo #26605: Feature request: string method `to_file` http://bugs.python.org/issue26605 closed by SilentGhost #26607: Rename a parameter in the function PyFile_FromFile http://bugs.python.org/issue26607 closed by SilentGhost #26611: assertRaises callableObj cannot be used as a keyword with args http://bugs.python.org/issue26611 closed by SilentGhost #26613: Descriptor HowTo Guide - Typo http://bugs.python.org/issue26613 closed by rhettinger #26614: False/0 and True/1 collision when used as dict keys? http://bugs.python.org/issue26614 closed by ethan.furman #26620: Fix ResourceWarning warnings in test_urllib2_localnet http://bugs.python.org/issue26620 closed by python-dev #26621: test_decimal fails with libmpdecimal 2.4.2 http://bugs.python.org/issue26621 closed by skrah #26622: test_winreg now logs "Windows exception: code 0x06ba" on Pytho http://bugs.python.org/issue26622 closed by haypo #26625: SELECT-initiated transactions can cause "database is locked" i http://bugs.python.org/issue26625 closed by rhunter #26630: Windows EXE extension installers not finding 32bit Python 3.5 http://bugs.python.org/issue26630 closed by eryksun #26635: Python default date does not match Unix time http://bugs.python.org/issue26635 closed by haypo #26636: SystemError while running tests: extra exception raised http://bugs.python.org/issue26636 closed by haypo #26637: importlib: better error message when import fail during Python http://bugs.python.org/issue26637 closed by haypo

1 0

GSOC_2016_ROUNDUP_PROPOSAL
by Mohit Kumra March 24, 2016

March 24, 2016

I am extremely interested in working for the Roundup issue tracker's github integration part.I am proficient in python and git and have worked before also on the git. It is requested to review the proposal for the same. Thank you for the consideration.A quick reply is appreciated. Thanking You Mohit Kumra mohitkumra95(a)gmail.com 91-9718388335

1 0

Re: [Python-Dev] [Python-ideas] Add citation() to site.py
by Jim J. Jewett March 23, 2016

March 23, 2016

On Sun Mar 20 16:26:03 EDT 2016, Nikolaus Rath wrote: > Which I believe makes it completely pointless to cite Python at all. As > far as I can see, nowadays citations are given for two reasons: > 1. To give the reader a starting point to get more information on a > topic. I don't often see references to good "starting points", but I'll grant the "get more information". > 2. To formally acknowledge the work done by someone else (who ends up > with an increased number of citations for the cited publication, > which is unfortunately a crucial metric in most academic hiring and > evaluation processes). There is a third category, of reader service. When I as a reader have wanted to follow a citation, it was because I wanted to know more about the specific claim it supposedly supported. In a few cases -- and these were probably the cases most valuable to the authors -- I wanted to build on the work, or test it out under new conditions. Ideally, my first step was to replicate the original result, to ensure that anything new I found was really caused by the intentional changes. If I was looking at a computational model, I really didn't even have the excuse of "too expensive to run that many subjects." For papers more than a few years old, even if the code was available, it generally didn't run -- and often didn't even compile. Were there a few missing utility files, or had they been using a language variant different from what had eventually become the standard? Obviously, it would have been better to just get a copy of the original environment, PDP and all. In real life, it was very helpful to know which version of which compiler the authors had been using. Even the authors who had managed to save their code didn't generally remember that level of detail about the original environment. Python today has much better backwards compatibility, but ... if some junior grad student (maybe not in CS) today came across code raising strings instead of Exceptions, how confident would she be that she had the real code, as opposed to a mangled transcription? Would it help if the paper had a citation that specified CPython 2.1 and she could still download a version of that ... where it worked? -jJ -- If there are still threading problems with my replies, please email me with details, so that I can try to resolve them. -jJ

1 0

Re: [Python-Dev] cpython: hashtable.h now supports keys of any size
by Serhiy Storchaka March 23, 2016

March 23, 2016

On 21.03.16 23:01, victor.stinner wrote: > https://hg.python.org/cpython/rev/aca4e9af1ca6 > changeset: 100640:aca4e9af1ca6 > user: Victor Stinner <victor.stinner(a)gmail.com> > date: Mon Mar 21 22:00:58 2016 +0100 > summary: > hashtable.h now supports keys of any size > > Issue #26588: hashtable.h now supports keys of any size, not only > sizeof(void*). It allows to support key larger than sizeof(void*), but also to > use less memory for key smaller than sizeof(void*). If key size is compile time constant, Py_MEMCPY() and memcpy() can be optimized in one machine instruction. If it is ht->key_size, it adds more overhead. These changes can have negative performance effect. It can be eliminated if pass a compile time constant to _Py_HASHTABLE_ENTRY_READ_KEY() etc.

1 1

Counting references to Py_None
by Facundo Batista March 21, 2016

March 21, 2016

Hello! I'm seeing that our code increases the reference counting to Py_None, and I find this a little strange: isn't Py_None eternal and will never die? What's the point of counting its references? Thanks! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ Twitter: @facundobatista

6 6

PEP 484 update: allow @overload in regular module files
by Guido van Rossum March 21, 2016

March 21, 2016

Here's another proposal for a change to PEP 484. In https://github.com/python/typing/issues/72 there's a long discussion ending with a reasonable argument to allow @overload in (non-stub) modules after all. This proposal does *not* sneak in a syntax for multi-dispatch -- the @overload versions are only for the benefit of type checkers while a single non-@overload implementation must follow that handles all cases. In fact, I expect that if we ever end up adding multi-dispatch to the language or library, it will neither replace not compete with @overload, but the two will most likely be orthogonal to each other, with @overload aiming at a type checker and some other multi-dispatch aiming at the interpreter. (The needs of the two cases are just too different -- e.g. it's hard to imagine multi-dispatch in Python use type variables.) More details in the issue (that's also where I'd like to get feedback if possible). I want to settle this before 3.5.2 goes out, because it requires a change to typing.py in the stdlib. Fortunately the change will be backward compatible (even though this isn't strictly required for a provisional module). In the original typing module, any use of @overload outside a stub is an error (it raises as soon as it's used). In the new proposal, you can decorate a function with @overload, but any attempt to call such a decorated function raises an error. This should catch cases early where you forget to provide an implementation. (Reference for provisional modules: https://www.python.org/dev/peps/pep-0411/) -- --Guido van Rossum (python.org/~guido)

1 1