bar

# expected output:

foo

123456789

bar

---------------------------------------------------------------- It seems that pattern matching/substitution iterations only go haywire once the matching iteration immediately prior to it turned out not to be a match. Maybe some internal variable is not cleaned up properly in an edge(?) case triggered by the example above? ---------- components: Regular Expressions messages: 296506 nosy: William Budd, ezio.melotti, mrabarnett priority: normal severity: normal status: open title: re.sub substitution match group contains wrong value after unmatched pattern was processed versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 01:13:56 2017 From: report at bugs.python.org (Sanyam Khurana) Date: Wed, 21 Jun 2017 05:13:56 +0000 Subject: [New-bugs-announce] [issue30721] Show expected input for right shift operator usage in custom "print" error message Message-ID: <1498022036.95.0.527028755561.issue30721@psf.upfronthosting.co.za> New submission from Sanyam Khurana: While working on issue: http://bugs.python.org/issue30597 to enhance the custom error message by showing expected output in Python3 syntax when someone uses Python2 syntax, a PR was raised: https://github.com/python/cpython/pull/2009, where we just handled the case for print with soft-space and excessive white-space. In the implementation discussion, an issue was raised to handle the case with right shift operator by Nick as in here: http://bugs.python.org/issue30597#msg295484 Nick suggested here about the possible patch: https://github.com/python/cpython/pull/2009#issuecomment-307539241 ---------- messages: 296518 nosy: CuriousLearner, ncoghlan priority: normal severity: normal status: open title: Show expected input for right shift operator usage in custom "print" error message type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 04:57:43 2017 From: report at bugs.python.org (Christoph Sarnowski) Date: Wed, 21 Jun 2017 08:57:43 +0000 Subject: [New-bugs-announce] [issue30722] Tools/demo/redemo.py broken Message-ID: <1498035463.93.0.0897725262949.issue30722@psf.upfronthosting.co.za> New submission from Christoph Sarnowski: In Python 3.6, the flags in the "re" module became members of an enum.IntFlag, whereas before they were just ints. This breaks the regex demo in Tools/demo/redemo.py. To fix this, in line 86 of redemo.py, getattr(re, name) has to be replaced by getattr(re, name).value Also, the checkbox for "LOCALE" can be removed (or fixed), as re.LOCALE is invalid for str patterns. ---------- components: Regular Expressions messages: 296530 nosy: Christoph Sarnowski2, ezio.melotti, mrabarnett priority: normal severity: normal status: open title: Tools/demo/redemo.py broken type: behavior versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 09:23:10 2017 From: report at bugs.python.org (Charles Wohlganger) Date: Wed, 21 Jun 2017 13:23:10 +0000 Subject: [New-bugs-announce] [issue30723] IDLE parenmatch - left and right highlighting, independent flash-delay Message-ID: <1498051390.64.0.726208179666.issue30723@psf.upfronthosting.co.za> New submission from Charles Wohlganger: Sorry, I'm new to this, and I've done it out of order. Commit #2306 covers the following: In IDLE, parenmatch extension: Add highlighting left and right parens to styles. Make flash-delay setting independent of parens highlighting style. Currently, the flash-delay option only affects one of the two styles, but there is no good reason for it not to affect both. ---------- assignee: terry.reedy components: IDLE messages: 296554 nosy: terry.reedy, wohlganger priority: normal severity: normal status: open title: IDLE parenmatch - left and right highlighting, independent flash-delay type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 12:06:47 2017 From: report at bugs.python.org (Kit Yan Choi) Date: Wed, 21 Jun 2017 16:06:47 +0000 Subject: [New-bugs-announce] [issue30724] ZipFile.open treats directory path as empty file Message-ID: <1498061207.73.0.213493352126.issue30724@psf.upfronthosting.co.za> New submission from Kit Yan Choi: Given a zipfile with the following content: subdir/ file1.txt subdir/file2.txt >>> archive = ZipFile(file_path, "r") >>> f = archive.open("subdir/", "r") >>>f.read() b'' It is quite odd that the subdirectory can be opened as if it was an empty file. One would expect it to raise. One use case is that the archive is created using shutil.make_archive, which includes the subdirectory paths in the namelist. Upon looping ZipFile.namelist(), you end up opening a subdirectory and getting the empty content, which should have led to error and prompted the developers to filter the namelist first. ---------- messages: 296564 nosy: Kit Yan Choi priority: normal severity: normal status: open title: ZipFile.open treats directory path as empty file type: behavior versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 13:59:07 2017 From: report at bugs.python.org (Kevin Keating) Date: Wed, 21 Jun 2017 17:59:07 +0000 Subject: [New-bugs-announce] [issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files Message-ID: <1498067947.84.0.203482425844.issue30725@psf.upfronthosting.co.za> New submission from Kevin Keating: If I use the Python 64-bit 2.7.13 Windows installer and install to C:\Program Files\Python27, then the Scripts folder doesn't get created and pip doesn't get installed. If I uninstall Python and reinstall it to C:\Python27, C:\Programs\Python27, or "C:\Path with spaces\Python27", then the Scripts folder is created and pip works correctly. If I install Python 2.7.12 using https://www.python.org/ftp/python/2.7.12/python-2.7.12.amd64.msi or Python 3.6.1 using https://www.python.org/ftp/python/3.6.1/python-3.6.1-amd64.exe, then I don't experience this issue. This issue does happen if I install to C:\PROGRA~1\Python27, which is the 8.3 filename equivalent of C:\Program Files\Python27. I've seen this on a handful of Windows 10 computers so far. I haven't tried other versions of Windows or the 32-bit installers. Steps to reproduce: - Download the Python installer from https://www.python.org/ftp/python/2.7.13/python-2.7.13.amd64.msi and run it. - Select "Install for all users" and click Next. - Enter C:\Program Files\Python27 as the installation folder and click Next. - Click on "Register Extensions" and select "Entire feature will be unavailable". (I don't know if this step is required, but it's what I've been doing to test.) Click Next. - Click Yes at the UAC prompt. - Wait for installation to finish. Expected results: The "C:\Program Files\Python27\Scripts" and "C:\Program Files\Python27\Lib\site-packages\pip" folders should get created during the installation. Actual results: Neither of the folders exist. ---------- components: Installation, Windows messages: 296571 nosy: KevKeating, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 18:18:03 2017 From: report at bugs.python.org (Segev Finer) Date: Wed, 21 Jun 2017 22:18:03 +0000 Subject: [New-bugs-announce] [issue30726] [Windows] Warnings in elementtree due to new expat Message-ID: <1498083483.53.0.88013526442.issue30726@psf.upfronthosting.co.za> New submission from Segev Finer: We are getting: Warning C4005 'HAVE_MEMMOVE': macro redefinition _elementtree c:\users\segev\prj\python\cpython\modules\expat\winconfig.h 34 Warning C4267 '=': conversion from 'size_t' to 'unsigned char', possible loss of data _elementtree c:\users\segev\prj\python\cpython\modules\expat\siphash.h 316 Warning C4996 'getenv': This function or variable may be unsafe. Consider using _dupenv_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. _elementtree C:\Users\Segev\prj\python\cpython\Modules\expat\xmlparse.c 796 Warning C4005 'HAVE_MEMMOVE': macro redefinition _elementtree c:\users\segev\prj\python\cpython\modules\expat\winconfig.h 34 Warning C4005 'HAVE_MEMMOVE': macro redefinition _elementtree c:\users\segev\prj\python\cpython\modules\expat\winconfig.h 34 And in 64-bit: c:\users\segev\prj\python\cpython\modules\expat\siphash.h(201): warning C4244: 'initializing': conversion from '__int64' to 'char', possible loss of data I'm not sure how many Python versions this affects. ---------- components: Extension Modules, Windows messages: 296590 nosy: Segev Finer, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: [Windows] Warnings in elementtree due to new expat versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 18:20:05 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 21 Jun 2017 22:20:05 +0000 Subject: [New-bugs-announce] [issue30727] [2.7] test_threading.ConditionTests.test_notify() hangs randomly on FreeBSD on Python 2.7 Message-ID: <1498083605.56.0.378803721046.issue30727@psf.upfronthosting.co.za> New submission from STINNER Victor: Example where the test hangs after at the 48th run: ---- [haypo at freebsd ~/prog/python/2.7]$ ./python -m test -F -m test.test_threading.ConditionTests.test_notify -v test_threading (...) 0:00:10 [ 47] test_threading test_notify (test.test_threading.ConditionTests) ... ok (...) 0:00:10 [ 48] test_threading test_notify (test.test_threading.ConditionTests) ... ---- It looks like a timing issue / race condition since the likehood of the bug seems to depend on the system load. Traceback using my watchdog: https://github.com/python/cpython/pull/2317 --- 0:00:57 [285] test_threading test_notify (test.test_threading.ConditionTests) ... *** STACKTRACE - START *** # ThreadID: 34391913984 File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 37, in task f() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 360, in f cond.wait() File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 340, in wait waiter.acquire() # ThreadID: 34392086528 File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 37, in task f() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 360, in f cond.wait() File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 340, in wait waiter.acquire() # ThreadID: 34384994304 File: "/usr/home/haypo/prog/python/2.7/Lib/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File: "/usr/home/haypo/prog/python/2.7/Lib/runpy.py", line 72, in _run_code exec code in run_globals File: "/usr/home/haypo/prog/python/2.7/Lib/test/__main__.py", line 3, in regrtest.main_in_temp_cwd() File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 2030, in main_in_temp_cwd main() File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 812, in main result = local_runtest() File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 798, in local_runtest testdir=testdir) File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 1007, in runtest return runtest_inner(test, verbose, quiet, huntrleaks, pgo, testdir) File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 1196, in runtest_inner indirect_test() File: "/usr/home/haypo/prog/python/2.7/Lib/test/test_threading.py", line 929, in test_main ThreadingExceptionTests, File: "/usr/home/haypo/prog/python/2.7/Lib/test/support/__init__.py", line 1571, in run_unittest _run_suite(suite) File: "/usr/home/haypo/prog/python/2.7/Lib/test/support/__init__.py", line 1530, in _run_suite result = runner.run(suite) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/runner.py", line 151, in run test(result) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/suite.py", line 70, in __call__ return self.run(*args, **kwds) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/suite.py", line 108, in run test(result) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/suite.py", line 70, in __call__ return self.run(*args, **kwds) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/suite.py", line 108, in run test(result) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/case.py", line 393, in __call__ return self.run(*args, **kwds) File: "/usr/home/haypo/prog/python/2.7/Lib/unittest/case.py", line 329, in run testMethod() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 401, in test_notify self._check_notify(cond) File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 384, in _check_notify _wait() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 16, in _wait time.sleep(0.01) # ThreadID: 34384996864 File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 774, in __bootstrap self.__bootstrap_inner() File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 801, in __bootstrap_inner self.run() File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 1971, in run self.dump_threads() File: "/usr/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 1997, in dump_threads self.dump_thread(stack) # ThreadID: 34392083968 File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 37, in task f() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 360, in f cond.wait() File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 340, in wait waiter.acquire() # ThreadID: 34392080128 File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 37, in task f() File: "/usr/home/haypo/prog/python/2.7/Lib/test/lock_tests.py", line 360, in f cond.wait() File: "/usr/home/haypo/prog/python/2.7/Lib/threading.py", line 340, in wait waiter.acquire() *** STACKTRACE - END *** --- ---------- components: Tests messages: 296591 nosy: haypo priority: normal severity: normal status: open title: [2.7] test_threading.ConditionTests.test_notify() hangs randomly on FreeBSD on Python 2.7 versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 21 19:36:55 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Wed, 21 Jun 2017 23:36:55 +0000 Subject: [New-bugs-announce] [issue30728] IDLE: Modernize configdialog code. Message-ID: <1498088215.04.0.812004436002.issue30728@psf.upfronthosting.co.za> New submission from Terry J. Reedy: Depending on the file, modernizing includes: * Add docstrings. * Change non-class names with caps to PEP8 no-caps names; this often means, for example, changing embedded 'A' to '_a'. * Make most comments be sentences, like this sentence. * Review and possibly change overly cryptic existing PEP8 names. * Switch to ttk widgets and revise imports; 'from tkinter import *' becomes 'from tkinter(.ttk) import item1, item2, ...'; use (...\n...) for multiple lines. * Split a toplevel class into a window class and a frame class. * Use modern code idioms and features up to current maintenance version. * Add tests, which are essential for checking correctness of above. For a large file like configdialog.py, I would like a separate PR or even issue for each item above. Of necessity, name changes must be done in test_configdialog.py, and it should be included in most patches for this issue. For some files, other consumers will also need patching. I don't think that modules other than test_configdialog access much of anything beside ConfigDialog, which name we are not presently changing. Cheryl's original patch for this issue combined conversion to pep8 names, revision of pep8 names (including existing #28523 'colour' to 'color'), and tkk and import conversion (and an unrelated typo correction in another file). Louie suggested adding comment revisions. At this point, I decided that this would be too much for one patch and that I would prefer more numerous patches that would be easier to review and test. (Louie's comments should be the basis for a separate PR.) Issue 28523 can be made a dependency of this issue and expanded to other name revisions. The order of changes is somewhat arbitrary, except that docstrings and comments do not need tests, and can be helpful for writing tests. Tests of some type are otherwise needed for the other steps. This presents a problem when code changes are needed to write tests. What is true is that each patch needs to apply to the current file, and once applied, should be backported immediately. (Out of order backports can 'work' but produce a wrong result. This happened already.) The problem of multiple patches to the same file possibly breaking each other includes exist patches on the tracker. When we changed textview, there were no outstanding patches that I know of. For help_about, there is an existing patch, but I did not want to apply it completely as is. Pieces of it will have to be adapted as needed. For config_key, there are at least 2 patches that may be ready-to-go or close to it. So I want to test those before writing additional patches to modernize config_key. I will review current config-dialog issues to see which have patches and which might be quick to apply. ---------- messages: 296603 nosy: csabella, louielu, terry.reedy priority: normal severity: normal stage: test needed status: open title: IDLE: Modernize configdialog code. type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 01:38:50 2017 From: report at bugs.python.org (Hang Liao) Date: Thu, 22 Jun 2017 05:38:50 +0000 Subject: [New-bugs-announce] [issue30729] Swap doesn't work in some circumstances Message-ID: <1498109930.97.0.653863984763.issue30729@psf.upfronthosting.co.za> New submission from Hang Liao: Suppose I have two lists L1 = [1,3,2,4], L2 = [1,3,2,4] L1[1], L1[2] = L1[2], L1[1] This gives me L1 = [1,2,3,4] However, if I write L2[1], L2[L2[1] - 1] = L2[L2[1] - 1], L2[1] This gives me back the same L2 = [1,3,2,4] I am not sure if this is a mistake ... If it is what it intended to do please tell me. ---------- components: macOS messages: 296614 nosy: Ikaros, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: Swap doesn't work in some circumstances type: behavior versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 04:07:00 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 22 Jun 2017 08:07:00 +0000 Subject: [New-bugs-announce] [issue30730] Injecting environment variable in subprocess on Windows Message-ID: <1498118820.13.0.596038385019.issue30730@psf.upfronthosting.co.za> New submission from Serhiy Storchaka: It is possible to inject an environment variable in subprocess on Windows if a user data is passed to a subprocess via environment variable. Provided PR fixes this vulnerability. It also adds other checks for invalid environment (variable names containing '=') and command arguments (containing '\0'). This was a part of issue13617, but extracted to a separate issue due to increased severity. ---------- components: Extension Modules messages: 296618 nosy: paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware priority: normal severity: normal stage: patch review status: open title: Injecting environment variable in subprocess on Windows type: security versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 05:33:42 2017 From: report at bugs.python.org (tumagonx) Date: Thu, 22 Jun 2017 09:33:42 +0000 Subject: [New-bugs-announce] [issue30731] Use correct executable manifest for windows Message-ID: <1498124022.5.0.932969179032.issue30731@psf.upfronthosting.co.za> New submission from tumagonx: I think there is typo in python default manifest (applies to exe dll and pyd) in official installation. currently written as: ... should be: ... notice the lowercase "i" in incorrect manifest ---------- messages: 296619 nosy: tumagonx priority: normal severity: normal status: open title: Use correct executable manifest for windows type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 05:38:57 2017 From: report at bugs.python.org (Krzysztof Nazarewski) Date: Thu, 22 Jun 2017 09:38:57 +0000 Subject: [New-bugs-announce] [issue30732] json.dumps() lack of information about RecursionError when using default function Message-ID: <1498124337.07.0.93184881583.issue30732@psf.upfronthosting.co.za> New submission from Krzysztof Nazarewski: RecursionErrors related to json.dumps' default argument give no information whatsoever about the underlying issue. Example: $ /usr/bin/python3 -c "import json;from decimal import Decimal;json.dumps(Decimal(),default=lambda v:round(v, 8))" Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3.6/json/__init__.py", line 238, in dumps **kw).encode(obj) File "/usr/lib/python3.6/json/encoder.py", line 199, in encode chunks = self.iterencode(o, _one_shot=True) File "/usr/lib/python3.6/json/encoder.py", line 257, in iterencode return _iterencode(o, 0) File "", line 1, in File "/usr/lib/python3.6/_pydecimal.py", line 1919, in __round__ return self.quantize(exp) File "/usr/lib/python3.6/_pydecimal.py", line 2603, in quantize return ans._fix(context) File "/usr/lib/python3.6/_pydecimal.py", line 1720, in _fix if not self: File "/usr/lib/python3.6/_pydecimal.py", line 852, in __bool__ return self._is_special or self._int != '0' RecursionError: maximum recursion depth exceeded in comparison Details: I have encountered issue when porting my code from Python 2 to 3. Traceback shows depth of 6, but says recursion was already reached. My first idea was that recursion counter was messed up, but it was not the case. Recursion limit was indeed reached because round() in Python 3 is returning Decimal and then applies default infinitely. The part of recursing code was inside C so it was not displayed in the traceback. Summing up it took me over 2 hours to determine what was wrong with the code. Fix ideas: - do not call default more than once on the same root object (might be problematic to implement) - raise an error if new object is equal to the previous (partially resolving issue since custom objects might not implement equality operator) - add a flag to raise an error when new object's class is equal to the previous (might give false positives hence the flag) ---------- components: Library (Lib) messages: 296620 nosy: Krzysztof Nazarewski priority: normal severity: normal status: open title: json.dumps() lack of information about RecursionError when using default function type: enhancement versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 08:34:09 2017 From: report at bugs.python.org (Jonathon Vandezande) Date: Thu, 22 Jun 2017 12:34:09 +0000 Subject: [New-bugs-announce] [issue30733] Typo in Document What's New: Calendar Message-ID: <1498134849.55.0.432143845642.issue30733@psf.upfronthosting.co.za> New submission from Jonathon Vandezande: Says: The HTMLCalendar has added new class attribute which ease the customisation the CSS classes in the produced HTML calendar. (Contributed by Oz Tiram in bpo-30095.) Should say: The HTMLCalendar has added new class attributes which ease the customisation of the CSS classes in the produced HTML calendar. (Contributed by Oz Tiram in bpo-30095.) Summary of changes: 'attribute' should be plural Missing an 'of' in front of 'the CSS classes', could also substitute 'of' for 'the' ---------- assignee: docs at python components: Documentation messages: 296625 nosy: Jonathon Vandezande, docs at python priority: normal severity: normal status: open title: Typo in Document What's New: Calendar type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 08:43:13 2017 From: report at bugs.python.org (George Shuklin) Date: Thu, 22 Jun 2017 12:43:13 +0000 Subject: [New-bugs-announce] [issue30734] 200000 indexes crashes eval and python (without eval) Message-ID: <1498135393.79.0.831850849211.issue30734@psf.upfronthosting.co.za> New submission from George Shuklin: If there is too many indexes python crashes: a[0][0][0][0].... segfault at 7ffd25fe6ff8 ip 0000564528c8cfe6 sp 00007ffd25fe7000 error 6 in python2.7[564528b6a000+324000] code to generate code: >>> i="[0]"*200000 >>> file('/tmp/bad_python.py','w').write('a=[]\na.append(a)\nprint(type(a'+i+'))\n') python2 /tmp/bad_python.py Segmentation fault (core dumped) python3 /tmp/bad_python.py RecursionError: maximum recursion depth exceeded during compilation Just in case I upload generated code. This bug affects both eval() function and python interpreter. ---------- components: Interpreter Core files: bad_python.py.gz messages: 296626 nosy: george-shuklin priority: normal severity: normal status: open title: 200000 indexes crashes eval and python (without eval) type: crash versions: Python 2.7 Added file: http://bugs.python.org/file46968/bad_python.py.gz _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 09:45:02 2017 From: report at bugs.python.org (Peter) Date: Thu, 22 Jun 2017 13:45:02 +0000 Subject: [New-bugs-announce] [issue30735] Python 3.6.1 test_asyncio fails on Solaris 11 Message-ID: <1498139102.26.0.319354129691.issue30735@psf.upfronthosting.co.za> New submission from Peter: I was building all the latest Python (2.7.13, 3.4.6, 3.5.3 and 3.6.1) on Solaris 11 using gcc 4.9.2 and found that Python 3.6.1 test_asyncio consistently fails while the other versions don't. Details: $ ./python -W default -bb -E -W error::BytesWarning -m test -r -w -j 0 test_asyncio Using random seed 44984 Run tests in parallel using 10 child processes 0:00:28 [1/1/1] test_asyncio failed Executing took 0.178 seconds test test_asyncio failed -- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/unittest/mock.py", line 1179, in patched return func(*args, **keywargs) File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_base_events.py", line 1232, in test_create_connection_service_name t, p = self.loop.run_until_complete(coro) File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 732, in create_connection infos = f1.result() File "/usr/local/src/Python-3.6.1/Lib/concurrent/futures/thread.py", line 55, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/src/Python-3.6.1/Lib/socket.py", line 743, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno 9] service name not available for the specified socket type 1 test failed: test_asyncio Re-running failed tests in verbose mode Re-running test 'test_asyncio' in verbose mode ... snipped ... ====================================================================== ERROR: test_create_connection_service_name (test.test_asyncio.test_base_events.BaseEventLoopWithSelectorTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/unittest/mock.py", line 1179, in patched return func(*args, **keywargs) File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_base_events.py", line 1232, in test_create_connection_service_name t, p = self.loop.run_until_complete(coro) File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 732, in create_connection infos = f1.result() File "/usr/local/src/Python-3.6.1/Lib/concurrent/futures/thread.py", line 55, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/src/Python-3.6.1/Lib/socket.py", line 743, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno 9] service name not available for the specified socket type ====================================================================== ERROR: test_server_close (test.test_asyncio.test_events.PollEventLoopTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_events.py", line 1340, in test_server_close ConnectionRefusedError, client.connect, ('127.0.0.1', port)) File "/usr/local/src/Python-3.6.1/Lib/unittest/case.py", line 728, in assertRaises return context.handle('assertRaises', args, kwargs) File "/usr/local/src/Python-3.6.1/Lib/unittest/case.py", line 177, in handle callable_obj(*args, **kwargs) TimeoutError: [Errno 145] Connection timed out ====================================================================== ERROR: test_sock_client_fail (test.test_asyncio.test_events.PollEventLoopTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_events.py", line 471, in test_sock_client_fail self.loop.sock_connect(sock, address)) File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/src/Python-3.6.1/Lib/asyncio/selector_events.py", line 451, in sock_connect return (yield from fut) File "/usr/local/src/Python-3.6.1/Lib/asyncio/selector_events.py", line 481, in _sock_connect_cb raise OSError(err, 'Connect call failed %s' % (address,)) TimeoutError: [Errno 145] Connect call failed ('127.0.0.1', 56937) ====================================================================== ERROR: test_server_close (test.test_asyncio.test_events.SelectEventLoopTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_events.py", line 1340, in test_server_close ConnectionRefusedError, client.connect, ('127.0.0.1', port)) File "/usr/local/src/Python-3.6.1/Lib/unittest/case.py", line 728, in assertRaises return context.handle('assertRaises', args, kwargs) File "/usr/local/src/Python-3.6.1/Lib/unittest/case.py", line 177, in handle callable_obj(*args, **kwargs) TimeoutError: [Errno 145] Connection timed out ====================================================================== ERROR: test_sock_client_fail (test.test_asyncio.test_events.SelectEventLoopTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/src/Python-3.6.1/Lib/test/test_asyncio/test_events.py", line 471, in test_sock_client_fail self.loop.sock_connect(sock, address)) File "/usr/local/src/Python-3.6.1/Lib/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/src/Python-3.6.1/Lib/asyncio/selector_events.py", line 451, in sock_connect return (yield from fut) File "/usr/local/src/Python-3.6.1/Lib/asyncio/selector_events.py", line 481, in _sock_connect_cb raise OSError(err, 'Connect call failed %s' % (address,)) TimeoutError: [Errno 145] Connect call failed ('127.0.0.1', 43072) ---------------------------------------------------------------------- Ran 1402 tests in 785.313s FAILED (errors=5, skipped=4) test test_asyncio failed 1 test failed again: test_asyncio Total duration: 13 min 34 sec Tests result: FAILURE $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/sparc-sun-solaris2.11/4.9.2/lto-wrapper Target: sparc-sun-solaris2.11 Configured with: ../gcc-4.9.2/configure --prefix=/usr/local --enable-languages=c,c++ --disable-nls --with-gnu-as --with-gnu-ld --target=sparc-sun-solaris2.11 Thread model: posix gcc version 4.9.2 (GCC) ---------- components: asyncio messages: 296629 nosy: petriborg, yselivanov priority: normal severity: normal status: open title: Python 3.6.1 test_asyncio fails on Solaris 11 versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 09:46:00 2017 From: report at bugs.python.org (Steven D'Aprano) Date: Thu, 22 Jun 2017 13:46:00 +0000 Subject: [New-bugs-announce] [issue30736] Support Unicode 10.0 Message-ID: <1498139160.83.0.103732716798.issue30736@psf.upfronthosting.co.za> New submission from Steven D'Aprano: Unicode 10.0 is now finalized: http://blog.unicode.org/2017/06/announcing-unicode-standard-version-100.html It would be good if Python 3.7 would support it. (I think that Python currently supports Unicode 8?) ---------- messages: 296630 nosy: steven.daprano priority: normal severity: normal status: open title: Support Unicode 10.0 type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 13:05:47 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Thu, 22 Jun 2017 17:05:47 +0000 Subject: [New-bugs-announce] [issue30737] Update devguide link to the new URL Message-ID: <1498151147.34.0.638989883605.issue30737@psf.upfronthosting.co.za> New submission from Mariatta Wijaya: The Devguide has a new URL: https://devguide.python.org I believe there are a few references to the devguide from CPython documentation. Those links should be updated to the new url. ---------- assignee: Mariatta components: Documentation messages: 296644 nosy: Mariatta priority: normal severity: normal stage: needs patch status: open title: Update devguide link to the new URL versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 22 13:19:12 2017 From: report at bugs.python.org (Hiba) Date: Thu, 22 Jun 2017 17:19:12 +0000 Subject: [New-bugs-announce] [issue30738] __next__() method in iterators 9.9 Message-ID: <1498151952.1.0.340362281065.issue30738@psf.upfronthosting.co.za> New submission from Hiba: class Reverse: """Iterator for looping over a sequence backwards.""" def __init__(self, data): self.data = data self.index = len(data) def __iter__(self): return self def next(self): if self.index == 0: raise StopIteration self.index = self.index - 1 return self.data[self.index] ********************************************* The next() method in the above code snippet(from 9.9 Iterators section in Tutorial is not correctly overridden. It's missing the underscores. ---------- assignee: docs at python components: Documentation messages: 296646 nosy: docs at python, hiba priority: normal severity: normal status: open title: __next__() method in iterators 9.9 versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 23 09:07:06 2017 From: report at bugs.python.org (Luc Zimmermann) Date: Fri, 23 Jun 2017 13:07:06 +0000 Subject: [New-bugs-announce] [issue30739] pypi ssl errors [CERTIFICATE_VERIFY_FAILED] Message-ID: <1498223226.69.0.666030277766.issue30739@psf.upfronthosting.co.za> New submission from Luc Zimmermann: Hi Guys, I've a strange behavior. We use python for configure our new boxes with openWRT and coovaChilli. But since yesterday, when i ask to pip to dowload PyJWT, json-cfg and speedtest-cli, some boxes can download these packages, and some can't. root at OpenWrt:~# cat /root/.pip/pip.log ------------------------------------------------------------ /usr/bin/pip run on Thu Apr 13 18:46:19 2017 Downloading/unpacking PyJWT Getting page https://pypi.python.org/simple/PyJWT/ Could not fetch URL https://pypi.python.org/simple/PyJWT/: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] unknown error (_ssl.c) Will skip URL https://pypi.python.org/simple/PyJWT/ when looking for download links for PyJWT Getting page https://pypi.python.org/simple/ Could not fetch URL https://pypi.python.org/simple/: connection error: HTTPSConnectionPool(host='pypi.python.org', port=443): Max r) Will skip URL https://pypi.python.org/simple/ when looking for download links for PyJWT Cannot fetch index base URL https://pypi.python.org/simple/ URLs to search for versions for PyJWT: * https://pypi.python.org/simple/PyJWT/ Getting page https://pypi.python.org/simple/PyJWT/ Could not fetch URL https://pypi.python.org/simple/PyJWT/: connection error: [SSL: CERTIFICATE_VERIFY_FAILED] unknown error (_ssl.c) Will skip URL https://pypi.python.org/simple/PyJWT/ when looking for download links for PyJWT Could not find any downloads that satisfy the requirement PyJWT Cleaning up... Removing temporary dir /tmp/pip_build_root... No distributions at all found for PyJWT Exception information: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/usr/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/commands/install.py", line 278, in run requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle) File "/usr/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/req.py", line 1177, in prepare_files url = finder.find_requirement(req_to_install, upgrade=self.upgrade) File "/usr/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/index.py", line 277, in find_requirement raise DistributionNotFound('No distributions at all found for %s' % req) DistributionNotFound: No distributions at all found for PyJWT ---------- messages: 296708 nosy: Luc Zimmermann priority: normal severity: normal status: open title: pypi ssl errors [CERTIFICATE_VERIFY_FAILED] type: resource usage versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 23 10:08:45 2017 From: report at bugs.python.org (Mark Haase) Date: Fri, 23 Jun 2017 14:08:45 +0000 Subject: [New-bugs-announce] [issue30740] SSLError when cancelling an SSL connection Message-ID: <1498226925.91.0.0585632472873.issue30740@psf.upfronthosting.co.za> New submission from Mark Haase: If a task is cancelled while it waiting for SSL negotiation, then an SSLError is raised, but there is no way (as far as I can tell) for the caller to catch it. (The example below is pretty contrived, but in an application I'm working on, the user can cancel downloads at any time.) Here's an example: import asyncio, random, ssl async def download(host): ssl_context = ssl.create_default_context() reader, writer = await asyncio.open_connection(host, 443, ssl=ssl_context) request = f'HEAD / HTTP/1.1\r\nHost: {host}\r\n\r\n' writer.write(request.encode('ascii')) lines = list() while True: newdata = await reader.readline() if newdata == b'\r\n': break else: lines.append(newdata.decode('utf8').rstrip('\r\n')) return lines[0] async def main(): while True: task = asyncio.Task(download('www.python.org')) await asyncio.sleep(random.uniform(0.0, 0.5)) task.cancel() try: response = await task print(response) except asyncio.CancelledError: print('request cancelled!') except ssl.SSLError: print('caught SSL error') await asyncio.sleep(1) loop = asyncio.get_event_loop() loop.run_until_complete(main()) loop.close() Running this script yields the following output: HTTP/1.1 200 OK request cancelled! HTTP/1.1 200 OK HTTP/1.1 200 OK : SSL handshake failed Traceback (most recent call last): File "/usr/lib/python3.6/asyncio/base_events.py", line 803, in _create_connection_transport yield from waiter File "/usr/lib/python3.6/asyncio/tasks.py", line 304, in _wakeup future.result() concurrent.futures._base.CancelledError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/asyncio/sslproto.py", line 577, in _on_handshake_complete raise handshake_exc File "/usr/lib/python3.6/asyncio/sslproto.py", line 638, in _process_write_backlog ssldata = self._sslpipe.shutdown(self._finalize) File "/usr/lib/python3.6/asyncio/sslproto.py", line 155, in shutdown ssldata, appdata = self.feed_ssldata(b'') File "/usr/lib/python3.6/asyncio/sslproto.py", line 219, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.6/ssl.py", line 692, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL] shutdown while in init (_ssl.c:2299) I posted this on async-sig, and Nathaniel replied: > SSLObject.unwrap has the contract that if it finishes successfully, then the SSL connection has been cleanly shut down and both sides remain in sync, and can continue to use the socket in unencrypted mode. When asyncio calls unwrap before the handshake has completed, then this contract is impossible to fulfill, and raising an error is the right thing to do. So imo the ssl module is correct here, and this is a (minor) bug in asyncio. The unwrap() call that throws is already wrapped in `try ... except SSLError` but the exception handler checks for specific SSL error codes and re-throws this particular SSL error. except (ssl.SSLError, ssl.CertificateError) as exc: if getattr(exc, 'errno', None) not in ( ssl.SSL_ERROR_WANT_READ, ssl.SSL_ERROR_WANT_WRITE, ssl.SSL_ERROR_SYSCALL): if self._state == _DO_HANDSHAKE and self._handshake_cb: self._handshake_cb(exc) raise self._need_ssldata = (exc.errno == ssl.SSL_ERROR_WANT_READ) I think this could be fixed checking for SSL_R_SHUTDOWN_WHILE_IN_INIT in this exception handler, but that constant doesn't exist in _ssl.c. As an alternative, maybe a new state _ABORT_HANDSHAKE could be introduced (the existing states are _DO_HANDSHAKE, _WRAPPED, _SHUTDOWN, and _UNWRAP). I'm happy to try my hand at either one of these approaches if somebody can point me in the right direction. ---------- components: asyncio messages: 296720 nosy: mehaase, yselivanov priority: normal severity: normal status: open title: SSLError when cancelling an SSL connection versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 23 10:24:00 2017 From: report at bugs.python.org (Luc Zimmermann) Date: Fri, 23 Jun 2017 14:24:00 +0000 Subject: [New-bugs-announce] [issue30741] https://www.pypi-mirrors.org/ error 503 Message-ID: <1498227840.1.0.346905721798.issue30741@psf.upfronthosting.co.za> New submission from Luc Zimmermann: is that linked with the certificate error on pypi ? you redirect http request to https, but you still listen 80 and not 443 ? ---------- messages: 296721 nosy: Luc Zimmermann priority: normal severity: normal status: open title: https://www.pypi-mirrors.org/ error 503 type: security _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 23 17:27:58 2017 From: report at bugs.python.org (=?utf-8?b?RMW+ZW5hbiBadWtpxIc=?=) Date: Fri, 23 Jun 2017 21:27:58 +0000 Subject: [New-bugs-announce] [issue30742] VS2015 support for 2.7 branch Message-ID: <1498253278.08.0.871118250294.issue30742@psf.upfronthosting.co.za> New submission from D?enan Zuki?: In VS2015 timezone and friends have been replace by _timezone (related issue24643). The second problem is missing _PyVerify_fd during linking phase. ---------- components: Library (Lib) messages: 296738 nosy: D?enan Zuki? priority: normal severity: normal status: open title: VS2015 support for 2.7 branch versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 23 17:57:36 2017 From: report at bugs.python.org (Alessandro Piccione) Date: Fri, 23 Jun 2017 21:57:36 +0000 Subject: [New-bugs-announce] [issue30743] unittest discover does not mention module file must be named with "test_" prefix Message-ID: <1498255056.87.0.611217256865.issue30743@psf.upfronthosting.co.za> New submission from Alessandro Piccione: 1. execute "python -m unittest" 2. Result: 0 test found 3. Change file name from "aaaTest.py" to "test_aaa.py" 4. execute "python -m unittest" 3. Result: Ran 1 tests in 000.0s Module file MUST be named using the prefiux "test_". The page "https://docs.python.org/3/library/unittest.html" does not mention this MANDATORY rule. I went to this conclusion because I readed the documentation without find any point about the naming convention of modules and than looking for this specific rule searching "test_" and "test_ " without any result. Regards, Alessandro ---------- assignee: docs at python components: Documentation messages: 296740 nosy: alex.75, docs at python priority: normal severity: normal status: open title: unittest discover does not mention module file must be named with "test_" prefix versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 00:05:29 2017 From: report at bugs.python.org (Nathaniel Smith) Date: Sat, 24 Jun 2017 04:05:29 +0000 Subject: [New-bugs-announce] [issue30744] Local variable assignment is broken when combined with threads + tracing + closures Message-ID: <1498277129.07.0.940069687434.issue30744@psf.upfronthosting.co.za> New submission from Nathaniel Smith: The attached script looks innocent, but gives wildly incorrect results on all versions of CPython I've tested. It does two things: - spawns a thread which just loops, doing nothing - in the main thread, repeatedly increments a variable 'x' And most of the increments of the variable are lost! This requires two key things I haven't mentioned, but that you wouldn't expect to change anything. First, the thread function closes over the local variable 'x' (though it doesn't touch this variable in any way). And second, the thread function has a Python-level trace function registered (but this trace function is a no-op). Here's what's going on: When you use sys.settrace() to install a Python-level trace function, it installs the C-level trace function "call_trampoline". And then whenever a trace event happens, call_trampoline calls PyFrame_FastToLocalsWithError, then calls the Python-level trace function, then calls PyFrame_LocalsToFast (see: https://github.com/python/cpython/blob/master/Python/sysmodule.c#L384-L395). This save/call/restore sequence is safe if all the variables being saved/restored are only visible to the current thread, which used to be true back in the days when local variables were really local. But it turns out nowadays (since, uh... python 2.1), local variables can be closed over, and thus can visible from multiple threads simultaneously. Which means we get the following sequence of events: - In thread A, a trace event occurs (e.g., executing a line of code) - In thread A, call_trampoline does PyFrame_FastToLocalsWithError, which saves a snapshot of the current value of 'x' - In thread A, call_trampoline then starts calling the trace function - In thread B, we increment 'x' - In thread A, the trace function returns - In thread A, call_trampoline then does PyFrame_LocalsToFast, which restores the old value of 'x', overwriting thread B's modifications This means that merely installing a Python-level trace function ? for example, by running with 'python -m trace' or under pdb ? can cause otherwise correct code to give wrong answers, in an incredibly obscure fashion. In real life, I originally ran into this in a substantially more complicated situation involving PyPy and coverage.py and a nonlocal variable that was protected by a mutex, which you can read about here: https://bitbucket.org/pypy/pypy/issues/2591/ It turns out that since this only affects *Python*-level trace functions, merely recording coverage information using coverage.py doesn't normally trigger it, since on CPython coverage.py tries to install an accelerator module that uses a *C*-level trace function. Which is lucky for my particular case. But probably it should be fixed anyway :-). CC'ing belopolsky as the interest area for the trace module, Mark Shannon because he seems to enjoy really pathological low-level bugs, and Benjamin and Yury as the "bytecode" interest area. I'm surprised that there's apparently no interest area for, like, "variables should retain the values they are assigned" -- apologies if I've CC'ed anyone incorrectly. ---------- components: Interpreter Core files: thread-closure-bug-demo.py messages: 296751 nosy: Mark.Shannon, belopolsky, benjamin.peterson, njs, yselivanov priority: normal severity: normal status: open title: Local variable assignment is broken when combined with threads + tracing + closures versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file46971/thread-closure-bug-demo.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 06:13:59 2017 From: report at bugs.python.org (Segev Finer) Date: Sat, 24 Jun 2017 10:13:59 +0000 Subject: [New-bugs-announce] [issue30745] Warnings in Modules/_winapi.c Message-ID: <1498299239.67.0.774522890033.issue30745@psf.upfronthosting.co.za> New submission from Segev Finer: ..\Modules\_winapi.c(886): warning C4090: 'function': different 'const' qualifiers ..\Modules\_winapi.c(848): warning C4101: 'wenvironment_size': unreferenced local variable Added in d174d24a5d37d1516b885dc7c82f71ecd5930700 ---------- components: Windows messages: 296761 nosy: Segev Finer, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Warnings in Modules/_winapi.c type: compile error versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 15:05:15 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 24 Jun 2017 19:05:15 +0000 Subject: [New-bugs-announce] [issue30746] Reject environment variable names containing '=' Message-ID: <1498331115.22.0.815724101624.issue30746@psf.upfronthosting.co.za> New submission from Serhiy Storchaka: Environment variable names shouldn't contain the '=' character, because it often is used as a separator between a name and a value. There is an exception -- starting '=' on Windows is used for defining "hidden" environment variables. Using names containing '=' in environment dict in subprocess is prohibited in issue30730. Proposed PR prohibits names containing '=' in two other cases: in os.putenv() and os.spawn*(). It fixes the part of issue4926. ---------- components: Extension Modules messages: 296781 nosy: larry, loewis, serhiy.storchaka priority: normal severity: normal stage: patch review status: open title: Reject environment variable names containing '=' type: behavior versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 15:35:59 2017 From: report at bugs.python.org (=?utf-8?b?UMOkciBCasO2cmtsdW5k?=) Date: Sat, 24 Jun 2017 19:35:59 +0000 Subject: [New-bugs-announce] [issue30747] _Py_atomic_* not actually atomic on Windows with MSVC Message-ID: <1498332959.93.0.572211672441.issue30747@psf.upfronthosting.co.za> New submission from P?r Bj?rklund: _Py_atomic_store and _Py_atomic_load are not implemented as atomic operations on Windows when using Visual Studio to build. This might cause hard to troubleshoot behaviour, especially in third party hosting applications.. ---------- components: Interpreter Core messages: 296786 nosy: Paxxi priority: normal severity: normal status: open title: _Py_atomic_* not actually atomic on Windows with MSVC type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 18:33:37 2017 From: report at bugs.python.org (Ben Lewis) Date: Sat, 24 Jun 2017 22:33:37 +0000 Subject: [New-bugs-announce] [issue30748] Upgrade tuples in socket to named tuple like Message-ID: <1498343617.76.0.0345167407647.issue30748@psf.upfronthosting.co.za> New submission from Ben Lewis: Within the socket module, there are various tuples that are used for different representations of a socket address. There are also other tuples returned by other functions in the socket module. As suggested on Python-ideas(https://mail.python.org/pipermail/python-ideas/2017-June/046028.html) and supported by Guido(https://mail.python.org/pipermail/python-ideas/2017-June/046086.html) these tuples should be made into named-tuple like sequences akin to the time tuple in the datetime module. I am willing to help contribute to make this happen. ---------- components: IO messages: 296792 nosy: Ben Lewis priority: normal severity: normal status: open title: Upgrade tuples in socket to named tuple like type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 18:59:56 2017 From: report at bugs.python.org (Alex Groce) Date: Sat, 24 Jun 2017 22:59:56 +0000 Subject: [New-bugs-announce] [issue30749] Non-atomic and unusual (wrong) rename behavior under OS X, Python 2.7.13 Message-ID: <1498345196.68.0.88210579685.issue30749@psf.upfronthosting.co.za> New submission from Alex Groce: Attached file causes a failed rename, which is fine. However, after the failed rename, the directory structure has changed (and the error reported is not very helpful). Behavior does not match Linux or Windows behavior. Discovered using random testing to check pyfakefs for conformance with os module, using TSTL tool. ---------- components: macOS files: renameatomic.py messages: 296794 nosy: Alex Groce, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: Non-atomic and unusual (wrong) rename behavior under OS X, Python 2.7.13 type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file46973/renameatomic.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Jun 24 19:45:59 2017 From: report at bugs.python.org (Brett Cannon) Date: Sat, 24 Jun 2017 23:45:59 +0000 Subject: [New-bugs-announce] [issue30750] Update `make patchcheck` to understand Misc/NEWS.d Message-ID: <1498347959.85.0.344853864513.issue30750@psf.upfronthosting.co.za> New submission from Brett Cannon: Title says it all. ---------- messages: 296797 nosy: brett.cannon, pitrou priority: normal severity: normal status: open title: Update `make patchcheck` to understand Misc/NEWS.d _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 01:50:20 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Sun, 25 Jun 2017 05:50:20 +0000 Subject: [New-bugs-announce] [issue30751] IDLE: Display entry errors for key sequence entry in entry box Message-ID: <1498369820.44.0.770357079807.issue30751@psf.upfronthosting.co.za> New submission from Terry J. Reedy: One of the features of query.Query boxes is that error messages are displayed in the box (in red) rather than in a separate tkinter.messagebox error box (showerror). This issue is about copying the idea and implementation to config_key.GetKeysDialog. To make testing of patched methods easier, #6739 is adding a trivial showerror method (= tkinter.messagebox.showerror). This issue will replace it with Query.showerror def showerror(self, message, widget=None): #self.bell(displayof=self) (widget or self.entry_error)['text'] = 'ERROR: ' + message and add something like self.entry_error = Label(frame, text=' ', foreground='red', font=self.error_font) just above the exit buttons. This issue should probably add subtests for the ValidationTests. Message test and line break when needed will be adjusted by visual checks. ---------- assignee: terry.reedy components: IDLE messages: 296804 nosy: terry.reedy priority: normal severity: normal stage: needs patch status: open title: IDLE: Display entry errors for key sequence entry in entry box type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 05:14:37 2017 From: report at bugs.python.org (=?utf-8?q?Ren=C3=A9_Podlogar?=) Date: Sun, 25 Jun 2017 09:14:37 +0000 Subject: [New-bugs-announce] [issue30752] Basic subtraction is wrong ( 1.83 - 1.52 == 0.31000000000000005) Message-ID: <1498382077.7.0.583083821643.issue30752@psf.upfronthosting.co.za> New submission from Ren? Podlogar: My Python-Installations Python 2.7.12, Python 3.4.5 @linux64 and the CLI on the python.org-Website (interactive shell) affected: Python 3.6.0 (default, Jan 13 2017, 00:00:00) [GCC 4.8.4] on linux Type "help", "copyright", "credits" or "license" for more information. >>> 1.83 - 1.52 0.31000000000000005 >>> Expected= 0.31 Verified in irc-channel #python.de ---------- messages: 296817 nosy: Ren? Podlogar priority: normal severity: normal status: open title: Basic subtraction is wrong ( 1.83 - 1.52 == 0.31000000000000005) versions: Python 2.7, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 07:11:27 2017 From: report at bugs.python.org (Vishal Devgn) Date: Sun, 25 Jun 2017 11:11:27 +0000 Subject: [New-bugs-announce] [issue30753] not able to execute print command on page 16 of documentation Message-ID: <1498389087.09.0.895603326933.issue30753@psf.upfronthosting.co.za> New submission from Vishal Devgn: >>> a, b = 0, 1 >>> while b < 1000: ... print(b, end=',') ... a, b = b, a+b in 3.6 as soon as i write print command, it displays an indentation error. ---------- files: 1.png messages: 296821 nosy: Vishal Devgn priority: normal severity: normal status: open title: not able to execute print command on page 16 of documentation type: compile error versions: Python 3.6 Added file: http://bugs.python.org/file46974/1.png _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 11:25:24 2017 From: report at bugs.python.org (Julian Berman) Date: Sun, 25 Jun 2017 15:25:24 +0000 Subject: [New-bugs-announce] [issue30754] textwrap.dedent mishandles empty lines Message-ID: <1498404324.65.0.525714137023.issue30754@psf.upfronthosting.co.za> New submission from Julian Berman: ? python2 -c 'from textwrap import dedent; print repr(dedent(" " * 2 + "\n" + " " * 4 + "\n"))' '\n\n' instead of the presumed '\n \n' The same appears to be the case for py3.6. (At first glance, this seems unrelated to http://bugs.python.org/issue19479 although that issue seems to have an unreviewed patch that changes the implementation, so it might also "accidentally" fix the issue). ---------- components: Library (Lib) messages: 296825 nosy: Julian, georg.brandl, terry.reedy priority: normal severity: normal status: open title: textwrap.dedent mishandles empty lines type: behavior versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 12:58:59 2017 From: report at bugs.python.org (Matthew Woodcraft) Date: Sun, 25 Jun 2017 16:58:59 +0000 Subject: [New-bugs-announce] [issue30755] locale.normalize() and getdefaultlocale() convert C.UTF-8 to en_US.UTF-8 Message-ID: <1498409939.21.0.261757462715.issue30755@psf.upfronthosting.co.za> New submission from Matthew Woodcraft: I have a system where the default locale is C.UTF-8, and en_US.UTF-8 is not installed. But locale.normalize() unhelpfully converts "C.UTF-8" to "en_US.UTF-8". So the following crashes for me: python3.6 -c "import locale;locale.setlocale(locale.LC_ALL, ('C', 'UTF-8'))" Similarly getdefaultlocale() returns ('en_US', 'UTF-8'), so this crashes too: export LANG=C.UTF-8 unset LC_CTYPE unset LC_ALL unset LANGUAGE python3.6 -c "import locale;locale.setlocale(locale.LC_ALL, locale.getdefaultlocale())" This behaviour is caused by a locale_alias entry in Lib/locale.py . https://bugs.python.org/issue20076 documents its addition but doesn't provide a rationale. I can see that it might be helpful to provide such a conversion if C.UTF-8 doesn't exist and en_US.UTF-8 does, but the current code is breaking modern correctly-configured systems for the benefit of old misconfigured ones (C.UTF-8 shouldn't really be in the environment if it isn't available on the system, after all). ---------- messages: 296828 nosy: mattheww priority: normal severity: normal status: open title: locale.normalize() and getdefaultlocale() convert C.UTF-8 to en_US.UTF-8 versions: Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Jun 25 15:02:20 2017 From: report at bugs.python.org (Cheryl Sabella) Date: Sun, 25 Jun 2017 19:02:20 +0000 Subject: [New-bugs-announce] [issue30756] GUI tests fail on Ubuntu Message-ID: <1498417340.5.0.500567108578.issue30756@psf.upfronthosting.co.za> New submission from Cheryl Sabella: Running the tests over up to date build on Ubuntu 16.04 64-bit. ./python -m test.test_ttk_guionly -v Sometimes this runs without failure and sometimes it 'hangs' and then produces failures. When it hangs, my computer freezes completely. As you can see, it can run for 8 minutes. It seems to hang most often on test_idenify in EntryTest. Here's one set of failures: ====================================================================== FAIL: test_identify (tkinter.test.test_ttk.test_widgets.EntryTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 332, in test_identify self.assertEqual(self.entry.identify(5, 5), "textarea") AssertionError: '' != 'textarea' + textarea ====================================================================== FAIL: test_get (tkinter.test.test_ttk.test_widgets.ScaleTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 807, in test_get self.assertEqual(self.scale.get(scale_width, 0), self.scale['to']) AssertionError: 0.0 != 1.0 ====================================================================== FAIL: test_set (tkinter.test.test_ttk.test_widgets.ScaleTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 849, in test_set self.assertEqual(conv(self.scale.get(self.scale.winfo_width(), 0)), max) AssertionError: 0.0 != 1.0 ====================================================================== FAIL: test_identify (tkinter.test.test_ttk.test_widgets.WidgetTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 71, in test_identify ), "label") AssertionError: '' != 'label' + label ---------------------------------------------------------------------- Ran 272 tests in 491.572s FAILED (failures=4) Here's another set from a different run: ====================================================================== FAIL: test_get (tkinter.test.test_ttk.test_widgets.ScaleTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 807, in test_get self.assertEqual(self.scale.get(scale_width, 0), self.scale['to']) AssertionError: 0.0 != 1.0 ====================================================================== FAIL: test_set (tkinter.test.test_ttk.test_widgets.ScaleTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 849, in test_set self.assertEqual(conv(self.scale.get(self.scale.winfo_width(), 0)), max) AssertionError: 0.0 != 1.0 ====================================================================== FAIL: test_identify (tkinter.test.test_ttk.test_widgets.WidgetTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_widgets.py", line 71, in test_identify ), "label") AssertionError: '' != 'label' + label ====================================================================== FAIL: test_horizontal_range (tkinter.test.test_ttk.test_extensions.LabeledScaleTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/cheryl/cpython/Lib/tkinter/test/test_ttk/test_extensions.py", line 122, in test_horizontal_range self.assertEqual(prev_xcoord, int(linfo_1['x'])) AssertionError: 16 != 1 ---------------------------------------------------------------------- Ran 272 tests in 353.180s FAILED (failures=4) ---------- components: Tests messages: 296835 nosy: csabella, serhiy.storchaka, terry.reedy priority: normal severity: normal status: open title: GUI tests fail on Ubuntu versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 00:26:08 2017 From: report at bugs.python.org (Denis Akhiyarov) Date: Mon, 26 Jun 2017 04:26:08 +0000 Subject: [New-bugs-announce] [issue30757] pyinstaller can be added to docs, py2exe ref can be updated Message-ID: <1498451168.27.0.593036349197.issue30757@psf.upfronthosting.co.za> New submission from Denis Akhiyarov: https://github.com/python/cpython/pull/1158 It is not clear why this FAQ item is written in addition to this document: https://github.com/python/cpython/blob/master/Doc/faq/windows.rst#how-do-i-make-python-scripts-executable https://github.com/python/cpython/blob/master/Doc/faq/programming.rst#how-can-i-create-a-stand-alone-binary-from-a-python-script ---------- assignee: docs at python components: Documentation messages: 296844 nosy: denfromufa, docs at python priority: normal severity: normal status: open title: pyinstaller can be added to docs, py2exe ref can be updated type: enhancement versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 05:39:54 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 09:39:54 +0000 Subject: [New-bugs-announce] [issue30758] test_pydoc (regrtest?) hangs on ARMv7 Ubuntu 3.x Message-ID: <1498469994.85.0.367724213837.issue30758@psf.upfronthosting.co.za> New submission from STINNER Victor: > ./python ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest --timeout=900 -j2 -j8 faulthandler was supposed to kill test_pydoc after 15 minutes, and regrtest is supposed to log "running: pydoc (since xxx seconds)" every 30 seconds. Something gone bad. Buildbot killed regrtest because it didn't produce output during 20 minutes. http://buildbot.python.org/all/builders/ARMv7%20Ubuntu%203.x/builds/968/steps/test/logs/stdio running: test_pydoc (420 sec), test_datetime (234 sec), test_tools (258 sec) 0:11:42 load avg: 3.90 [404/406] test_datetime passed (240 sec) -- running: test_pydoc (428 sec), test_tools (266 sec) running: test_pydoc (458 sec), test_tools (296 sec) 0:12:13 load avg: 3.15 [405/406] test_tools passed (296 sec) -- running: test_pydoc (459 sec) command timed out: 1200 seconds without output running ['make', 'buildbottest', 'TESTOPTS=-j2 -j8', 'TESTPYTHONOPTS=', 'TESTTIMEOUT=900'], attempting to kill process killed by signal 9 program finished with exit code -1 elapsedTime=1936.512343 ---------- components: Tests keywords: buildbot messages: 296861 nosy: haypo priority: normal severity: normal status: open title: test_pydoc (regrtest?) hangs on ARMv7 Ubuntu 3.x versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 05:44:05 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 09:44:05 +0000 Subject: [New-bugs-announce] [issue30759] [2.7] Fix python2 -m test --list-cases test_multibytecodec_support test_robotparser Message-ID: <1498470245.46.0.632048342488.issue30759@psf.upfronthosting.co.za> New submission from STINNER Victor: On Python 2.7, listing *all* test cases with "./python -m test --list-cases" fails on the following test files: * test_multibytecodec_support * test_robotparser regrtest of Python 2.7 uses the test_main() function of each test file, if the function is defined. Whereas --list-cases is more written as a raw discovery function listing all cases which inherit from unittest.TestCase. These 3 files have base test cases which are "abstract" or configured below. Options: * Modify --list-cases to tolerate failures and report them at exit * Modify these 2 tests to make them more "test discovery"-friendly * Use test_main() function if available but modify its behaviour to only list test cases, instead of running them I would prefer to limit changes in Python 2.7 branch, so IMHO the second option is the best: modify the 2 tests. haypo at selma$ ./python -m test --list-cases test_multibytecodec_support Traceback (most recent call last): ... File "/home/haypo/prog/python/2.7/Lib/test/test_multibytecodec_support.py", line 268, in __init__ self.open_mapping_file().close() # test it to report the error early File "/home/haypo/prog/python/2.7/Lib/test/test_multibytecodec_support.py", line 273, in open_mapping_file return test_support.open_urlresource(self.mapfileurl) AttributeError: 'TestBase_Mapping' object has no attribute 'mapfileurl' haypo at selma$ ./python -m test --list-cases test_robotparser Traceback (most recent call last): ... File "/home/haypo/prog/python/2.7/Lib/test/regrtest.py", line 1511, in list_cases suite = unittest.defaultTestLoader.loadTestsFromName(abstest) File "/home/haypo/prog/python/2.7/Lib/unittest/loader.py", line 103, in loadTestsFromName return self.loadTestsFromModule(obj) File "/home/haypo/prog/python/2.7/Lib/unittest/loader.py", line 65, in loadTestsFromModule tests.append(self.loadTestsFromTestCase(obj)) File "/home/haypo/prog/python/2.7/Lib/unittest/loader.py", line 56, in loadTestsFromTestCase loaded_suite = self.suiteClass(map(testCaseClass, testCaseNames)) TypeError: __init__() takes exactly 6 arguments (2 given) ---------- messages: 296862 nosy: haypo priority: normal severity: normal status: open title: [2.7] Fix python2 -m test --list-cases test_multibytecodec_support test_robotparser _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 05:48:10 2017 From: report at bugs.python.org (quanyechavshuo) Date: Mon, 26 Jun 2017 09:48:10 +0000 Subject: [New-bugs-announce] [issue30760] configparse module in python3 can not write '%' to config file Message-ID: <1498470490.58.0.585332868378.issue30760@psf.upfronthosting.co.za> New submission from quanyechavshuo: Hello,I was using configparser module in python3.6,but find it works not good when I try to write '%' to my config file,below is my func: def update_config_file_key_value(file, section, key_name, key_value): # ??configparser??????????? # section?[]???? if os.path.exists(file) == False: os.system("touch %s" % file) import configparser config = configparser.ConfigParser() config.read(file) sectionList = config.sections() if section not in sectionList: config.add_section(section) config.set(section, key_name, str(key_value)) with open(file, 'w') as f: config.write(f) When I use it as: update_config_file_key_value('config.ini','default','cookie',"123") it works well,but below not ok: update_config_file_key_value('config.ini','default','cookie',"%123") and below not ok: update_config_file_key_value('config.ini','default','cookie',"123%") and below not ok: update_config_file_key_value('config.ini','default','cookie',"12%3") That's to say,configparser can not write '%' to config file. ---------- messages: 296865 nosy: quanyechavshuo priority: normal severity: normal status: open title: configparse module in python3 can not write '%' to config file type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 06:10:13 2017 From: report at bugs.python.org (Louie Lu) Date: Mon, 26 Jun 2017 10:10:13 +0000 Subject: [New-bugs-announce] [issue30761] pdb: Add step / next count arguments Message-ID: <1498471813.04.0.648864128078.issue30761@psf.upfronthosting.co.za> New submission from Louie Lu: This propose to add *count* times on step and next instruction in pdb. step [count] next [count] User can use `next [count]` to run next *count* times, or `step [count]` to run step *count* times, until it countdown, or occure a breakpoint. Similar function has been implemented in gdb[1] before. [1]: https://sourceware.org/gdb/onlinedocs/gdb/Continuing-and-Stepping.html ---------- components: Library (Lib) messages: 296869 nosy: louielu priority: normal severity: normal status: open title: pdb: Add step / next count arguments type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 06:13:37 2017 From: report at bugs.python.org (Antoine Pietri) Date: Mon, 26 Jun 2017 10:13:37 +0000 Subject: [New-bugs-announce] =?utf-8?q?=5Bissue30762=5D_Misleading_messag?= =?utf-8?b?ZSDigJxjYW4ndCBjb25jYXQgYnl0ZXMgdG8gc3Ry4oCd?= Message-ID: <1498472017.09.0.210411923746.issue30762@psf.upfronthosting.co.za> New submission from Antoine Pietri: >>> b'a' + 'a' Traceback (most recent call last): File "", line 1, in TypeError: can't concat bytes to str This error message is misleading because it is reversed: what is really happening is that we're concatenating str to bytes! When you say "attach A to B" it means B is there first and A is added to it afterwards. That said, we can't just reverse the message (?can't concat str to bytes?), because having the message reversed compared to the code would be also misleading. I therefore propose to use ?and? (? ?can't concat bytes and str?), which makes more sense and preserve the order. ---------- messages: 296870 nosy: antoine.pietri priority: normal severity: normal status: open title: Misleading message ?can't concat bytes to str? _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 07:30:08 2017 From: report at bugs.python.org (Yang Xiao) Date: Mon, 26 Jun 2017 11:30:08 +0000 Subject: [New-bugs-announce] [issue30763] There is functionality bug in linecache library. Message-ID: <1498476608.04.0.760408193877.issue30763@psf.upfronthosting.co.za> New submission from Yang Xiao: There is a functionality bug in linecache library. >>test.py<< import linecache def test_getline(f): print linecache.getlines(f) if __name__ == "__main__": tf1 = 'aaa' with open(tf1,'w') as f: f.write('good morning\n') test_getline(tf1) tf2 = 'bbb' with open(tf2,'w') as f: f.write('good evening\n') test_getline(tf2) tf1 = 'aaa' with open(tf1,'w') as f: f.write('good morning 123\n') test_getline(tf1) tf2 = 'bbb' with open(tf2,'w') as f: f.write('good evening 123\n') test_getline(tf2) The expectant output shoule be: ['good morning\n'] ['good evening\n'] ['good morning\n'] ['good evening\n'] However, the script above outputs below: ['good morning\n'] ['good evening\n'] ['good morning\n'] ['good evening\n'] I think there is a bug about implementation of linecache library. ---------- components: 2to3 (2.x to 3.x conversion tool) messages: 296874 nosy: Yang Xiao priority: normal severity: normal status: open title: There is functionality bug in linecache library. type: behavior versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 08:17:09 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 12:17:09 +0000 Subject: [New-bugs-announce] [issue30764] regrtest: Add --fail-env-changed option Message-ID: <1498479429.85.0.905289080128.issue30764@psf.upfronthosting.co.za> New submission from STINNER Victor: The be able to debug bpo-30280 using my bisection script: https://github.com/haypo/misc/blob/205fea00d509ddd1cffa30c5c6f2da012f3ec54e/python/bisect_test.py I would like to be able to mark tests which alter the environment as failed, using an explicit option. It would be nice to be able to enable this option by default, or even remove the option and just make the behaviour as the default, but it would require to fix some issues first (like bpo-30280). ---------- components: Tests messages: 296883 nosy: haypo priority: normal severity: normal status: open title: regrtest: Add --fail-env-changed option type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 08:27:17 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Mon, 26 Jun 2017 12:27:17 +0000 Subject: [New-bugs-announce] [issue30765] PyThread_acquire_lock can block even when asked not ot Message-ID: <1498480037.14.0.659231073261.issue30765@psf.upfronthosting.co.za> New submission from Antoine Pitrou: Discovered in issue30703. When POSIX semaphores are not used for Python locks, pthread_mutex_lock() is called for acquiring a lock even when asked not to block. This can be disastrous when called from a signal handler. ---------- components: Interpreter Core messages: 296886 nosy: haypo, ned.deily, pitrou, ronaldoussoren priority: normal severity: normal stage: needs patch status: open title: PyThread_acquire_lock can block even when asked not ot type: behavior versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 08:40:49 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Mon, 26 Jun 2017 12:40:49 +0000 Subject: [New-bugs-announce] [issue30766] Make CHECK_STATUS_PTHREAD signal-safe Message-ID: <1498480849.13.0.653593799418.issue30766@psf.upfronthosting.co.za> New submission from Antoine Pitrou: Lock functions may be called from the C signal handler, so strive to make them more signal-safe (they are not unfortunately, but minimizing the number of non-signal-safe functions called there is a good thing). Discovered in issue30703. ---------- components: Interpreter Core messages: 296887 nosy: pitrou priority: low severity: normal stage: needs patch status: open title: Make CHECK_STATUS_PTHREAD signal-safe type: behavior versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 09:23:05 2017 From: report at bugs.python.org (Mihail Krivushin) Date: Mon, 26 Jun 2017 13:23:05 +0000 Subject: [New-bugs-announce] [issue30767] logging must check exc_info correctly Message-ID: <1498483385.09.0.415131659339.issue30767@psf.upfronthosting.co.za> New submission from Mihail Krivushin: Logging checking `if exc_info:` and this maybe incorrect, due exception instance can have __bool__ method and thus can be false. If this is a case, then error that is return false from __bool__ will cause logging to swallow traceback. We need to check exc_info correctly. Will do PR myself. ---------- components: Library (Lib) messages: 296892 nosy: krivushinme priority: normal severity: normal status: open title: logging must check exc_info correctly _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 09:50:01 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 13:50:01 +0000 Subject: [New-bugs-announce] [issue30768] PyThread_acquire_lock_timed() should recompute the timeout when interrupted by a signal Message-ID: <1498485001.71.0.115721395457.issue30768@psf.upfronthosting.co.za> New submission from STINNER Victor: The current code of PyThread_acquire_lock_timed() (the implementation not using semaphore) doesn't compute correctly the timeout when pthread_cond_timedwait() is interrupted by a signal. We should recompute the timeout using a deadline. Something like select.select(): if (tvp) deadline = _PyTime_GetMonotonicClock() + timeout; do { ... use tvp if (errno != EINTR) break; /* select() was interrupted by a signal */ if (PyErr_CheckSignals()) goto finally; if (tvp) { timeout = deadline - _PyTime_GetMonotonicClock(); if (timeout < 0) { n = 0; break; } _PyTime_AsTimeval_noraise(timeout, &tv, _PyTime_ROUND_CEILING); /* retry select() with the recomputed timeout */ } } while (1); ---------- messages: 296896 nosy: haypo, neologix, pitrou priority: normal severity: normal status: open title: PyThread_acquire_lock_timed() should recompute the timeout when interrupted by a signal versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 12:41:42 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 16:41:42 +0000 Subject: [New-bugs-announce] [issue30769] test_execve_invalid_env() of test_os leaks references Message-ID: <1498495302.46.0.49393281355.issue30769@psf.upfronthosting.co.za> New submission from STINNER Victor: haypo at selma$ ./python -m test -R 3:3 -m test_execve_invalid_env test_os test_os leaked [2, 2, 2] references, sum=6 test_os leaked [2, 2, 2] memory blocks, sum=6 I don't understand if it's related to bpo-30602 or not? ---------- components: Tests messages: 296915 nosy: haypo priority: normal severity: normal status: open title: test_execve_invalid_env() of test_os leaks references type: resource usage versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 14:08:51 2017 From: report at bugs.python.org (Nate Soares) Date: Mon, 26 Jun 2017 18:08:51 +0000 Subject: [New-bugs-announce] [issue30772] If I make an attribute "[a unicode version of B]", it gets assigned to "[ascii B]", and so on. Message-ID: <1498500531.27.0.587971014084.issue30772@psf.upfronthosting.co.za> New submission from Nate Soares: [NOTE: In this comment, I use BB to mean unicode character 0x1D539, b/c the issue tracker won't let me submit a comment with unicode characters in it.] Directory structure: repro/ foo.py test_foo.py Contents of foo.py: BB = 1 __all__ = ['BB'] Contents of test_foo.py: from .foo import * Error message: AttributeError: module 'repro.foo' has no attribute 'BB' If I change foo.py to have `__all__ = ['B']` (note that 'B' is not the same as 'BB'), then everything works "fine", modulo the fact that now foo.B is a thing and foo.BB is not a thing. [Recall that in the above, BB is a placeholder for U+1D539, which the issuetracker prevents me from writing here.] ---------- components: Unicode messages: 296928 nosy: Nate Soares, ezio.melotti, haypo priority: normal severity: normal status: open title: If I make an attribute "[a unicode version of B]", it gets assigned to "[ascii B]", and so on. versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 14:55:33 2017 From: report at bugs.python.org (Dima Tisnek) Date: Mon, 26 Jun 2017 18:55:33 +0000 Subject: [New-bugs-announce] [issue30773] async generator receives wrong value when shared between coroutines Message-ID: <1498503333.78.0.356156621032.issue30773@psf.upfronthosting.co.za> New submission from Dima Tisnek: MRE ``` import asyncio async def generator(): while True: x = yield 42 print("received", x) await asyncio.sleep(0.1) async def user(name, g): print("sending", name) await g.asend(name) async def helper(): g = generator() await g.asend(None) await asyncio.gather(*(user(f"user-{x}", g) for x in range(3))) if __name__ == "__main__": asyncio.get_event_loop().run_until_complete(helper()) ``` Produces output: ``` sending user-0 received user-0 sending user-1 sending user-2 received None received None ``` Expected output (some variance allowed): ``` sending user-0 received user-0 sending user-1 sending user-2 received user-1 received user-2 ``` Initial report / discussion: https://mail.python.org/pipermail/async-sig/2017-June/000293.html ---------- components: asyncio messages: 296931 nosy: Dima.Tisnek, yselivanov priority: normal severity: normal status: open title: async generator receives wrong value when shared between coroutines type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 15:56:59 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Mon, 26 Jun 2017 19:56:59 +0000 Subject: [New-bugs-announce] [issue30774] list_repr not safe against concurrent mutation Message-ID: <1498507019.02.0.505462443219.issue30774@psf.upfronthosting.co.za> New submission from Antoine Pitrou: list_repr() is careful to fetch the list size on each iteration. However, it seems that the list size may be mutated just after by concurrent code, perhaps in _PyUnicodeWriter_WriteASCIIString() or Py_EnterRecursiveCall(). I witnessed this with a signal handler that shrank a list while printing a list from a loop in the main code path. gdb excerpt: Program received signal SIGSEGV, Segmentation fault. 0x00000000004a17d6 in PyObject_Repr (v=) at Objects/object.c:485 485 res = (*v->ob_type->tp_repr)(v); (gdb) bt #0 0x00000000004a17d6 in PyObject_Repr (v=) at Objects/object.c:485 #1 0x000000000047eef3 in list_repr (v=0x7ffff68e1d08) at Objects/listobject.c:373 [...] (gdb) frame 1 #1 0x000000000047eef3 in list_repr (v=0x7ffff68e1d08) at Objects/listobject.c:373 373 s = PyObject_Repr(v->ob_item[i]); (gdb) p v $2 = (PyListObject *) 0x7ffff68e1d08 (gdb) p i $3 = 19 (gdb) p v->ob_item[18] $12 = (gdb) p v->ob_item[19] $13 = (gdb) p ((PyVarObject*)(v))->ob_size $14 = 19 ---------- messages: 296936 nosy: haypo, pitrou, rhettinger, serhiy.storchaka priority: normal severity: normal status: open title: list_repr not safe against concurrent mutation versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 16:16:57 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 20:16:57 +0000 Subject: [New-bugs-announce] [issue30775] [3.6] test_multiprocessing_forkserver leaks references on Python 3.6 Message-ID: <1498508217.21.0.984521551654.issue30775@psf.upfronthosting.co.za> New submission from STINNER Victor: $ ./python -m test --match=test.test_multiprocessing_forkserver.WithProcessesTestBarrier.test_barrier --match=test.test_multiprocessing_forkserver.WithProcessesTestFinalize.test_finalize -R 3:3 test_multiprocessing_forkserver test_multiprocessing_forkserver leaked [222, 222, 225] memory blocks, sum=669 test_multiprocessing_forkserver failed Total duration: 5 sec Tests result: FAILURE ---------- components: Tests messages: 296942 nosy: haypo priority: normal severity: normal status: open title: [3.6] test_multiprocessing_forkserver leaks references on Python 3.6 type: resource usage versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 17:49:23 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 21:49:23 +0000 Subject: [New-bugs-announce] [issue30776] regrtest: change -R/--huntrleaks rule to decide if a test leaks Message-ID: <1498513763.26.0.144257056209.issue30776@psf.upfronthosting.co.za> New submission from STINNER Victor: Currently, regrtest considers that a test file leaks if at least one run increased or decreased the global reference counter. The problem is that in practice, Python is full of singletons, caches, and other jokes of the garbage collector, etc. To reduce false alarms and focus more on real bugs, I suggest to change the reference difference checker from: def check_rc_deltas(deltas): return any(deltas) to: def check_rc_deltas(deltas): return all(delta>=1 for delta in deltas) It would allow to ignore false positives like: * [3, 0, 0] * [0, 1, 0] * [8, -8, 1] ---------- components: Tests messages: 296950 nosy: haypo priority: normal severity: normal status: open title: regrtest: change -R/--huntrleaks rule to decide if a test leaks versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 17:57:01 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Mon, 26 Jun 2017 21:57:01 +0000 Subject: [New-bugs-announce] [issue30777] IDLE: configdialog -- add docstrings and improve comments Message-ID: <1498514221.98.0.774452449719.issue30777@psf.upfronthosting.co.za> New submission from Terry J. Reedy: Spinoff from #30728. Docstrings are a form of comment. Both leave behavior alone and do not require testing, just human review. Add the docstrings from the original version of PR 2307, and any others. Review and fix comments in light of the comments on that PR. ---------- messages: 296955 nosy: csabella, louielu, terry.reedy priority: normal severity: normal stage: needs patch status: open title: IDLE: configdialog -- add docstrings and improve comments type: enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 17:58:36 2017 From: report at bugs.python.org (STINNER Victor) Date: Mon, 26 Jun 2017 21:58:36 +0000 Subject: [New-bugs-announce] [issue30778] test_bsddb3 crash on x86 Windows XP 2.7 Message-ID: <1498514316.81.0.754509003042.issue30778@psf.upfronthosting.co.za> New submission from STINNER Victor: http://buildbot.python.org/all/builders/x86%20Windows%20XP%202.7/builds/213/steps/test/logs/stdio Run tests in parallel using 2 child processes ... 0:22:09 [321/404/1] test_bsddb3 crashed -- running: test_io (242 sec) test_bsddb3 still working, be patient... Berkeley DB 4.7.25: (May 15, 2008) Test path prefix: c:\docume~1\db3l\locals~1\temp\z-test_bsddb3-2068 ... 361 tests OK. 1 test failed: test_bsddb3 ... Re-running test 'test_bsddb3' in verbose mode ... testCheckElapsedTime (test.test_bsddb3.TimingCheck) ... ok test01_get_returns_none (bsddb.test.test_get_none.GetReturnsNoneTestCase) ... ok test02_get_raises_exception (bsddb.test.test_get_none.GetReturnsNoneTestCase) ... ok testCheckElapsedTime (test.test_bsddb3.TimingCheck) ... ok test01_join (bsddb.test.test_join.JoinTestCase) ... ok testCheckElapsedTime (test.test_bsddb3.TimingCheck) ... ok test01_simple (bsddb.test.test_lock.LockingTestCase) ... ok test02_threaded (bsddb.test.test_lock.LockingTestCase) ... ok test04_lock_timeout2 (bsddb.test.test_lock.LockingTestCase) ... FAIL testCheckElapsedTime (test.test_bsddb3.TimingCheck) ... ok test01_badpointer (bsddb.test.test_misc.MiscTestCase) ... Berkeley DB 4.7.25: (May 15, 2008) Test path prefix: c:\docume~1\db3l\locals~1\temp\z-test_bsddb3-644 program finished with exit code -1073741819 elapsedTime=2073.500000 ---------- messages: 296956 nosy: haypo priority: normal severity: normal status: open title: test_bsddb3 crash on x86 Windows XP 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 18:34:16 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Mon, 26 Jun 2017 22:34:16 +0000 Subject: [New-bugs-announce] [issue30779] IDLE: configdialog -- factor out Changes class Message-ID: <1498516456.91.0.038376204652.issue30779@psf.upfronthosting.co.za> New submission from Terry J. Reedy: configdialog.ConfigDialog mixes together two things: a user interface for changing options and a mechanism for storing proposed changes and applying them to the configuration dictionaries managed by config. The change mechanism is based on a 3-level dict that maps user config file, config file section, and section entry to a new values. Most GUI event handlers insert entries into the dict. Cancel clears the dict. Apply and call a method to apply changes (and then clear them). This issue will factor out the changes structure and all methods that touch it into a new Changes class. ConfigDialog needs to be able to call methods to add changes, clear changes, apply changes, and maybe something else. GUI tests need to be able to query currently stored changes. Tests of Changes, which are part of this issue and should be 'complete', will accept examples changes from the test functions and send changes to either configparser mocks or even the actual configparser structures, but not to disk. A complete test of the GUI (not part of this issue) will simulate user interaction with every widget and then query Changes() to see that the proper changes orders have been recorded. ---------- messages: 296962 nosy: terry.reedy priority: normal severity: normal stage: test needed status: open title: IDLE: configdialog -- factor out Changes class type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 18:38:31 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Mon, 26 Jun 2017 22:38:31 +0000 Subject: [New-bugs-announce] [issue30780] IDLE: configdialog - add tests for ConfigDialog GUI. Message-ID: <1498516711.25.0.892352273971.issue30780@psf.upfronthosting.co.za> New submission from Terry J. Reedy: A complete test of the GUI will simulate user interaction with every widget and then query Changes() to see that the proper changes orders have been recorded. This issue depends on #30779, factor out Changes class. ---------- messages: 296963 nosy: terry.reedy priority: normal severity: normal stage: test needed status: open title: IDLE: configdialog - add tests for ConfigDialog GUI. type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 18:47:15 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Mon, 26 Jun 2017 22:47:15 +0000 Subject: [New-bugs-announce] [issue30781] IDLE: configdialog -- switch to ttk widgets. Message-ID: <1498517235.92.0.120194527847.issue30781@psf.upfronthosting.co.za> New submission from Terry J. Reedy: Change imports and see what else needs fixing. #27755 is one specific ttk switch that could be done before, as part of, or after this. This issue depends on #30780 test GUI ---------- assignee: terry.reedy components: IDLE messages: 296964 nosy: terry.reedy priority: normal severity: normal stage: test needed status: open title: IDLE: configdialog -- switch to ttk widgets. type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 21:05:22 2017 From: report at bugs.python.org (Andy Balaam) Date: Tue, 27 Jun 2017 01:05:22 +0000 Subject: [New-bugs-announce] [issue30782] Allow limiting the number of concurrent tasks in asyncio.as_completed Message-ID: <1498525522.6.0.617023291854.issue30782@psf.upfronthosting.co.za> New submission from Andy Balaam: asyncio.as_completed allows us to provide lots of coroutines (or Futures) to schedule, and then deal with the results as soon as they are available, in a loop, or a streaming style. I propose to allow as_completed to work on very large numbers of coroutines, provided through a generator (rather than a list). In order to make this practical, we need to limit the number of coroutines that are scheduled simultaneously to a reasonable number. For tasks that open files or sockets, a reasonable number might be 1000 or fewer. For other tasks, a much larger number might be reasonable, but we would still like some limit to prevent us running out of memory. I suggest adding a "limit" argument to as_completed that limits the number of coroutines that it schedules simultaneously. For me, the key advantage of as_completed (in the proposed modified form) is that it enables a streaming style that looks quite like synchronous code, but is efficient in terms of memory usage (as you'd expect from a streaming style): #!/usr/bin/env python3 import asyncio import sys limit = int(sys.argv[1]) async def double(x): await asyncio.sleep(1) return x * 2 async def print_doubles(): coros = (double(x) for x in range(1000000)) for res in asyncio.as_completed(coros, limit=limit): r = await res if r % 100000 == 0: print(r) loop = asyncio.get_event_loop() loop.run_until_complete(print_doubles()) loop.close() Using my prototype implementation, this runs faster and uses much less memory on my machine when you run it with a limit of 100K instead of 1 million concurrent tasks: $ /usr/bin/time --format "Memory usage: %MKB\tTime: %e seconds" ./example 1000000 Memory usage: 2234552KB Time: 97.52 seconds $ /usr/bin/time --format "Memory usage: %MKB\tTime: %e seconds" ./example 100000 Memory usage: 252732KB Time: 94.13 seconds I have been working on an implementation and there is some discussion in my blog posts: http://www.artificialworlds.net/blog/2017/06/12/making-100-million-requests-with-python-aiohttp/ and http://www.artificialworlds.net/blog/2017/06/27/adding-a-concurrency-limit-to-pythons-asyncio-as_completed/ Possibly the most controversial thing about this proposal is the fact that we need to allow passing a generator to as_completed instead of enforcing that it be a list. This is fundamental to allowing the style I outlined above, but it's possible that we can do better than the blanket allowing of all generators that I did. ---------- components: asyncio messages: 296982 nosy: andybalaam, yselivanov priority: normal severity: normal status: open title: Allow limiting the number of concurrent tasks in asyncio.as_completed type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 22:23:04 2017 From: report at bugs.python.org (Ofek Lev) Date: Tue, 27 Jun 2017 02:23:04 +0000 Subject: [New-bugs-announce] [issue30783] Spawned subprocesses don't respect environment Message-ID: <1498530184.51.0.0376373958552.issue30783@psf.upfronthosting.co.za> New submission from Ofek Lev: The following example shows that we are indeed changing PATH, but the subprocess does not acknowledge it in Windows 7 x64. Also note this works in Linux (Ubuntu 16.04). ----- import os import subprocess from contextlib import contextmanager from tempfile import TemporaryDirectory def get_python_path(): return subprocess.check_output( ['python', '-c', 'import sys;print(sys.executable)'] ).decode().strip() @contextmanager def temp_chdir(cwd=None): with TemporaryDirectory() as d: origin = cwd or os.getcwd() os.chdir(d) try: yield d finally: os.chdir(origin) def create_venv(d, pypath=None): command = ['virtualenv', d] if pypath: command.extend(['-p', pypath]) subprocess.call(command) @contextmanager def venv(d): if os.path.exists(os.path.join(d, 'bin')): # no cov venv_exe_dir = os.path.join(d, 'bin') elif os.path.exists(os.path.join(d, 'Scripts')): venv_exe_dir = os.path.join(d, 'Scripts') else: raise OSError('Unable to locate executables directory.') old_path = os.environ['PATH'] os.environ['PATH'] = '{}{}{}'.format(venv_exe_dir, os.pathsep, old_path) yield os.environ['PATH'] = old_path def test_venv(): with temp_chdir() as d: d = os.path.join(d, 'test_env') create_venv(d) global_python = get_python_path() print('PATH', os.environ['PATH'][:140]) with venv(d): print('PATH', os.environ['PATH'][:140]) venv_python = get_python_path() assert global_python != venv_python assert global_python == get_python_path() ---------- components: Windows messages: 296986 nosy: Ofekmeister, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Spawned subprocesses don't respect environment type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Jun 26 23:21:40 2017 From: report at bugs.python.org (Louie Lu) Date: Tue, 27 Jun 2017 03:21:40 +0000 Subject: [New-bugs-announce] [issue30784] IDLE: seperate editor window and text Message-ID: <1498533700.74.0.75769354704.issue30784@psf.upfronthosting.co.za> New submission from Louie Lu: Currently, IDLE EditorWindow was mixed with the GUI skeleton and text area, and the other plugin such as hyperparser was operate on editwin. Such a design let IDLE is difficult to changed its GUI design, from new window to new tab style. If we seperate EditorWindow and the text zone, it will make more easy to port to ttk.Notebook. How do you think about this, terry? ---------- assignee: terry.reedy components: IDLE messages: 296992 nosy: louielu, terry.reedy priority: normal severity: normal status: open title: IDLE: seperate editor window and text versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Jun 27 04:01:37 2017 From: report at bugs.python.org (Christopher Aycock) Date: Tue, 27 Jun 2017 08:01:37 +0000 Subject: [New-bugs-announce] [issue30785] ast.c duplicates STR(CHILD) Message-ID: <1498550497.04.0.537095530939.issue30785@psf.upfronthosting.co.za> New submission from Christopher Aycock: The function alias_for_import_name() duplicates logic starting at Python/ast.c:3237 char *sch = STR(CHILD(n, i)); strcpy(s, STR(CHILD(n, i))); s += strlen(sch); *s++ = '.'; I assume the strcpy() is supposed to use the sch value from the line above. There shouldn't be any consequence to the code as it currently is; I just noticed it while reading through the source. ---------- components: Interpreter Core messages: 297018 nosy: Christopher Aycock priority: normal severity: normal status: open title: ast.c duplicates STR(CHILD) type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Jun 27 06:40:08 2017 From: report at bugs.python.org (Radek Smejkal) Date: Tue, 27 Jun 2017 10:40:08 +0000 Subject: [New-bugs-announce] [issue30786] getaddrinfo emulation does not support AI_NUMERICSERV Message-ID: <1498560008.54.0.948539783321.issue30786@psf.upfronthosting.co.za> New submission from Radek Smejkal: Modules/getaddrinfo.c should support AI_NUMERICSERV. Moreover, not supporting AI_NUMERICSERV may cause troubles on platforms where the getaddrinfo function is available but it's buggy (see configure.ac and Modules/socketmodule.c), because Modules/addrinfo.h does not #undef AI_NUMERICSERV and Modules/socketmodule.c exports AI_NUMERICSERV defined in a system header that may collide with another flag defined in Modules/addrinfo.h and confuse the user. ./configure --with-pydebug Comment out HAVE_GETADDRINFO in pyconfig.h Comment out ENABLE_IPV6 in pyconfig.h on platforms where getipnodebyname and friends are not available make -j ./python Python 3.7.0a0 (default, Jun 27 2017, 11:59:50) [GCC 4.7.2] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.AI_NUMERICSERV >>> socket.getaddrinfo(None, "http", flags=socket.AI_NUMERICSERV) Traceback (most recent call last): File "", line 1, in File "/home/radek/src/github/cpython/Lib/socket.py", line 743, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno 3] invalid value for ai_flags. >>> ---------- components: Extension Modules messages: 297020 nosy: smejkar priority: normal severity: normal status: open title: getaddrinfo emulation does not support AI_NUMERICSERV type: behavior versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Jun 27 10:23:18 2017 From: report at bugs.python.org (tom kronmiller) Date: Tue, 27 Jun 2017 14:23:18 +0000 Subject: [New-bugs-announce] [issue30787] Please add a comprehensive index of decorators to the documentation. Message-ID: <1498573398.64.0.663772847899.issue30787@psf.upfronthosting.co.za> New submission from tom kronmiller: It is difficult to learn what decorators there are because there is no single index which lists all of them (at least, I have been unable to find one). Instead, one must stumble across them while reading library module documentation. An index listing the decorators with a short description would be really helpful (to me, at least). Thanks. ---------- assignee: docs at python components: Documentation messages: 297039 nosy: docs at python, tom kronmiller priority: normal severity: normal status: open title: Please add a comprehensive index of decorators to the documentation. type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Jun 27 15:58:41 2017 From: report at bugs.python.org (Joel Hillacre) Date: Tue, 27 Jun 2017 19:58:41 +0000 Subject: [New-bugs-announce] [issue30788] email.policy.SMTP.fold() issue with long filenames with spaces Message-ID: <1498593521.18.0.236128551176.issue30788@psf.upfronthosting.co.za> New submission from Joel Hillacre: Found an issue in email.policy.SMTP.fold on "Content-Disposition" headers for long filenames with spaces. Managed to simply the issue to a test case as follows: >>> from email.policy import SMTP; SMTP.fold('Content-Disposition', 'attachment; filename="{}"'.format('1234 67890' + '1234567890' * 6)) Below are the tracebacks various python versions produces for this code. I think that the difference between python 3.5 - 3.6 and 3.7 are related to the fix in bpo-30532. Python 3.6.1 (default, Apr 7 2017, 09:32:32) & Python 3.5.3 (default, Jan 17 2017, 14:34:36) Traceback (most recent call last): File "", line 1, in File "/usr/lib64/python3.6/email/policy.py", line 183, in fold return self._fold(name, value, refold_binary=True) File "/usr/lib64/python3.6/email/policy.py", line 213, in _fold return self.header_factory(name, ''.join(lines)).fold(policy=self) File "/usr/lib64/python3.6/email/headerregistry.py", line 255, in fold return header.fold(policy=policy) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 300, in fold self._fold(folded) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 1228, in _fold rest._fold(folded) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 347, in _fold if folded.append_if_fits(part): File "/usr/lib64/python3.6/email/_header_value_parser.py", line 149, in append_if_fits token._fold(self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 338, in _fold if folded.append_if_fits(part, tstr): ... last 4 lines repeated 482 more times ... File "/usr/lib64/python3.6/email/_header_value_parser.py", line 149, in append_if_fits token._fold(self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 325, in _fold tstr = str(part) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in __str__ return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in __str__ return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in __str__ return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 196, in return ''.join(str(x) for x in self) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 633, in __str__ return quote_string(''.join(str(x) for x in self)) File "/usr/lib64/python3.6/email/_header_value_parser.py", line 633, in return quote_string(''.join(str(x) for x in self)) RecursionError: maximum recursion depth exceeded while getting the str of an object Python 3.7.0a0 (heads/master:e613e6add5, Jun 27 2017, 12:17:18) Traceback (most recent call last): File "", line 1, in File "/home/joel/PycharmProjects/cpython/Lib/email/policy.py", line 183, in fold return self._fold(name, value, refold_binary=True) File "/home/joel/PycharmProjects/cpython/Lib/email/policy.py", line 213, in _fold return self.header_factory(name, ''.join(lines)).fold(policy=self) File "/home/joel/PycharmProjects/cpython/Lib/email/headerregistry.py", line 255, in fold return header.fold(policy=policy) File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 300, in fold self._fold(folded) File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 1226, in _fold rest._fold(folded) File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 345, in _fold if folded.append_if_fits(part): File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 145, in append_if_fits ws = token.pop_leading_fws() File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 272, in pop_leading_fws return self[0].pop_leading_fws() File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 272, in pop_leading_fws return self[0].pop_leading_fws() File "/home/joel/PycharmProjects/cpython/Lib/email/_header_value_parser.py", line 270, in pop_leading_fws if self[0].token_type == 'fws': IndexError: list index out of range Note that the following example without a space does not cause a traceback: Python 3.7.0a0 (heads/master:e613e6add5, Jun 27 2017, 12:17:18) >>> from email.policy import SMTP; SMTP.fold('Content-Disposition', 'attachment; filename="{}"'.format('1234567890' + '1234567890' * 6)) 'Content-Disposition: attachment;\r\n filename="1234567890123456789012345678901234567890123456789012345678901234567890"\r\n' ---------- components: email messages: 297072 nosy: barry, jhillacre, r.david.murray priority: normal severity: normal status: open title: email.policy.SMTP.fold() issue with long filenames with spaces versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Jun 27 20:10:41 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 28 Jun 2017 00:10:41 +0000 Subject: [New-bugs-announce] [issue30789] Redesign PyCodeObject.co_extras to use a single memory block, instead of two Message-ID: <1498608641.09.0.230211440925.issue30789@psf.upfronthosting.co.za> New submission from STINNER Victor: Currently, _PyCode_SetExtra() uses two memory block for code extras. Using a different structure, it would be possible to use a single memory block: less memory fragmentation, better CPU cache usage, less indirections, etc. It matters since the long term plan for co_extras is to implement of kind-of JIT compiler insider CPython: see bpo-28158. ---------- components: Interpreter Core messages: 297077 nosy: haypo priority: normal severity: normal status: open title: Redesign PyCodeObject.co_extras to use a single memory block, instead of two type: performance versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 05:21:41 2017 From: report at bugs.python.org (Wu Zongyong) Date: Wed, 28 Jun 2017 09:21:41 +0000 Subject: [New-bugs-announce] [issue30790] Can't use proxy to connect internet on windows Message-ID: <1498641701.55.0.210548070467.issue30790@psf.upfronthosting.co.za> Changes by Wu Zongyong : ---------- components: Library (Lib) nosy: Cordius priority: normal severity: normal status: open title: Can't use proxy to connect internet on windows type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 11:18:18 2017 From: report at bugs.python.org (=?utf-8?b?SMOla29uIEjDpmdsYW5k?=) Date: Wed, 28 Jun 2017 15:18:18 +0000 Subject: [New-bugs-announce] [issue30791] tkinter.Tk() adds suffix to window class name when launching multiple instances Message-ID: <1498663098.01.0.2360806195.issue30791@psf.upfronthosting.co.za> New submission from H?kon H?gland: Hello. In order to group several instances of a given application under one icon in the desktop launcher (I am using Ubuntu 17.04) they must have the same appName property of the WM_CLASS string. For example, if I run emacs twice: ?$ emacs & $ emacs & Both instances will show up under the Emacs icon in the desktop launchbar. The reason is that both instances have the same WM_CLASS string. We can check this string using ?$ xprop WM_CLASS and then click on the Emacs window. It then shows: ?WM_CLASS(STRING) = "emacs", "Emacs" Here "emacs" is the resource (appName), and "Emacs" is the className. Now, consider this program (my-tkapp.py): #! /usr/bin/env python import tkinter as tk root = tk.Tk(className='myTkApp') label = tk.Label(root, text="Hello World") label.pack() root.mainloop() If I run this program twice: ?$ my-tkapp.py & $ my-tkapp.py & and then run xprop to check the WM_CLASS property of both windows, the first window gives: ?WM_CLASS(STRING) = "myTkApp", "Mytkapp" whereas the second gives: ?WM_CLASS(STRING) = "myTkApp #2", "Mytkapp" Note that tkinter has added a #2 suffix to the app name property. This is not desired. It makes the window manager group the two windows under separate icons in the desktop launch bar. How can I keep the same appName property of the WM_CLASS string for different instances of my application? Note: This question was first asked at stackoverflow.com: https://stackoverflow.com/q/44795622/2173773 I tried to follow the source from the call: root = tkinter.Tk(className='myTkApp') but at 5 levels down on the stack I ended up inside TCL code, and I was not able to determine who was responsible for adding the "#2" suffix. However, a similar perl script gives the same behavior, so I suspect the problem is within the TCL TK code. Is there a way to change the WM_CLASS property of the window after the call to tkinter.Tk, but before entering mainloop() in order to work around the issue? After entering the mainloop(), I guess it is too late to do anything, since then the icon is already displayed in the window manager's launch bar. I am using Ubuntu 17.04 and Python version 3.6.1. Best regards, H?kon H?gland ---------- components: Tkinter messages: 297191 nosy: hakonhagland priority: normal severity: normal status: open title: tkinter.Tk() adds suffix to window class name when launching multiple instances type: behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 11:48:31 2017 From: report at bugs.python.org (Steven D'Aprano) Date: Wed, 28 Jun 2017 15:48:31 +0000 Subject: [New-bugs-announce] [issue30792] Add contextlib.convert_exception manager Message-ID: <1498664911.2.0.271174194344.issue30792@psf.upfronthosting.co.za> New submission from Steven D'Aprano: As discussed on Python-Ideas, there's some interest in a context manager that can convert an exception from one type to another (similarly to the way PEP 479 has StopIteration converted to RuntimeError. See the thread starting here: https://mail.python.org/pipermail/python-ideas/2017-June/046109.html and particularly Nick's comment here: https://mail.python.org/pipermail/python-ideas/2017-June/046218.html I've written a recipe on ActiveState: https://code.activestate.com/recipes/580808-guard-against-an-exception-in-the-wrong-place/ which acts as both a context manager and function decorator. That can be used as proof-of-concept or as a basis for a PR. ---------- components: Library (Lib) messages: 297193 nosy: ncoghlan, steven.daprano priority: normal severity: normal status: open title: Add contextlib.convert_exception manager type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 14:58:13 2017 From: report at bugs.python.org (Anselm Kiefner) Date: Wed, 28 Jun 2017 18:58:13 +0000 Subject: [New-bugs-announce] [issue30793] Parsing error on f-string-expressions containing strings with backslash Message-ID: <1498676293.91.0.9735369648.issue30793@psf.upfronthosting.co.za> New submission from Anselm Kiefner: Considering that x = 3 f"{'hello' if x == 3 else 'goodbye'} world" is a simple, elegant and powerful piece of code that works just as expected by itself, I often find myself stumbling and wondering why f"text {'\n' if x == 3 else ''} text" fails horribly just because of the \ within the extra quoted string that must be worked around with ugly code like nl = "\n" f"text {nl if x==3 else ''} text" which really doesn't feel like python at all. I am aware that the specification for f-strings says "no \ in expressions", but please consider that in this case, the \ is not really part of the expression but rather part of a string that isn't evaluated as part of the expression, which might just as well be referenced to by a variable. ---------- messages: 297206 nosy: Anselm Kiefner priority: normal severity: normal status: open title: Parsing error on f-string-expressions containing strings with backslash type: behavior versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 16:03:41 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Wed, 28 Jun 2017 20:03:41 +0000 Subject: [New-bugs-announce] [issue30794] Add multiprocessing.Process.kill() Message-ID: <1498680221.55.0.739149893408.issue30794@psf.upfronthosting.co.za> New submission from Antoine Pitrou: subprocess.Popen() has both terminate() and kill() methods. Under Unix, the first sends SIGTERM and the second SIGKILL. multiprocessing.Process() only has terminate(), which sends SIGTERM. It may be useful to add a kill() method to send SIGKILL (on Windows, kill() would be the same as terminate()). One possible use case is when the child process has redefined the SIGTERM handler to something that doesn't trigger an exit (or takes a long time to exit). Or if something non-interruptible is running... ---------- components: Library (Lib) messages: 297216 nosy: davin, pitrou priority: normal severity: normal stage: needs patch status: open title: Add multiprocessing.Process.kill() type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 16:05:38 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Wed, 28 Jun 2017 20:05:38 +0000 Subject: [New-bugs-announce] [issue30795] OS X failures in test_site Message-ID: <1498680338.75.0.476997562196.issue30795@psf.upfronthosting.co.za> New submission from Antoine Pitrou: It seems there is a sporadic failure on OS X (oops, sorry, I mean "macOS"): https://travis-ci.org/python/cpython/jobs/248079407#L3403 ====================================================================== FAIL: test_getsitepackages (test.test_site.HelperFunctionsTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/travis/build/python/cpython/Lib/test/test_site.py", line 266, in test_getsitepackages self.assertEqual(len(dirs), 2) AssertionError: 1 != 2 ---------------------------------------------------------------------- ---------- components: macOS messages: 297217 nosy: haypo, ned.deily, pitrou, ronaldoussoren priority: normal severity: normal status: open title: OS X failures in test_site type: behavior versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 18:23:54 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Wed, 28 Jun 2017 22:23:54 +0000 Subject: [New-bugs-announce] [issue30796] Failures/crashes in test_signal on some buildbots Message-ID: <1498688634.58.0.502091331703.issue30796@psf.upfronthosting.co.za> New submission from Antoine Pitrou: The test added for issue #30703 crashes on some Unix buildbots (FreeBSD 9.x, OS X Tiger, AIX). Example here: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.x/builds/275/steps/test/logs/stdio As noted in the PR for that issue, some systems may have low resolution for setitimer(). For example, the FreeBSD man page says: > Time values smaller than the resolution of the system clock are rounded up to this resolution (typically 10 milliseconds). ---------- components: Tests messages: 297237 nosy: haypo, pitrou priority: normal severity: normal stage: needs patch status: open title: Failures/crashes in test_signal on some buildbots type: behavior versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 18:24:05 2017 From: report at bugs.python.org (Segev Finer) Date: Wed, 28 Jun 2017 22:24:05 +0000 Subject: [New-bugs-announce] [issue30797] ./pyconfig.h:1438:0: warning: "_GNU_SOURCE" redefined [enabled by default] Message-ID: <1498688645.93.0.221276689872.issue30797@psf.upfronthosting.co.za> New submission from Segev Finer: This is caused by _GNU_SOURCE being defined here: https://github.com/python/cpython/blob/c08177a1ccad2ed0d50898c2731b518c631aed14/configure.ac#L124, But also getting defined by AC_USE_SYSTEM_EXTENSIONS (https://github.com/python/cpython/blob/c08177a1ccad2ed0d50898c2731b518c631aed14/configure.ac#L906). AC_USE_SYSTEM_EXTENSIONS does use an #ifndef but Python's AC_DEFINE seems to be getting order after it. ---------- components: Build messages: 297238 nosy: Segev Finer priority: normal severity: normal status: open title: ./pyconfig.h:1438:0: warning: "_GNU_SOURCE" redefined [enabled by default] type: compile error versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Jun 28 22:32:34 2017 From: report at bugs.python.org (James Lin) Date: Thu, 29 Jun 2017 02:32:34 +0000 Subject: [New-bugs-announce] [issue30798] Document that subprocess.Popen does not set PWD Message-ID: <1498703554.38.0.302571639781.issue30798@psf.upfronthosting.co.za> New submission from James Lin: Even though http://bugs.python.org/issue4057 was rejected (which I think is fair), I think it would be worth mentioning something about PWD in the Python docs for subprocess.Popen's cwd parameter (and possibly for os.chdir): 1. It's pretty common for people to use Python to execute other things. 2. I don't think it's that uncommon to come across binaries/scripts that directly read PWD instead of calling getcwd() or equivalent. 3. For people who encounter this problem for the first time, it can be really puzzling. My suggestion would be to add something like: Note: Some programs might expect that the current directory is specified in a PWD environment variable. Callers should explicitly set it themselves when invoking such programs. or even just: Note: Callers are responsible for setting a PWD environment variable if necessary. ---------- assignee: docs at python components: Documentation messages: 297244 nosy: docs at python, jamesdlin priority: normal severity: normal status: open title: Document that subprocess.Popen does not set PWD type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 01:28:50 2017 From: report at bugs.python.org (chexex) Date: Thu, 29 Jun 2017 05:28:50 +0000 Subject: [New-bugs-announce] [issue30799] Improved test coverage Lib/_osx_support.py 99% Message-ID: <1498714130.01.0.630088547438.issue30799@psf.upfronthosting.co.za> Changes by chexex : ---------- components: Tests nosy: chexex priority: normal severity: normal status: open title: Improved test coverage Lib/_osx_support.py 99% versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 01:56:39 2017 From: report at bugs.python.org (dennis) Date: Thu, 29 Jun 2017 05:56:39 +0000 Subject: [New-bugs-announce] [issue30800] zlib.compressobj took too much memory on window Message-ID: <1498715799.11.0.0910878994528.issue30800@psf.upfronthosting.co.za> New submission from dennis: I'm working on a MMORPG Game server, and using the 32bit window Python(Python2.7.9 and Python3.6.0). And i create a zlib.compressobj for every connection. when the connection reach about 7500, the program raise an MemoryError exception. The Program only took me 700MB in memory, But the committed memory is about 2GB. Here is my test result and test code: -----------test result------------------ 7613 compressobj created! ('memory info:', pmem(rss=736342016, vms=2057256960, num_page_faults=179812, pea k_wset=736342016, wset=736342016, peak_paged_pool=130760, paged_pool=130584, pea k_nonpaged_pool=28344, nonpaged_pool=28344, pagefile=2057256960, peak_pagefile=2 057256960, private=2057256960)) --------------test code ---------------- # -*- encoding:utf-8 -*- import os import psutil import zlib def test(): result = [] for i in range(10000): try: result.append(zlib.compressobj()) except: print('%d compressobj created!'%(i)) pid = os.getpid() p = psutil.Process(pid) print('memory info:', p.memory_info()) break if __name__ == '__main__': test() ---------- components: Windows messages: 297257 nosy: dennisding, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: zlib.compressobj took too much memory on window type: resource usage versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 03:56:43 2017 From: report at bugs.python.org (alberfontan1) Date: Thu, 29 Jun 2017 07:56:43 +0000 Subject: [New-bugs-announce] [issue30801] shoutdown process error with python 3.4 and pyqt/PySide Message-ID: <1498723003.06.0.480156754664.issue30801@psf.upfronthosting.co.za> New submission from alberfontan1: For a package applicaction with pyqt/PySide, Python 3.4 on Windows, appers a window fatal error when shoutdown process manager of multiprocessing ---------- components: Library (Lib) messages: 297261 nosy: alberfontan1 priority: normal severity: normal status: open title: shoutdown process error with python 3.4 and pyqt/PySide type: crash versions: Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 04:58:08 2017 From: report at bugs.python.org (winton Wang) Date: Thu, 29 Jun 2017 08:58:08 +0000 Subject: [New-bugs-announce] [issue30802] datetime.datetime.strptime('200722', '%Y%U') Message-ID: <1498726688.6.0.920894490968.issue30802@psf.upfronthosting.co.za> New submission from winton Wang: datetime stiptime error according to "%U" format. Python version: 3.4.3, 2.7.13 ,3.6.0, 3.5.2 from datetime import datetime input: datetime.strptime('201726', '%Y%U') output: datetime.datetime(2007, 1, 1, 0, 0) ---------- components: Library (Lib) messages: 297265 nosy: winton priority: normal severity: normal status: open title: datetime.datetime.strptime('200722', '%Y%U') type: behavior versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 09:36:18 2017 From: report at bugs.python.org (Peter Thomassen) Date: Thu, 29 Jun 2017 13:36:18 +0000 Subject: [New-bugs-announce] [issue30803] Truth value of sets not properly documented Message-ID: <1498743378.1.0.0570911503542.issue30803@psf.upfronthosting.co.za> New submission from Peter Thomassen: The truth value of sets is not properly documented, in particular regarding whether an empty set is considered false or not. Ignoring primitive (such as numerals) as well as user-defined types, https://docs.python.org/3/library/stdtypes.html#truth says: > The following values are considered false: > > - [...] > - any empty sequence, for example, '', (), []. > - any empty mapping, for example, {}. > - [...] > > All other values are considered true According to https://docs.python.org/3/library/stdtypes.html#sequence-types-list-tuple-range, a set is not a sequence (it is unordered, its elements do not have indices, etc.): > There are three basic sequence types: lists, tuples, and range objects. And, according to https://docs.python.org/3/library/stdtypes.html#mapping-types-dict, > There is currently only one standard mapping type, the dictionary. So, as per the documentation, the set type is not a type that can ever be False. However, when I try, bool(set()) evaluates to False. When I asked this on Stack Overflow, someone checked in the CPython code and judged that this is most likely a mere documentation issue: https://stackoverflow.com/a/44813565/6867099 ---------- assignee: docs at python components: Documentation messages: 297268 nosy: docs at python, thomassen priority: normal severity: normal status: open title: Truth value of sets not properly documented type: enhancement versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 11:30:53 2017 From: report at bugs.python.org (STINNER Victor) Date: Thu, 29 Jun 2017 15:30:53 +0000 Subject: [New-bugs-announce] [issue30804] bolen-dmg-3.x build-installer.py failed Message-ID: <1498750253.94.0.363268872371.issue30804@psf.upfronthosting.co.za> New submission from STINNER Victor: It may be related to bpo-29585, see commits: - a8f8d5b4bd30dbe0828550469d98f12d2ebb2ef4 - b01c574ad6d796025152b5d605eceb7816e6f7a7 - 6b42eb17649bed9615b6e6cecaefdb2f46990b2c http://buildbot.python.org/all/builders/bolen-dmg-3.x/builds/209/steps/compile/logs/stdio ... gcc-4.0 -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g -L/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/dmg/libraries/usr/local/lib -Wl,-stack_size,1000000 -framework CoreFoundation Python.framework/Versions/3.7/Python -o python.exe Programs/python.o -ldl -framework CoreFoundation DYLD_FRAMEWORK_PATH=/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/dmg/_bld/python ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ if test $? -ne 0 ; then \ echo "generate-posix-vars failed" ; \ rm -f ./pybuilddir.txt ; \ exit 1 ; \ fi gcc-4.0 -c -fno-strict-aliasing -Wsign-compare -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g -I/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/dmg/libraries/usr/local/include -std=c99 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -IObjects -IInclude -IPython -I. -I/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Include -isysroot /Developer/SDKs/MacOSX10.4u.sdk -DPy_BUILD_CORE -o Modules/_math.o /Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Modules/_math.c File "/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Mac/BuildScript/build-installer.py", line 1643, in main() File "/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Mac/BuildScript/build-installer.py", line 1596, in main buildPython() File "/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Mac/BuildScript/build-installer.py", line 1146, in buildPython runCommand("make") File "/Users/db3l/buildarea.dmg/bolen-dmg-3.x/build/Mac/BuildScript/build-installer.py", line 531, in runCommand raise RuntimeError("command failed: %s"%(commandline,)) RuntimeError: command failed: make program finished with exit code 1 elapsedTime=1419.113943 ---------- components: macOS messages: 297277 nosy: haypo, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: bolen-dmg-3.x build-installer.py failed versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 13:40:25 2017 From: report at bugs.python.org (William Grzybowski) Date: Thu, 29 Jun 2017 17:40:25 +0000 Subject: [New-bugs-announce] [issue30805] asyncio: race condition with debug and subprocess Message-ID: <1498758025.07.0.201255065023.issue30805@psf.upfronthosting.co.za> New submission from William Grzybowski: If a process is schedule to run in the event loop with debug disabled and debug is then enabled before the process finishes it will result in a traceback: debug_log undefined. [2017/06/29 14:39:13] (ERROR) asyncio.default_exception_handler():1261 - Ta sk exception was never retrieved future: exception=UnboundLocal Error("local variable 'debug_log' referenced before assignment",)> Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/vm.py", line 503, in kmod_load kldstat = (await (await Popen(['/sbin/kldstat'], stdout=subprocess.PIPE )).communicate())[0].decode() File "/usr/local/lib/python3.6/asyncio/subprocess.py", line 225, in creat e_subprocess_exec stderr=stderr, **kwds) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1194, in sub process_exec logger.info('%s: %r', debug_log, transport) ---------- components: asyncio messages: 297289 nosy: wg, yselivanov priority: normal pull_requests: 2549 severity: normal status: open title: asyncio: race condition with debug and subprocess versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 15:12:21 2017 From: report at bugs.python.org (James) Date: Thu, 29 Jun 2017 19:12:21 +0000 Subject: [New-bugs-announce] [issue30806] netrc.__repr__() is broken for writing to file Message-ID: <1498763541.77.0.380552653426.issue30806@psf.upfronthosting.co.za> New submission from James: Have any valid .netrc file. For testing purposes you can use this: machine abc.xyz login myusername password mypassword The documentation for netrc.__repr__() states that it "dumps the class data as a string in the format of a netrc file". However, when you try to actually do this, you'll encounter a nasty bug. This can be seen by running the follow commands: auth = netrc.netrc(os.path.expanduser(r"~\.netrc")) print(auth.__repr__()) The expected output is: machine abc.xyz login myusername password mypassword The actual output is: machine abc.xyz login 'myusername' password 'mypassword' If you write this back out to the .netrc file, authentication will fail since incorrect username/password (with ' character at beginning at end) will be passed. ---------- components: Library (Lib) messages: 297296 nosy: Bezier89 priority: normal pull_requests: 2550 severity: normal status: open title: netrc.__repr__() is broken for writing to file type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 15:49:10 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Thu, 29 Jun 2017 19:49:10 +0000 Subject: [New-bugs-announce] [issue30807] setitimer() can disable timer by mistake Message-ID: <1498765750.02.0.334201584192.issue30807@psf.upfronthosting.co.za> New submission from Antoine Pitrou: The C setitimer() function supports intervals with microsecond resolution. However, Python's setitimer() takes a float and then converts it to a C `struct timeval`, which can round down to zero. The consequence is that the timer is disabled (timeval == {0,0}) while the user asked for a one microsecond timeout. ---------- components: Library (Lib) messages: 297300 nosy: pitrou priority: normal severity: normal stage: needs patch status: open title: setitimer() can disable timer by mistake type: behavior versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 16:01:06 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Thu, 29 Jun 2017 20:01:06 +0000 Subject: [New-bugs-announce] [issue30808] Use _Py_atomic API for concurrency-sensitive signal state Message-ID: <1498766466.5.0.206048898577.issue30808@psf.upfronthosting.co.za> New submission from Antoine Pitrou: We already use the _Py_atomic APIs in ceval.c, for lockless boolean flags. We should do the same in the signal module where there are similar concurrency issues (for example between the signal handler running in one thread and PyErr_CheckSignals running in another thread). ---------- components: Interpreter Core messages: 297304 nosy: haypo, jyasskin, neologix, pitrou priority: normal severity: normal stage: patch review status: open title: Use _Py_atomic API for concurrency-sensitive signal state type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Jun 29 16:36:07 2017 From: report at bugs.python.org (Charles Wohlganger) Date: Thu, 29 Jun 2017 20:36:07 +0000 Subject: [New-bugs-announce] [issue30809] IDLE parenmatch - highlighting options Message-ID: <1498768567.92.0.13204753323.issue30809@psf.upfronthosting.co.za> New submission from Charles Wohlganger: Current IDLE parenmatch highlighting uses the 'hilite' style when highlighting the parens/expression. Desired behavior is to use a user-setting based style that is independent from the hilite style (which is used for highlighting selected text). Desired selectable options are for foreground color, background color, underlining and font (which covers font type, size, bold, and italics) Apart from running IDLE and checking that the selections match, I don't know how to test. Testing would need a human to check for correct colors, etc. if it was made, so it couldn't be automated... ---------- assignee: terry.reedy components: IDLE messages: 297317 nosy: terry.reedy, wohlganger priority: normal severity: normal status: open title: IDLE parenmatch - highlighting options type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 03:58:55 2017 From: report at bugs.python.org (Tarek Saier) Date: Fri, 30 Jun 2017 07:58:55 +0000 Subject: [New-bugs-announce] =?utf-8?q?=5Bissue30810=5D_Germany_made_the_?= =?utf-8?b?dXBwZXIgY2FzZSDDnyBvZmZpY2lhbC4gJ8OfJy51cHBlcigpIHNob3VsZCBu?= =?utf-8?b?b3cgcmV0dXJuIOG6ni4=?= Message-ID: <1498809535.65.0.688686047851.issue30810@psf.upfronthosting.co.za> New submission from Tarek Saier: I'm not sure if Python just relies on some other resource for this (i.e. a C function), but as of yesterday the correct upper case of ? is ?: Official announcement in German: http://www.rechtschreibrat.com/DOX/rfdr_PM_2017-06-29_Aktualisierung_Regelwerk.pdf ---------- messages: 297351 nosy: Tarek Saier priority: normal severity: normal status: open title: Germany made the upper case ? official. '?'.upper() should now return ?. _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 05:02:48 2017 From: report at bugs.python.org (Antony Lee) Date: Fri, 30 Jun 2017 09:02:48 +0000 Subject: [New-bugs-announce] [issue30811] A venv created and activated from within a virtualenv uses the outer virtualenv's site-packages rather than its own. Message-ID: <1498813368.34.0.349011380575.issue30811@psf.upfronthosting.co.za> New submission from Antony Lee: Python 3.6.1, virtualenv 15.1.0 (Arch Linux, distro packages) ``` export PIP_CONFIG_FILE=/dev/null # just to be sure # python -mvirtualenv outer-env # using /usr/bin/python(3) python2 -mvirtualenv outer-env # using /usr/bin/python(3) source outer-env/bin/activate python -mvenv inner-env # using outer-env's python source inner-env/bin/activate python -minspect -d pip ``` The last step outputs ``` Target: pip Origin: /tmp/inner-env/lib/python3.6/site-packages/pip/__init__.py Cached: /tmp/inner-env/lib/python3.6/site-packages/pip/__pycache__/__init__.cpython-36.pyc Loader: <_frozen_importlib_external.SourceFileLoader object at 0x7f27c019c710> Submodule search path: ['/tmp/inner-env/lib/python3.6/site-packages/pip'] ``` i.e., the outer environment's pip leaks into the inner environment; the inner environment does not have its own pip installed. Trying to use that pip from the inner environment (from inner-env, `python -mpip install ...`) results in the package being installed in the outer environment rather than the inner one. Now this may all seem very academic, but for example Travis uses virtualenvs as toplevel containers for their Python projects, so this bug makes it difficult to test, say, projects that set up venvs as part of their workflow. ---------- components: Library (Lib) messages: 297365 nosy: Antony.Lee priority: normal severity: normal status: open title: A venv created and activated from within a virtualenv uses the outer virtualenv's site-packages rather than its own. versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 05:43:34 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 30 Jun 2017 09:43:34 +0000 Subject: [New-bugs-announce] [issue30812] Running test_warnings twice fails Message-ID: <1498815814.09.0.930459011173.issue30812@psf.upfronthosting.co.za> New submission from STINNER Victor: Example on Python 3.6: haypo at selma$ ./python -m test test_warnings test_warnings Run tests sequentially 0:00:00 load avg: 1.74 [1/2] test_warnings 0:00:01 load avg: 1.68 [2/2] test_warnings /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:902: UserWarning: foo wmod.warn("foo") /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:1000: UserWarning: foo wmod.warn("foo") /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:964: UserWarning: This is a warning wmod.warn(text) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:986: UserWarning: This is a warning wmod.warn(text) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:148: UserWarning: FilterTests.test_always self.module.warn(message, UserWarning) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:159: UserWarning: FilterTests.test_always_after_ignore self.module.warn(message, UserWarning) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:180: UserWarning: FilterTests.test_default self.module.warn(message, UserWarning) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:249: UserWarning: handle normally self.module.warn(text) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:135: UserWarning: FilterTests.test_ignore_after_default self.module.warn(message, UserWarning) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:195: UserWarning: FilterTests.test_module self.module.warn(message, UserWarning) f.py:42: UserWarning: b __init__.py:42: UserWarning: FilterTests.test_once /home/haypo/prog/python/3.6/Lib/test/test_warnings/data/stacklevel.py:9: UserWarning: spam1 warnings.warn(message, stacklevel=stacklevel) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:354: UserWarning: multi 0 self.module.warn(text) /home/haypo/prog/python/3.6/Lib/test/__main__.py:9: UserWarning: spam9 __main__:9: UserWarning: spam11 __main__:9: UserWarning: spam10 test.test_warnings.data.stacklevel:9: UserWarning: spam8 /home/haypo/prog/python/3.6/Lib/test/test_warnings/data/stacklevel.py:9: UserWarning: spam3 warnings.warn(message, stacklevel=stacklevel) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:415: DeprecationWarning: module-level warning import test.test_warnings.data.import_warning nonascii??:1: UserWarning: text /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:365: UserWarning: self.module.warn(ob) /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:561: MyWarningClass: good warning category self.module.warn('good warning category', MyWarningClass) :42: UserWarning: defaultaction test test.test_warnings:778: UserWarning: test file:42: UserWarning: onceregistry test /home/haypo/prog/python/3.6/Lib/test/test_warnings/__init__.py:741: UserWarning: Warning! self.module.warn('Warning!') /home/haypo/prog/python/3.6/Lib/unittest/case.py:178: UserWarning: Warning! callable_obj(*args, **kwargs) test test_warnings failed -- multiple errors occurred; run in verbose mode for details test_warnings failed 1 test OK. 1 test failed: test_warnings Total duration: 3 sec Tests result: FAILURE ---------- messages: 297368 nosy: haypo priority: normal severity: normal status: open title: Running test_warnings twice fails versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 05:50:28 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 30 Jun 2017 09:50:28 +0000 Subject: [New-bugs-announce] [issue30813] test_unittest fails when hunting reference leaks Message-ID: <1498816228.35.0.729692699149.issue30813@psf.upfronthosting.co.za> New submission from STINNER Victor: Example of Python 3.5 (same error on master): haypo at selma$ ./python -m test -R 3:3 -v test_unittest (...) ====================================================================== ERROR: test_discover_with_init_module_that_raises_SkipTest_on_import (unittest.test.test_discovery.TestDiscovery) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/haypo/prog/python/3.5/Lib/unittest/test/test_discovery.py", line 572, in test_discover_with_init_module_that_raises_SkipTest_on_import pickle.loads(pickle.dumps(suite, proto)) _pickle.PicklingError: Can't pickle : attribute lookup ModuleSkipped on unittest.loader failed ====================================================================== ERROR: test_discover_with_module_that_raises_SkipTest_on_import (unittest.test.test_discovery.TestDiscovery) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/haypo/prog/python/3.5/Lib/unittest/test/test_discovery.py", line 548, in test_discover_with_module_that_raises_SkipTest_on_import pickle.loads(pickle.dumps(suite, proto)) _pickle.PicklingError: Can't pickle : attribute lookup ModuleSkipped on unittest.loader failed ---------- messages: 297370 nosy: haypo priority: normal severity: normal status: open title: test_unittest fails when hunting reference leaks versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 07:09:48 2017 From: report at bugs.python.org (Samuele Santi) Date: Fri, 30 Jun 2017 11:09:48 +0000 Subject: [New-bugs-announce] [issue30814] Import dotted name as alias breaks with concurrency Message-ID: <1498820988.28.0.530762803635.issue30814@psf.upfronthosting.co.za> New submission from Samuele Santi: I noticed this weird behavior in Python 3.6: Apparently ``import package.module as _alias`` fails in a threaded environment, sometimes raising an ``ImportError``, seemingly at random. Everything seems to be working perfectly fine: - On 3.5 and lower - When *not* defining an alias, eg. ``import package.module`` - When using the ``from package import module as alias`` style See this repo with code for reproducing the issue: https://github.com/rshk/python36-import-alias-concurrency-bug I tested this on the system Python 3.6.1 shipped with Archlinux (both inside and outside of a virtualenv), and in the official docker image for 3.6. This all started here https://github.com/psycopg/psycopg2/issues/550 as others were experiencing this issue too. ---------- messages: 297380 nosy: Samuele Santi2 priority: normal severity: normal status: open title: Import dotted name as alias breaks with concurrency versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 08:26:04 2017 From: report at bugs.python.org (INADA Naoki) Date: Fri, 30 Jun 2017 12:26:04 +0000 Subject: [New-bugs-announce] [issue30815] StringIO uses inefficient PyUnicode_AsUCS4 Message-ID: <1498825564.05.0.576507824205.issue30815@psf.upfronthosting.co.za> New submission from INADA Naoki: >From PEP393, PyUnicode_AsUCS4 is inefficient. And C implementation of io.StringIO() uses it. That's why Python 3 is slower than Python 2 on logging_format and logging_simple benchmarks. https://mail.python.org/pipermail/speed/2017-February/000503.html Maybe, it can use _PyUnicodeWriter APIs instead. ---------- components: IO messages: 297394 nosy: inada.naoki priority: normal severity: normal status: open title: StringIO uses inefficient PyUnicode_AsUCS4 type: performance versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 10:19:31 2017 From: report at bugs.python.org (Xavier de Gaye) Date: Fri, 30 Jun 2017 14:19:31 +0000 Subject: [New-bugs-announce] [issue30817] Abort in PyErr_PrintEx() when no memory Message-ID: <1498832371.19.0.0580869338001.issue30817@psf.upfronthosting.co.za> New submission from Xavier de Gaye: To reproduce the abort (the set_nomemory() function is being added to _testcapi in issue 30695): $ ./python memerr.py python: Objects/call.c:89: _PyObject_FastCallDict: Assertion `!PyErr_Occurred()' failed. Aborted (core dumped) The corresponding backtrace: #0 0x00007ffff7131670 in raise () from /usr/lib/libc.so.6 #1 0x00007ffff7132d00 in abort () from /usr/lib/libc.so.6 #2 0x00007ffff712a45a in __assert_fail_base () from /usr/lib/libc.so.6 #3 0x00007ffff712a4d2 in __assert_fail () from /usr/lib/libc.so.6 #4 0x00000000004628ce in _PyObject_FastCallDict ( callable=, args=args at entry=0x7fffffffe330, nargs=nargs at entry=3, kwargs=kwargs at entry=0x0) at Objects/call.c:89 #5 0x0000000000426004 in PyErr_PrintEx (set_sys_last_vars=set_sys_last_vars at entry=1) at Python/pythonrun.c:641 #6 0x00000000004263ac in PyErr_Print () at Python/pythonrun.c:510 #7 0x0000000000427586 in PyRun_SimpleFileExFlags (fp=fp at entry=0x987620, filename=, filename at entry=0x7ffff6febcd0 "memerr.py", closeit=closeit at entry=1, flags=flags at entry=0x7fffffffe4cc) at Python/pythonrun.c:403 #8 0x0000000000427673 in PyRun_AnyFileExFlags (fp=fp at entry=0x987620, filename=0x7ffff6febcd0 "memerr.py", closeit=closeit at entry=1, flags=flags at entry=0x7fffffffe4cc) at Python/pythonrun.c:82 #9 0x0000000000437217 in run_file (fp=fp at entry=0x987620, filename=0x91a190 L"memerr.py", p_cf=p_cf at entry=0x7fffffffe4cc) at Modules/main.c:341 #10 0x0000000000437bae in Py_Main (argc=argc at entry=2, argv=argv at entry=0x918020) at Modules/main.c:901 #11 0x000000000041d7fa in main (argc=2, argv=0x7fffffffe6c8) at ./Programs/python.c:102 ---------- components: Interpreter Core files: memerr.py messages: 297408 nosy: xdegaye priority: normal severity: normal status: open title: Abort in PyErr_PrintEx() when no memory type: crash versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file46982/memerr.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 10:17:08 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 30 Jun 2017 14:17:08 +0000 Subject: [New-bugs-announce] [issue30816] test_open() of test_eintr timeout after 10 min Message-ID: <1498832228.54.0.975621351907.issue30816@psf.upfronthosting.co.za> New submission from STINNER Victor: http://buildbot.python.org/all/builders/x86-64%20El%20Capitan%203.x/builds/413/steps/test/logs/stdio 0:32:36 load avg: 1.58 [328/406/1] test_eintr failed test_all (test.test_eintr.EINTRTests) ... FAIL ====================================================================== FAIL: test_all (test.test_eintr.EINTRTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/test_eintr.py", line 18, in test_all script_helper.assert_python_ok("-u", tester) File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/script_helper.py", line 151, in assert_python_ok return _assert_python(True, *args, **env_vars) File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/script_helper.py", line 137, in _assert_python res.fail(cmd_line) File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/script_helper.py", line 79, in fail err)) AssertionError: Process return code is 1 command line: ['/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/python.exe', '-X', 'faulthandler', '-I', '-u', '/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py'] stdout: --- test_read (__main__.OSEINTRTest) ... ok test_wait (__main__.OSEINTRTest) ... ok test_wait3 (__main__.OSEINTRTest) ... ok test_wait4 (__main__.OSEINTRTest) ... ok test_waitpid (__main__.OSEINTRTest) ... ok test_write (__main__.OSEINTRTest) ... ok test_accept (__main__.SocketEINTRTest) ... ok test_open (__main__.SocketEINTRTest) ... --- stderr: --- Timeout (0:10:00)! Thread 0x00007fff79b17000 (most recent call first): File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py", line 343 in python_open File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py", line 339 in _test_open File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/__init__.py", line 556 in wrapper File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py", line 348 in test_open File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/case.py", line 615 in run File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/case.py", line 663 in __call__ File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/suite.py", line 122 in run File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/suite.py", line 84 in __call__ File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/suite.py", line 122 in run File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/suite.py", line 84 in __call__ File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/unittest/runner.py", line 176 in run File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/__init__.py", line 1896 in _run_suite File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/support/__init__.py", line 1940 in run_unittest File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py", line 488 in test_main File "/Users/buildbot/buildarea/3.x.billenstein-elcapitan/build/Lib/test/eintrdata/eintr_tester.py", line 492 in --- ---------------------------------------------------------------------- Ran 1 test in 603.735s FAILED (failures=1) Warning -- files was modified by test_eintr Before: [] After: ['@test_40253_tmp'] test test_eintr failed ---------- components: Tests, macOS keywords: buildbot messages: 297407 nosy: haypo, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: test_open() of test_eintr timeout after 10 min versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 11:04:34 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 30 Jun 2017 15:04:34 +0000 Subject: [New-bugs-announce] [issue30818] Warning -- asyncore.socket_map was modified by test_ftplib on AMD64 FreeBSD 10.x Shared 3.x Message-ID: <1498835074.68.0.82947303088.issue30818@psf.upfronthosting.co.za> New submission from STINNER Victor: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.x%20Shared%203.x/builds/524/steps/test/logs/stdio test_with_statement (test.test_ftplib.TestTLS_FTPClassMixin) ... ok test_auth_issued_twice (test.test_ftplib.TestTLS_FTPClass) ... ok test_auth_ssl (test.test_ftplib.TestTLS_FTPClass) ... ok test_ccc (test.test_ftplib.TestTLS_FTPClass) ... ok test_check_hostname (test.test_ftplib.TestTLS_FTPClass) ... ok test_context (test.test_ftplib.TestTLS_FTPClass) ... ok test_control_connection (test.test_ftplib.TestTLS_FTPClass) ... ok test_data_connection (test.test_ftplib.TestTLS_FTPClass) ... ok test_login (test.test_ftplib.TestTLS_FTPClass) ... Exception in thread Thread-88: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 388, in recv return super(SSLConnection, self).recv(buffer_size) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 374, in recv data = self.socket.recv(buffer_size) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/ssl.py", line 987, in recv return self.read(buflen) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/ssl.py", line 865, in read return self._sslobj.read(len, buffer) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/ssl.py", line 627, in read v = self._sslobj.read(len) ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2136) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asynchat.py", line 117, in handle_read data = self.recv(self.ac_in_buffer_size) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 394, in recv self.handle_close() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asynchat.py", line 190, in handle_close self.close() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 404, in close self._do_ssl_shutdown() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 356, in _do_ssl_shutdown super(SSLConnection, self).close() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 397, in close self.socket.close() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/socket.py", line 417, in close self._real_close() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/ssl.py", line 1052, in _real_close socket._real_close(self) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/socket.py", line 411, in _real_close _ss.close(self) ConnectionResetError: [Errno 54] Connection reset by peer During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 83, in read obj.handle_read_event() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 366, in handle_read_event super(SSLConnection, self).handle_read_event() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 423, in handle_read_event self.handle_read() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asynchat.py", line 121, in handle_read self.handle_error() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 399, in handle_error raise Exception Exception During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/threading.py", line 917, in _bootstrap_inner self.run() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 279, in run asyncore.loop(timeout=0.1, count=1) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 207, in loop poll_fun(timeout, map) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 150, in poll read(obj) File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/asyncore.py", line 87, in read obj.handle_error() File "/usr/home/buildbot/python/3.x.koobs-freebsd10/build/Lib/test/test_ftplib.py", line 399, in handle_error raise Exception Exception ok test__all__ (test.test_ftplib.MiscTestCase) ... ok ---------------------------------------------------------------------- Ran 89 tests in 11.986s OK Warning -- threading_cleanup() failed to cleanup 0 threads after 2 sec (count: 0, dangling: 2) Warning -- asyncore.socket_map was modified by test_ftplib Before: {} After: {4: } ---------- components: Tests messages: 297415 nosy: haypo priority: normal severity: normal status: open title: Warning -- asyncore.socket_map was modified by test_ftplib on AMD64 FreeBSD 10.x Shared 3.x versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 12:56:50 2017 From: report at bugs.python.org (Robert Boehne) Date: Fri, 30 Jun 2017 16:56:50 +0000 Subject: [New-bugs-announce] [issue30819] Linking with 'ld -b' fails with 64-bit using HP compiler Message-ID: <1498841810.07.0.0205568789779.issue30819@psf.upfronthosting.co.za> Changes by Robert Boehne : ---------- components: Build nosy: Robert Boehne priority: normal severity: normal status: open title: Linking with 'ld -b' fails with 64-bit using HP compiler type: compile error versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 13:03:41 2017 From: report at bugs.python.org (Anton Khirnov) Date: Fri, 30 Jun 2017 17:03:41 +0000 Subject: [New-bugs-announce] [issue30820] email.contentmanager.raw_data_manager fails to create multipart messages Message-ID: <1498842221.12.0.837001254234.issue30820@psf.upfronthosting.co.za> New submission from Anton Khirnov: The documentation for the "new API" -- email.contentmanager.raw_data_manager -- claims that passing a list of messages to set_content() will create a multipart message. However, it fails with "KeyError: 'builtins.list'" and from looking at the code it seems this functionality is not and never was implemented. ---------- components: email messages: 297430 nosy: barry, elenril, r.david.murray priority: normal severity: normal status: open title: email.contentmanager.raw_data_manager fails to create multipart messages type: behavior versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 13:13:29 2017 From: report at bugs.python.org (Max Rothman) Date: Fri, 30 Jun 2017 17:13:29 +0000 Subject: [New-bugs-announce] [issue30821] unittest.mock.Mocks with specs aren't aware of default arguments Message-ID: <1498842809.59.0.716482523297.issue30821@psf.upfronthosting.co.za> New submission from Max Rothman: For a function f with the signature f(foo=None), the following three calls are equivalent: f(None) f(foo=None) f() However, only the first two are equivalent in the eyes of unittest.mock.Mock.assert_called_with: >>> with patch('__main__.f', autospec=True) as f_mock: f_mock(foo=None) f_mock.assert_called_with(None) >>> with patch('__main__.f', autospec=True) as f_mock: f_mock(None) f_mock.assert_called_with() AssertionError: Expected call: f() Actual call: f(None) This is definitely surprising to new users (it was surprising to me!) and unnecessarily couples tests to how a particular piece of code happens to call a function. ---------- components: Library (Lib) messages: 297433 nosy: Max Rothman priority: normal severity: normal status: open title: unittest.mock.Mocks with specs aren't aware of default arguments versions: Python 2.7, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Jun 30 19:47:48 2017 From: report at bugs.python.org (Utkarsh Upadhyay) Date: Fri, 30 Jun 2017 23:47:48 +0000 Subject: [New-bugs-announce] [issue30822] Python implementation of datetime module is not being tested correctly. Message-ID: <1498866468.86.0.743233238239.issue30822@psf.upfronthosting.co.za> New submission from Utkarsh Upadhyay: While investigating http://bugs.python.org/issue30302 it was discovered that the Python implementation of the datetime module was not being tested correctly. The datetimetester.py was supposed to execute tests twice, once for the _Fast implementation (i.e. C extension code in _datetimemodule.c) and once for the _Pure implementation (i.e the Python code). The fix is contained in the following two commits: - https://github.com/python/cpython/pull/1493/commits/08e7548f56838fca43b488cefe51de4bdd600f3d - https://github.com/python/cpython/pull/1493/commits/94d5a4e4d33a1d14a2bb1be8fbff5e1e4cd2b7a6 The bug does not effect Python 2.7 as the C version of the datetime module had not been introduced back then. However, as fas as I can tell, the fix needs to be applied to all Python 3.x branches. ---------- components: Tests messages: 297455 nosy: musically_ut, serhiy.storchaka priority: normal severity: normal status: open title: Python implementation of datetime module is not being tested correctly. type: enhancement versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________