[issue14937] IDLE's deficiency in the completion of file names (Python 32, Windows XP)
Roger Serwy
report at bugs.python.org
Sat Jun 2 22:03:52 CEST 2012
Roger Serwy <roger.serwy at gmail.com> added the comment:
I agree that chr(32) should be included in FILENAME_CHARS.
The algorithm for backward searching checks that each character is contained in FILENAME_CHARS. I'm concerned about running time, as expanding FILENAME_CHARS to include all valid Unicode would be a large set to search. Do you know a better algorithm for determining when to perform a file-system completion when in a string?
Also, are there any Unicode code points above 127 that are not valid in a filename? I appreciate that different file systems can have different constraints but I don't know all these subtle points.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14937>
_______________________________________
More information about the Python-bugs-list
mailing list