Daniel Stutzbach wrote: > Likewise, a FILE * isn't safe to pass around, unless I can guarantee > that the application really is one big happy family compiled against the > same version of the C library. Given that, it seems to me that it's a mistake for Python to provide any APIs that take a FILE* directly in the first place. Maybe PyObject_Print should be deprecated in favour of something that takes a Python I/O object instead. -- Greg
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