Ben Finney writes:
> Is there an open bug tracker issue with more information?
Answer: http://bugs.python.org/issue2562>. Apparently the issue
is resolved http://bugs.python.org/msg72385> for Python 2.6. I
will need to wait for my distribution to catch up before I can know
whether it's resolved.
>>> Meanwhile, the 'register' command accepts Unicode, but is broken in
>>> handling it. […]
>>>
>>> Unfortunately, this isn't fixable until there's a new 2.5.x release.
>>> For previous Python versions, both register and write_pkg_info()
>>> accepted 8-bit strings and passed them on as-is, so the
Ben Finney writes:
> "Phillip J. Eby" writes:
>
> > Meanwhile, the 'register' command accepts Unicode, but is broken in
> > handling it. […]
> >
> > Unfortunately, this isn't fixable until there's a new 2.5.x release.
> > For previous Python versions, both register and write_pkg_info()
> > acc
On Fri, Apr 3, 2009 at 2:25 AM, Ben Finney wrote:
> "Phillip J. Eby" writes:
>
>> However, there's currently no standard, as far as I know, for what
>> encoding the PKG-INFO file should use.
>
> Who would define such a standard?
PEP 376 where we can explain that all files in egg-info should be i
"Phillip J. Eby" writes:
> However, there's currently no standard, as far as I know, for what
> encoding the PKG-INFO file should use.
Who would define such a standard? My vote goes for “default is UTF-8”.
> Meanwhile, the 'register' command accepts Unicode, but is broken in
> handling it. […]
