[issue40740] Missing api-ms-win-core-path-l1-1.0.dll for python-3.9.0b1-amd64.exe Under Win7
Claudio Canepa added the comment: also, no mention in https://pythondev.readthedocs.io/platforms.html -- ___ Python tracker <https://bugs.python.org/issue40740> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40740] Missing api-ms-win-core-path-l1-1.0.dll for python-3.9.0b1-amd64.exe Under Win7
Claudio Canepa added the comment: opps, [0] https://www.python.org/downloads/release/python-390b5/ -- ___ Python tracker <https://bugs.python.org/issue40740> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40740] Missing api-ms-win-core-path-l1-1.0.dll for python-3.9.0b1-amd64.exe Under Win7
Claudio Canepa added the comment: At beta 5 the download page [0] says nothing about dropping win7 support. The installer, at least the one I tried ( python-3.9.0b5-amd64.exe ) will install on win7, and without warnings. It would be much better if it refused to install. -- nosy: +ccanepa ___ Python tracker <https://bugs.python.org/issue40740> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20867] fix_import in 2to3 adds spurious relative import (windows)
Claudio Canepa added the comment: No. #19510 is about 2 to 3 confused when the same import line has some modules that should be 'relativized' and others that not. The present issue is about 2to3 incorrectly 'relativize' a module / package by forgetting that module names are case-sensitive but filenames are case-insensitive in windows. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20867 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20867] fix_import in 2to3 adds spurious relative import (windows)
New submission from Claudio Canepa: 0. windows specific i. In the pyglet library, written for py2 and officially running in 3 after the stock installation that does the 2to3 conversion ii. Omitting files which are unimportant for the issue, the package dir looks as pyglet image codecs pil.py (each package - subpackage has a proper __init__.py) iii. In the pyglet repository checkout, near the begining of pil.py theres the block try: import Image except ImportError: from PIL import Image That PIL refers to the pillow package (fork of PIL, and yes it its the recommended import line in pillow's doc) iv. after installing with cd working_copy py -3.3 setup.py install the same block looks as try: import Image except ImportError: from .PIL import Image which is wrong, and precludes pyglet to import Pillow. v. I tracked the problem to (CPython) LIB/lib2to3/fixes/fix_import.py In method FixImport.probably_a_local_import the heuristic is if 'import name' is seen, look if theres a sibling file with that name, and if exists assume it needs to be a relative import The problem is that the implementation uses os.path.exists to check sibling existence, but that has false positive cases due to Windows case-insensivity for filenames. Module names are case-sensitive. So, the import machinery would never match PIL to pil, but the code in fix_import.py will merrily match. vi. To verify the issue I patched fix_import.py, deleted the old pyglet install under 3, reinstalled: Now the block is unmolested. Attached the diff with the fixed code (diff obtained with the GNU C utils) vii. This was seen in python 3.3.1 , on Windows xp sp3. I see in the cpython repo the same issue will happen in the default branch (the offending lines in fix_import.py are unchanged, so I assume 3.4 will show the same defect) viii. as a reference, the original issue in pyglet can be found at http://code.google.com/p/pyglet/issues/detail?id=707 ix. Anyone can suggest a workaround, a change in the problematic block in pyglet that would tell 2to3 to not change the block ? -- components: 2to3 (2.x to 3.x conversion tool) files: fix_import.diff keywords: patch messages: 212899 nosy: ccanepa priority: normal severity: normal status: open title: fix_import in 2to3 adds spurious relative import (windows) type: behavior versions: Python 3.3 Added file: http://bugs.python.org/file34302/fix_import.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20867 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5559] IDLE Output Window 's goto fails when path has spaces
Claudio Canepa ccanep...@gmail.com added the comment: On Sat, May 2, 2009 at 11:31 PM, Kurt B. Kaiser rep...@bugs.python.orgwrote: Kurt B. Kaiser k...@shore.net added the comment: r72227. How's your test code coming? A relative Win filename with leading spaces should be found even when there's a file of same name but no spaces. -- keywords: +26backport ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5559 ___ Sorry for the delay, Kurt. Test with rev 72227 , ok. test cases: (one space betwwen a and b , one before second tmp, one before first x) Searching 'hello' in d:\tmp\*.tmp ... d:\tmp\ xx.tmp: 1: hello # see woot.py:24 :24 d:\tmp\a b\ tmp\ xx.tmp: 1: hello # see woot.py:24 :24 d:\tmp\a b\ xx.tmp: 1: hello # see woot.py:24 :24 Found 3 hits. ( all three opens the correct file) Same changing the target lines to stress the regex: d:\tmp\ xx.tmp: 1: hello # see woot.py: 24:24 d:\tmp\a b\ tmp\ xx.tmp: 1: hello # see woot.py: 24:24 d:\tmp\a b\ xx.tmp: 1: hello # see woot.py: 24:24 Found 3 hits. ( all three opens the correct file) Non absolute path: xx.py: 1: hello # see woot.py: 24:24 xx.py: 1: hello # see woot.py: 24:24 Found 2 hits. ( both opens the correct file) others; not listed: ok. Thanks for taking care Kurt. -- Added file: http://bugs.python.org/file13848/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5559 ___brbr div class=gmail_quoteOn Sat, May 2, 2009 at 11:31 PM, Kurt B. Kaiser span dir=ltrlt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;/span wrote:br blockquote class=gmail_quote style=PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid div class=imbrKurt B. Kaiser lt;a href=mailto:k...@shore.net;k...@shore.net/agt; added the comment:brbr/divr72227.brbrHow#39;s your test code coming?  A relative Win filename with leadingbrspaces should be found even when there#39;s a file of same name but nobr spaces.brbr--/blockquote blockquote class=gmail_quote style=PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solidspan id=/spanbrkeywords: +26backportbr div div/div div class=h5br___brPython tracker lt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;brlt;a href=http://bugs.python.org/issue5559; target=_blankhttp://bugs.python.org/issue5559/agt;br ___br/div/div/blockquote/div divbr /div div /div divSorry for the delay, Kurt./div divTest with rev 72227 , ok./div div /div divtest cases:/div div(one space betwwen a and b , one before second tmp, one before first x)/div divSearching #39;hello#39; in d:\tmp\*.tmp ...brd:\tmp\ xx.tmp: 1: hello # see woot.py:24 :24 brd:\tmp\a b\ tmp\ xx.tmp: 1: hello # see woot.py:24 :24 brd:\tmp\a b\ xx.tmp: 1: hello # see woot.py:24 :24 brFound 3 hits.br ( all three opens the correct file)/div div /div divSame changing the target lines to stress the regex:/div divd:\tmp\ xx.tmp: 1: hello # see woot.py: 24:24 brd:\tmp\a b\ tmp\ xx.tmp: 1: hello # see woot.py: 24:24 brd:\tmp\a b\ xx.tmp: 1: hello # see woot.py: 24:24 brFound 3 hits.br( all three opens the correct file)/div div /div divNon absolute path:/div div xx.py: 1: hello # see woot.py: 24:24 brxx.py: 1: hello # see woot.py: 24:24 brFound 2 hits.br( both opens the correct file)/div div /div divothers; not listed: ok./div div /div divThanks for taking care Kurt./div divspan lang=ES-MODERN/span /div divspan lang=ES-MODERN--/span/div divccanepa/div ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5559] IDLE Output Window 's goto fails when path has spaces
Claudio Canepa ccanep...@gmail.com added the comment: On a second look: 1. the code in OutputWindow.py for the 'goto' action looks for a match with the first regex in file_line_pats = [ r'file ([^]*), line (\d+)', r'([^\s]+)\((\d+)\)', r'([^\s]+):\s*(\d+):', ] and it assumes the first group gives a valid filename, the second a line number. 2. the potential target lines produced by GrepDialog.py are writen by: sys.stdout.write(%s: %s: %s\n % (fn, lineno, line)) where: fn :a valid filename ( because an open(fn) was issued before), not guaranted an abspath lineno : unsigned int line: a text line in an arbitrary file, but mostly an *.py Clearly the 3rd regex is the only one that can hit the line produced by GrepDialog, and clearly will fail in any OS that allows spaces in a valid path: the regex breaks the first group at the first whitespace. The tentative fix propossed in the initial post was a minimal change that allow spaces in the path, but was very ugly and not comunicates a clear intention. I like more: r'(?:\s*)(.+):\s+(\d+):' wich discards leading whitespace ( feature unused by GrepDialog but probably handy in pyShell, wich subclasses OutputWindow ) It is a better regex that the original in IDLE, meaning it would hit more positives, but can fail sometimes: Supose the GrepDialog found a hit at line 111 in the file c:\foo.py , with the text a = 1 # see 24: 32: 1 The line sent to OutputWindow would be c:\foo.py: 111: a = 1 # see 24: 32: 1 and the regex will capture the groups: filename = c:\foo.py: 111: a = 1 # see 24 linenum = 32 The first group fails to capture the filename. I can live with such special case failures, but anyway: In windows, changing the regex to break the first group at the first ': ' would fix the thing ( ': ' cant happen in a fn that pass open (fn) ) How about other OSes ? -- -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5559 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5559] IDLE Output Window 's goto fails when path has spaces
New submission from Claudio Canepa ccanep...@gmail.com: in windows XP, python 2.6.1, 2.6 , python 2.4 1. do an Edit | 'Find in files' [ it pop ups the Output Window with result] 2. Right click over one of the target lines found, click the 'goto file \line' pop up If the path in the target line has spaces, it will popup a window with title 'No special line' and message 'the line you point at doenst look like a valid file name followed by a line number' posible fix: in idlelib/OutputWindow.py replace the literal r'([^\s]+):\s*(\d+):' with r'([^\t\n\r\f\v]+):\s*(\d+):' fair warning: seems to work in windows XP, dont know about other OSes -- components: IDLE messages: 84142 nosy: ccanepa severity: normal status: open title: IDLE Output Window 's goto fails when path has spaces type: behavior versions: Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5559 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
