A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-May/111314.html below:

[Python-Dev] [Python-checkins] cpython: _PyImport_LoadDynamicModule() encodes the module name explicitly to ASCII

[Python-Dev] [Python-checkins] cpython: _PyImport_LoadDynamicModule() encodes the module name explicitly to ASCII [Python-Dev] [Python-checkins] cpython: _PyImport_LoadDynamicModule() encodes the module name explicitly to ASCIIAntoine Pitrou solipsis at pitrou.net
Tue May 10 02:06:03 CEST 2011
On Mon, 09 May 2011 16:11:15 +0200
Victor Stinner <victor.stinner at haypocalc.com> wrote:
> Le lundi 09 mai 2011 à 09:00 -0400, Jim Jewett a écrit :
> > Are you asserting that all foreign modules (or at least all handled by
> > this) are in C, as opposed to C++ or even Java or Fortran?  (And the C
> > won't change?)
> 
> C and C++ identifiers are restricted to ASCII. I don't know for Fortran
> or Java.

Why is it important, though?
What matters is not what C/C++ can produce, but what a shared library
can export. So the question is: are shared libraries limited to ASCII
symbols?

Regards

Antoine.


More information about the Python-Dev mailing list

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