"Fredrik Lundh" <fredrik@effbot.org> writes:
> > Feels to me like there's a bug in the string literal processing that
> > makes *any* string literal containing \N{...} fail during code
> > generation.
>
> umm. can anyone explain how this can happen:
>
> python ../lib/test/regrtest.py test_ucn
> test_ucn
> 1 test OK.
This will run the .pyc if present?
> python ../lib/test/test_ucn.py
> UnicodeError: Unicode-Escape decoding error: Invalid Unicode Character Name
This won't?
Note: no traceback -> (in effect, if not design) compile time error.
> how can a test that works under regrtest.py fail when
> it's run separately? what am I missing here?
Well, this is just my guess.
Cheers,
M.
--
Well, you pretty much need Microsoft stuff to get misbehaviours bad
enough to actually tear the time-space continuum. Luckily for you,
MS Internet Explorer is available for Solaris.
-- Calle Dybedahl, alt.sysadmin.recovery
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