Martin v. Löwis wrote:
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 t
Martin v. Löwis wrote:
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.
Works perfectly, thanks!
> [...]
Bye,
Walter Dörwald
__
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
Martin v. Löwis wrote:
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 requi
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)?
Martin v. Löwis sagte:
> 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 t
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)
[EMAIL PROTECTED] wrote:
Zitat von Walter Dörwald <[EMAIL PROTECTED]>:
I've uploaded a new package to the new PyPI. Editing this
new packages gives me a unicode error. The URL is
http://www.python.org/pypi?:action=submit_form&name=ll-ansistyle&version=0.6.1
I see that the package is online now, so
> Zitat von Walter Dörwald <[EMAIL PROTECTED]>:
>
>> I've uploaded a new package to the new PyPI. Editing this
>> new packages gives me a unicode error. The URL is
>>
>> http://www.python.org/pypi?:action=submit_form&name=ll-ansistyle&version=0.6.1
>
> I see that the package is online now, so I ass
Zitat von Walter Dörwald <[EMAIL PROTECTED]>:
> I've uploaded a new package to the new PyPI. Editing this
> new packages gives me a unicode error. The URL is
>
> http://www.python.org/pypi?:action=submit_form&name=ll-ansistyle&version=0.6.1
I see that the package is online now, so I assume that
i
11 matches
Mail list logo
