[Python-Dev] -U option?

Martin v. Loewis martin@loewis.home.cs.tu-berlin.de
Wed, 6 Jun 2001 22:34:30 +0200


[Tim]
> Anyone understand -U?  Like, shoulQd it work, why is it there if it
> doesn't and isn't expected to, and are there docs for it beyond the
> "python -h" blurb?

I'm not surprised it doesn't work, but I think it could be made
working in many cases. I also think it would be worthwhile making that
work; in the process, many places will be taught to accept Unicode
strings which currently don't.

[Barry]
> Nope, except that /for me/ an installed Python 2.1 seems to start up
> just fine with -U.
[...]

Sure, but it won't work

martin@mira:~ > python -U                                               [22:29]
Python 2.2a0 (#336, May 29 2001, 09:28:57)
[GCC 2.95.2 19991024 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import string
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named string
>>> import sys
>>> sys.path
['', u'/usr/src/omni/lib/python', u'/usr/src/omni/lib/i586_linux_2.0_glibc2.1',
u'/usr/ilu-2.0b1/lib', u'/home/martin', u'/usr/local/lib/python2.2', u'/usr/local/lib/python2.2/plat-linux2', u'/usr/local/lib/python2.2/lib-tk', u'/usr/local/lib/python2.2/lib-dynload', u'/usr/local/lib/python2.2/site-packages', u'/usr/local/lib/site-python']

The main problem (also with the SF bug report) seems to be that
Unicode objects in sys.path are not accepted, but I think they should.

Regards,
Martin