> Bill Janssen schrieb: > >> Hmm, perhaps the ctypes documentation could use a more prominent warning > >> that it may not be available on some Unix platforms (HP-UX, AIX, IRIX), > >> and that it may require the use of GCC rather than the vendor compiler > >> on others (Solaris). > >> > >> At the moment, I suspect some projects may be switching to using it > >> without realising the implications for cross-platform portability. > > > > I think it's a tad more problematic. As other modules, both in and > > out of the standard library, move to use ctypes, it implies that > > *Python* isn't supported on those combinations. Personally, that's > > fine with me (as long as there's a workaround for Solaris!), but I > > think that Ulrich is right in saying this should be more prominent. > > I won't object if anyone adds this notice to the Python docs, > so please go ahead. A table of platforms (on the wiki?) where ctypes > builds/works or does not may also be helpful. What happens on those platforms where ctypes doesn't work? Does the module fail to import, either because it isn't present, or because it can't load the libffi library? Or does it fail silently in some way? Bill
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