public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: python wide-unicode problem
Date: Sat, 22 Jan 2011 12:56:35 +0100	[thread overview]
Message-ID: <1295697395.3501.0@numa-i> (raw)
In-Reply-To: <ihcsvv$a57$1@dough.gmane.org>

On 01/21/2011 10:14:33 PM, walt wrote:
> On 01/21/2011 07:48 AM, Helmut Jarausch wrote:
> > On 01/21/2011 04:26:09 PM, walt wrote:
> >> On 01/21/2011 12:13 AM, Helmut Jarausch wrote:
> >>> Hi,
> >>>
> >>> using Python3.1, if I say
> >>> import site
> >>>
> >>> I get
> >>>
> >>>     File "/usr/lib64/python3.1/site.py", line 472, in setencoding
> >>>       sys.setdefaultencoding(encoding) # Needs Python Unicode
> >> build !
> >>> ValueError: Can only set default encoding to utf-8
> >>>
> >>> But
> >>>
> >>> emerge -vp dev-lang/python-3.1.3  shows
> >>> USE="doc gdbm ipv6 ncurses readline sqlite ssl threads tk (wide-
> >>> unicode) xml -build -examples -wininst"
> >>>
> >>> Why is 'wide-unicode' in parentheses?
> >>
> >> Hm.  Try using a different tool, like equery u python.  Note the
> >> warning
> >> about changing that useflag.
> >
> > Thanks, unfortunately I don't understand the output
> > I've got
> > [ Legend : U - final flag setting for installation]
> > [        : I - package is installed with flag     ]
> > [ Colors : set, unset                             ]
> >   * Found these USE flags for dev-lang/python-3.1.3:
> > .....
> >   - + wide-unicode : Enable wide Unicode implementation which uses
> 4-
> > byte
> >                      Unicode characters. Switching of this USE flag
> > changes ABI
> >                      of Python and requires reinstallation of many
> > Python
> >                      modules. (DON'T DISABLE THIS UNLESS YOU KNOW
> WHAT
> > YOU'RE
> >                      DOING)
> >
> > So, I have U- but I+ on wide-unicode
> > What does that mean?
> 
> I just re-emerged python:3.1 as a test, and I see exactly the same 
> but
> I don't get that error.
> 
> For some reason site.py certainly thinks your python3 is built 
> without
> wide-unicode.  Have you tried re-installing python3 just for fun?
> 
> You could try deleting site.pyc and site.pyo as an easy test.
> 

Thanks Walt,
I've noticed that my root account did use an ASCII locale. Now I've 
changed that to the same locale en_US.iso88591 that is used in non-root 
accounts on my machine. With that I rebuild Python3.1.
And now, the error is gone. A bit strange.
I came along this problem when I tried to emerge the new 
package app-portage/smart-live-rebuild
This fails because the author's name contain non-ascii (even non 
latin1) characters. The author (Michał Górny) sent me a patch to 
distutils.eclass and after generating an utf-8 locale
LANG=en_US.utf-8 emerge -v app-portage/smart-live-rebuild
finally succeeded. He says, it's a Python problem.

Have a nice weekend,
Helmut.



      reply	other threads:[~2011-01-22 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  8:13 [gentoo-user] python wide-unicode problem Helmut Jarausch
2011-01-21 15:26 ` [gentoo-user] " walt
2011-01-21 15:48   ` Helmut Jarausch
2011-01-21 21:14     ` walt
2011-01-22 11:56       ` Helmut Jarausch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1295697395.3501.0@numa-i \
    --to=jarausch@igpm.rwth-aachen.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox