Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

non unicode data not correctly handled in Python 3 #734

Closed
fbenkstein opened this issue Jan 21, 2016 · 3 comments
Closed

non unicode data not correctly handled in Python 3 #734

fbenkstein opened this issue Jan 21, 2016 · 3 comments
Labels

Comments

@fbenkstein
Copy link
Collaborator

Filenames and command line arguments can include (non-unicode) binary data on most operating systems. This is more difficult to handle on Python 3 because these are generally expressed as the str type. I've created pull request #733 with a test case that highlights the issue but do not have a solution at this point.

@giampaolo
Copy link
Owner

Fixed in #733

@giampaolo
Copy link
Owner

...also on OSX (818ef90 and ba83883).

@giampaolo
Copy link
Owner

It turns out this problem exists on pretty much all platforms and it affects name(), exe(), cmdline(), cwd() and open_files() methods on Python 3 only.

giampaolo added a commit that referenced this issue Jan 23, 2016
giampaolo added a commit that referenced this issue Jan 23, 2016
@giampaolo giampaolo reopened this Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants