Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #65373 > unrolled thread
| Started by | Skip Montanaro <skip@pobox.com> |
|---|---|
| First post | 2014-02-03 13:52 -0600 |
| Last post | 2014-02-03 13:52 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString Skip Montanaro <skip@pobox.com> - 2014-02-03 13:52 -0600
| From | Skip Montanaro <skip@pobox.com> |
|---|---|
| Date | 2014-02-03 13:52 -0600 |
| Subject | Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString |
| Message-ID | <mailman.6360.1391457145.18130.python-list@python.org> |
> 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 top | Article view | comp.lang.python
csiph-web