[Python-Dev] Criticism of execfile() removal in Python3 (original) (raw)
Steve Dower Steve.Dower at microsoft.com
Sun Jun 15 01:36:15 CEST 2014
- Previous message: [Python-Dev] Criticism of execfile() removal in Python3
- Next message: [Python-Dev] Criticism of execfile() removal in Python3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think the point is that the encoding may be embedded in the file as a coding comment and there's no obvious way to deal with that.
Top-posted from my Windows Phone
From: Greg Ewing<mailto:greg.ewing at canterbury.ac.nz> Sent: 6/14/2014 16:19 To: python-dev at python.org<mailto:python-dev at python.org> Subject: Re: [Python-Dev] Criticism of execfile() removal in Python3
Fabio Zadrozny wrote:
Well, I must say that the exec(open().read()) is not really a proper execfile implementation because it may fail because of encoding issues...
It's not far off, though -- all it needs is an optional encoding parameter.
-- Greg
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40microsoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140614/153a6a39/attachment.html>
- Previous message: [Python-Dev] Criticism of execfile() removal in Python3
- Next message: [Python-Dev] Criticism of execfile() removal in Python3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]