> 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
On Tue, Feb 4, 2014 at 5:59 AM, Skip Montanaro wrote:
> On Mon, Feb 3, 2014 at 12:27 PM, Chris Angelico wrote:
>> On Tue, Feb 4, 2014 at 4:41 AM, Skip Montanaro wrote:
>>> I think this means that at configure time, OpenSuSE and our vendor
>>> chose different values for the --enable-unicode optio
On Mon, Feb 3, 2014 at 12:27 PM, Chris Angelico wrote:
> On Tue, Feb 4, 2014 at 4:41 AM, Skip Montanaro wrote:
>> I think this means that at configure time, OpenSuSE and our vendor
>> chose different values for the --enable-unicode option. Is that
>> correct?
>
> Easy enough to check. Fire up eac
On Tue, Feb 4, 2014 at 4:41 AM, Skip Montanaro wrote:
> I think this means that at configure time, OpenSuSE and our vendor
> chose different values for the --enable-unicode option. Is that
> correct?
Easy enough to check. Fire up each Python and have a look at what
sys.maxunicode is - if it's 655
traceback:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/vtk/__init__.py", line 41, in
from vtkCommonPython import *
ImportError: /usr/lib64/libvtkPythonCore.so.5.10: undefined symbol:
_PyUnicodeUCS4_AsDefaultEncodedString
I t
