On Fri, Jul 25, 2003 at 03:13:46AM -0400, Tim Peters wrote: > [martin at v.loewis.de] > > While the feature is desirable, I don't like the patch it all. It > > copies the relevant code of Gnome glib, and I > > a) doubt it works on all systems we care about, and > > b) is too much code for us to maintain, and > > c) introduces yet another license (although the true authors > > of that code would be willing to relicense it) > > OTOH, even assuming "C" locale, Python's float<->string story varies across > platforms anyway, due to different C libraries treating things like > infinities, NaNs, signed zeroes, and the number of digits displayed in an > exponent differently. This also has bad consequences, although one-platform > programmers usually don't notice them (Windows programmers do more than > most, because MS's C library can't read back the strings it produces for > NaNs and infinities -- which Python also produces and can't read back in > then). > > So it's not that the patch is too much code to maintain, it's not enough > code to do the whole job <0.9 wink>. My question, now, is if we would we be able to cobble something even more magical into the g_ascii_* functions that makes Python more robust to these changes (over time)? 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