Marc-Andre Lemburg <m...@egenix.com> added the comment: Ezio Melotti wrote: > > Ezio Melotti <ezio.melo...@gmail.com> added the comment: > >> For bug fixes, you can put the macros straight into unicodeobject.c, >> but please leave unicodeobject.h untouched - otherwise people will >> mess around with these macros (even if they are private) and users >> will start to wonder about linker errors if they use old patch >> level releases of Python 2.7/3.2. > > OK, so in 2.7/3.2 I'll put them in unicodeobject.c, and in 3.3 I'll move them > in unicodeobject.c. > > Regarding the name, other macros in unicodeobject.c don't have any prefix, so > we can do the same (e.g. IS_SURROGATE) for 2.7/3.2 if that's fine.
Sure. >> Also note that some of these macros change the behavior of Python >> - that's good if it fixes a bug (obviously :-)), but bad if it >> changes areas that are correctly implemented and then suddenly expose >> new behavior. > > After this we can fix #9200 and make narrow builds behave correctly (i.e. > like wide ones) with non-BMP chars (at least in some places). Ok. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10542> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
