Walter Dörwald wrote:
The stateful decoder has a little problem: At least three bytes
have to be available from the stream until the StreamReader
decides whether these bytes are a BOM that has to be skipped.
This means that if the file only contains "ab", the user will
never see these two character
Walter Dörwald wrote:
There's been a problem with your request
exceptions.UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
position 92: ordinal not in range(128)
That should be fixed now, please try again.
Please report further errors you find to sf.net/projects/pypi.
Suggestions/RFEs c
Walter Dörwald wrote:
The register command in 2.4 (and current CVS) simply does a
value = str(value)
in post_to_server() so the encoded bytes sent depend on the
default encoding. Would it be sufficient to change this to
value = unicode(value).encode("utf-8")
Indeed. I think this can go into 2
Walter Dörwald wrote:
So is this change wanted? useful? implementable with reasonable effort? Or
just not worth it?
I think it is just not worth it. This means I won't attempt to implement
it. I think I defined originally the __module__ attribute for classes to
support better pickling (and defined
Walter Dörwald wrote:
So can I have one setup.py for both Python 2.4 and Python 2.5 that does the
correct thing when creating a Windows installer for
Python 2.4 (I've used Unicode strings for that until now) and using the upload
command with Python CVS (which seems to require a
byte string now)?
Walter Dörwald wrote:
I'm not sure if this is the right approach.
I think the approach is right, but the implementation is wrong.
The encoding I specify in
setup.py should be independent of the encoding used between distutils
and PyPI to communicate on the wire. I.e. the author (and maintainer)
