On Wed, Jul 16, 2003 at 06:44:21AM +0200, Martin v. L=F6wis wrote: > Christian Reis <kiko@async.com.br> writes: >=20 > > I've spoken briefly to Guido about this, and he's suggested python-de= v > > as the place to ask. I'd really like to know how bad "too much would > > break" is, and if anybody contemplates a way to fix it [*]. I'd volun= teer to > > work on the change, of course.=20 >=20 > I added the special-casing of LC_NUMERIC when I found Python can't > parse floating point literals in Python source code anymore, in such a > locale (de_DE uses the same convention). This is triggered by atof(3) > changing its meaning, inside compile.c:parsenumber. Is there a good reason to prefer atof() over strtod(), if we already have a locale-safe version of the latter? Take care, -- Christian Reis, Senior Engineer, Async Open Source, Brazil. http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
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