Message189869
| Author |
neologix |
| Recipients |
giampaolo.rodola, neologix, pitrou, python-dev |
| Date |
2013年05月23日.17:05:11 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAH_1eM2Lws5Tv51vdQ08E+T_wgEurhu5m0W+_FEnEYWU_4zU8g@mail.gmail.com> |
| In-reply-to |
<1369132880.2545.0.camel@fsol> |
| Content |
> Shouldn't the surrogateescape error handler (PEP 383) prevent this?
Yes, it shoud (I just read PEP 383, I told you I didn't know anything
about encoding :-).
So basically, for the test failure, the issue is simply that the
platform's default encoding can't encode character '\xff'.
Should I simply remove the offending character from this test address?
Also, let's say I wanted to test that it can be passed and returned
properly, so I add '0円xff' to the adress passed to testBytesName:
s.bind(b"\x00python\x00test\xff")
How should I check the string returned by getsockname()?
self.assertEquals(s.getsockname(), ???) |
|