> pickle doesn't have the INF=>1.0 bug: > >>>> import pickle >>>> pickle.loads(pickle.dumps(1e10000)) > ... > ValueError: invalid literal for float(): 1.#INF > >>>> import cPickle >>>> cPickle.loads(cPickle.dumps(1e10000)) > ... > ValueError: could not convert string to float > >>>> import marshal >>>> marshal.loads(marshal.dumps(1e10000)) > 1.0 should I check in a fix for this? the code in PyFloat_FromString contains lots of trickery to deal with more or less broken literals, and more or less broken C libraries. unfortunately, and unlike most other functions with similar names, PyFloat_FromString takes a Python object, not a char pointer. would it be a good idea to add a variant that takes a char*? if so, should PyFloat_FromString use the new function, or are we avoiding that kind of refactoring for speed reasons these days? any opinions? </F>
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