[Python-Dev] PEP 384 status (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue Aug 31 10:51:00 CEST 2010
- Previous message: [Python-Dev] PEP 384 status
- Next message: [Python-Dev] PEP 384 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 31 Aug 2010 11:12:17 +0900 David Cournapeau <cournape at gmail.com> wrote:
> Hmm... that last point is a bit of any issue actually, since it also > flows the other way (changes made via the locale module won't be > visible to any extension modules using a different C runtime). So I > suspect mixing C runtimes is still going to come with the caveat of > potential locale related glitches. As far as IO is concerned, FILE* is just a special case of a more generic issue, though, so maybe this could be a bit reworded. For example, file descriptor cannot be shared between runtimes either.
Er, really? So it means that, for example, a FileIO object couldn't be shared between runtimes either? How about a socket object? Do you want to forbid FileIO and socket objects as part of the API?
Again, I propose that FILE* functions are allowed in the API, but their use discouraged in the docs (with proper explanations from those who know how to word them).
Regards
Antoine.
- Previous message: [Python-Dev] PEP 384 status
- Next message: [Python-Dev] PEP 384 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]