[issue8654] Improve ABI compatibility between UCS2 and UCS4 builds
Daniel Stutzbach
report at bugs.python.org
Sat May 8 18:19:29 CEST 2010
Daniel Stutzbach <daniel at stutzbachenterprises.com> added the comment:
On Sat, May 8, 2010 at 11:02 AM, Martin v. Löwis <report at bugs.python.org> wrote:
> Did you mean to include the hunk from msg105295 as part of the patch?
> If so, wouldn't that defeat the whole point of the patch?
My intention is to offer two compilation modes to extension authors:
1) A mode that defines Py_UNICODE, PyUnicodeObject, and various unsafe
functions and macros.
2) A mode that does not define them.
In mode #1, importing the module should fail if the Unicode settings
are mismatched. I had meant to include the hunk from msg105295 only
in mode #1.
Right now I favor your idea of generating a runtime error when loading
the module, instead of a linker error. Assuming we go that route, the
hunk from msg105295 will not be used at all.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8654>
_______________________________________
More information about the Python-bugs-list
mailing list