Home/ Questions/Q 6830957
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T22:40:47+00:00

On 64-bit Debian Linux 6: Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48) [GCC 4.4.5]

  • 0

On 64-bit Debian Linux 6:

Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.maxint
9223372036854775807
>>> sys.maxunicode
1114111

On 64-bit Windows 7:

Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.maxint
2147483647
>>> sys.maxunicode
65535

Both Operating Systems are 64-bit. They have sys.maxunicode, according to wikipedia There are 1,114,112 code points in unicode. Is sys.maxunicode on Windows wrong?

And why do they have different sys.maxint?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know what your question is, but sys.maxunicode is not wrong on Windows.

    See the docs:

    sys.maxunicode

    An integer giving the largest supported code point for a Unicode character. The value of this depends on the configuration option that
    specifies whether Unicode characters are stored as UCS-2 or UCS-4.

    Python on Windows uses UCS-2, so the largest code point is 65,535 (and the supplementary-plane characters are encoded by 2*16 bit “surrogate pairs”).

    About sys.maxint, this shows at which point Python 2 switches from “simple integers” (123) to “long integers” (12345678987654321L). Obviously Python for Windows uses 32 bits, and Python for Linux uses 64 bits. Since Python 3, this has become irrelevant because the simple and long integer types have been merged into one. Therefore, sys.maxint is gone from Python 3.

    • 0