allow Unicode Command-Line options #310
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a couple of unicode-related bugs from the command-line
Of particular note is that (in config/loader.py)
argparse.parse_args
will now always get a list ofunicode
objects, and neverstr
s.There is also a fix in
InteractiveShell._safe_exec_file
, whereexecfile
(at least in 2.6.1) does not encode with the filesystemencoding, but rather the defaultencoding, so a unicode string will raise a UnicodeEncodeError.Things that should now work that did not before: