This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fgracia
Recipients fgracia, loewis, roger.serwy, terry.reedy, westley.martinez
Date 2012-06-02.21:02:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338670948.72.0.846032057338.issue14937@psf.upfronthosting.co.za>
In-reply-to
Content
Is there any necessity at all for the IDLE to test the validity of the filenames? 

I mean: the file specification is provided by the underlying operating system, so by definition it has to be taken as valid. Testing for its validity is superfluous and, in my opinion, a fault in the general conception of the procedure. IDLE's only role should be to present the data it receives in the best possible form and silently integrate the election made by the user.

Excuse me if I speak nonsense, but I got this idea from studying *Autocomplete.py* and its dependencies. It seems to me that the difficulty resides in submitting natural language strings to the judgement of *PyParse* and *Hyperparser*, which are not competent for it because its purpose is to check the validity of Python code and Python *identifiers*. This confussion is what in my opinion causes this bug (and probably others related to the treatment of natural language text files by the IDLE, as it could also happen with issue 14929).
History
Date User Action Args
2012-06-02 21:02:28fgraciasetrecipients: + fgracia, loewis, terry.reedy, roger.serwy, westley.martinez
2012-06-02 21:02:28fgraciasetmessageid: <1338670948.72.0.846032057338.issue14937@psf.upfronthosting.co.za>
2012-06-02 21:02:28fgracialinkissue14937 messages
2012-06-02 21:02:27fgraciacreate