Changes between Initial Version and Version 2 of Ticket #11774


Ignore:
Timestamp:
May 17, 2007, 1:29:02 PM (17 years ago)
Author:
mww@…
Comment:

If this does not break compatibility in some way, I have no objections to add this to the default build options.

Are there any problems that might occur? (besides people using "clever tricks" that include provoking ValueError...)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11774

    • Property Cc mww@… jann@… added
    • Property Status changed from new to assigned
    • Property Owner changed from macports-dev@… to mww@…

  • Ticket #11774 – Description

    initial v2  
    1 Since version 2.2, it has been possible to compile Python with the option --enable-unicode=ucs4, enabling Python Unicode strings to contain characters beyond the Basic Multilingual Plane (e.g. {{{unichr(65535+1)}}} would no longer result in a {{{ValueError}}}). Without that specific option, Python defaults to using the rather obsolete UCS-2 (resulting in a "narrow build").
     1''''''''''''Since version 2.2, it has been possible to compile Python with the option --enable-unicode=ucs4, enabling Python Unicode strings to contain characters beyond the Basic Multilingual Plane (e.g. {{{unichr(65535+1)}}} would no longer result in a {{{ValueError}}}). Without that specific option, Python defaults to using the rather obsolete UCS-2 (resulting in a "narrow build").
    22
    33This can be seen by issuing the following commands in the interactive interpreter: