Tim Peters wrote: > > http://sf.net/tracker/?func=detail&atid=105470&aid=430269&group_id=5470 > python -U breaks import with 2.1 > > Anyone understand -U? Like, should 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? The -U option is there to be able to test drive Python into the Unicode age. As you and many others have noted, there's still a long way to go... > Last mention of it I found in c.l.py was > > """ > Date: Tue, 06 Feb 2001 16:09:46 +0100 > From: "M.-A. Lemburg" <mal@lemburg.com> > Subject: Re: [Python-Dev] Pre-PEP: Python Character Model > > ... > Well, with -U on, Python will compile "" into u"", > ... > last I tried, Python didn't even start up :-( > ... > """ > > An earlier msg (08 Sep 2000) said: > > """ > Note that many thing fail when Python is started with -U... that > switch was introduced to be able to get an idea of which parts of > the standard fail to work in a mixed string/Unicode environment. > """ > > If this is just an internal development switch, python -h probably shouldn't > advertise it. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4