Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString

References	<CANc-5Uwi0vXJV+ifF98V5W4aci+JZ35BP39g7bONpKmsR2asAw@mail.gmail.com> <CAPTjJmoS3=GXP-Zvjpenm-dcoHA6k5oqmV+Rh6NOmeVr=9RQXQ@mail.gmail.com> <CANc-5Uz9ZVsTCTYbsxLsUXuRjttr6_Date4z88AVN9_ypdUkjg@mail.gmail.com> <CAPTjJmoDJcS5LEUO29mxY8gv2fkCoEZ0YXC7OkKLLVuDcFESJg@mail.gmail.com>
Date	2014-02-03 13:52 -0600
Subject	Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString
From	Skip Montanaro <skip@pobox.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.6360.1391457145.18130.python-list@python.org> (permalink)

Show all headers | View raw

> Good luck getting this fixed. Even if you do manage to get your vendor
> to start shipping wide builds, you're going to have people screaming
> about how much more RAM their processes use now :( Never mind that
> other Linux builds of Python have done the same thing for years.

Our vendor hasn't been all that responsive about other things, so I'm
not too worried about the screams from users. Besides, essentially
everything we do that matters here is plain old ASCII. Many of our C++
libraries don't grok Unicode, so there's not much chance a wide
version of Python from our vendor would cause much problem.

Thanks,

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString Skip Montanaro <skip@pobox.com> - 2014-02-03 13:52 -0600

csiph-web