On 25.08.2012 19:36, Stefan Krah wrote: > "Martin v. L?wis" <martin at v.loewis.de> wrote: >> - each CRT has its own locale. This may be an issue if an extension >> module relies on the CRT locale for data formatting; I just think >> this is unlikely to occur in practice (and when it does, it's easily >> notable). > > _decimal's 'n' format specifier actually relies on the CRT locale. The > functions in question are in libmpdec, so on Windows it is not possible > to compile a static libmpdec and build the module from that. Building a static libmpdec should work fine, as long as it links with the CRT DLL. Most likely, the problem was that the project file in question would also link with the static CRT, which then causes the problem. But I see the point that extension modules may rely on the locale set by the Python script. Regards, Martin
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