Skip to content

Fix #1982 #1983

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

Merged
merged 3 commits into from Oct 1, 2012
Merged

Fix #1982 #1983

merged 3 commits into from Oct 1, 2012

Conversation

ghost
Copy link

@ghost ghost commented Sep 27, 2012

fixes #1982

Had to hemstring another test so the fix will not break the tests, see
first patch in series I think it's the right thing to do.

There was another fix for a similar unicode problem in 703bbba,
there seems to be some Unicode whack-a-mole going on...

I'm willing to try my hand at fixing the unicode issues more seriously,
but that probably involves many changes throughout the codebase,
and some pain until things settle down.

would you consider such a big PR?

y-p added 3 commits September 27, 2012 17:51
Since the codepoints resulting from a decode depend on the encoding,
this test can only be an example of error handling, but the current code
doesn't treat it as as such. so IMHO this is wrong,  it breaks
another fix which I believe does the right thing in this respect,
for another issue. and so It is removed by this patch.
Unicode<-> bytes conversion and coercing should be done at I/O
entry points, not internal code.
internal representations should be unicode objects, not
strings, conversion should be at I/O contact-points only.

Note: this still does not address the problem of pprinting
indices that have a tuple of unicode strings, as a value.
This issue came up before, monkey-patched in f4e3ab6,
but second time around - a more general solution is needed.
@wesm
Copy link
Member

wesm commented Sep 29, 2012

I'm definitely aware of the Unicode whack-a-mole. It's used up a huge amount of development time. Having to deal with different console encodings is also a big pain. I'd be willing to accept a big PR cleaning this up after 0.9 is out; I guess we have a test suite and CI to protect us on Python 2 and Python 3.

@wesm wesm merged commit b482fd5 into pandas-dev:master Oct 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UnicodeEncodeError in index.summary()
1 participant