Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.022 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'python,': 0.02; 'configure': 0.05; 'feature,': 0.09; 'pep': 0.09; 'skip:/ 10': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; 'anyway': 0.14; 'character.': 0.16; 'check.': 0.16; 'concern,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'porting': 0.16; 'sorts': 0.16; 'stuff.': 0.16; 'term.': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'thanks.': 0.20; 'feb': 0.22; '>>>': 0.22; 'cc:addr:python.org': 0.22; 'certainly': 0.24; 'fixed.': 0.24; 'removed.': 0.24; 'skip': 0.24; 'mon,': 0.24; 'looks': 0.24; 'cc:2**0': 0.24; 'second': 0.26; 'values': 0.27; 'header:In-Reply- To:1': 0.27; 'point': 0.28; 'function': 0.29; 'appear': 0.29; 'chris': 0.29; 'am,': 0.29; 'vendor': 0.30; 'message- id:@mail.gmail.com': 0.30; "i'm": 0.30; 'getting': 0.31; 'that.': 0.31; 'option.': 0.31; 'another': 0.32; 'linux': 0.33; 'says': 0.33; 'could': 0.34; 'agree': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'ram': 0.36; 'done': 0.36; 'doing': 0.36; 'changing': 0.37; 'problems': 0.38; 'skip:- 10': 0.38; 'pm,': 0.38; 'that,': 0.38; 'skip:_ 30': 0.39; 'enough': 0.39; 'either': 0.39; 'according': 0.40; 'how': 0.40; 'even': 0.60; 'easy': 0.60; 'mentioned': 0.61; "you're": 0.61; 'complete': 0.62; 'name': 0.63; 'our': 0.64; 'more': 0.64; 'different': 0.65; 'chance': 0.65; 'great': 0.65; 'fire': 0.65; 'worth': 0.66; 'blame.': 0.84; 'certain,': 0.84; 'extensions.': 0.84; 'internally.': 0.84; 'pain': 0.84; 'subject:skip:_ 30': 0.84; 'to:none': 0.92; 'luck': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=8BBsrmlEQtR9f019dp3vaTtl4WXnDsZRS9zjfYDB794=; b=MwvnXbwDyaPLtH85qpdizuaa4R82kWYk+UdyyJ5IrOGM1J6KX/ej5kwZlQvITR4VmI C6o4UARbMvHOFlTczXlCy5wtohWNg0sYDgtPGgiSKsBK1p+cL9zd+rBzUGPwU+JUdcBh pL/gPEB0Fd+nQ0ln06woIriX5GgAHofWkiwgfD6UFmW8q1xOTfmFZDIGr3RwdFew4x/u SkotBvIVDeuRf+cDPz0K6LTF7Rt60ilKQm8vAqCf4qv4zCDkcENNdX6sftBHYfgIp9j6 4SfusbXqKClqhFRzbYzQ3PiO+7sHuQ5fzEoHezd9kWVBvfeaE61p4HhEjofKIZSslWfE lLUA== MIME-Version: 1.0 X-Received: by 10.66.102.39 with SMTP id fl7mr38609391pab.43.1391454573075; Mon, 03 Feb 2014 11:09:33 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Feb 2014 06:09:33 +1100 Subject: Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString From: Chris Angelico Cc: Python Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 43 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1391454576 news.xs4all.nl 2978 [2001:888:2000:d::a6]:46386 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:65366 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 option. Is that >>> correct? >> >> Easy enough to check. Fire up each Python and have a look at what >> sys.maxunicode is - if it's 65535, you have a buggy-mode Python that >> uses either UCS-2 or UTF-16 internally. > > Thanks. I get 65535 for our vendor-built Python, and 1114111 from > /usr/bin/python. So (no great surprise), it looks like our vendor is > to blame. That could be a problem, if you now need to have a complete backward-incompatible Python replacement. Could be a bit of a pain for all your other extensions. But it's worth doing if you have any chance of ever seeing an astral character. >> But there is another concern, which your second point minorly touches >> on. I'm not certain, but I think the name >> _PyUnicodeUCS4_AsDefaultEncodedString means that VTK was built against >> a wide Python ("UCS4") and calls _PyUnicode_AsDefaultEncodedString. >> According to PEP 393, that function - which had always been internal >> anyway - is completely removed. Porting VTK to Python 3.3+ will mean >> changing that. > > I'm not concerned about that, certainly not in the immediate term. > /usr/bin/python and VTK appear to agree on this stuff. I trust Kitware > and the OpenSuSE people to take care of these sorts of problems if VTK > ever supports Python 3.x. Okay. You mentioned the FSR, which is a 3.3 feature, so I thought I may as well point out what the associated PEP says about that particular function. 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. ChrisA