Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1a.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.006 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'python,': 0.02; 'configure': 0.05; 'pep': 0.09; 'skip:/ 10': 0.09; 'cc:addr :python-list': 0.11; 'python': 0.11; 'anyway': 0.14; 'check.': 0.16; 'concern,': 0.16; 'from:addr:pobox.com': 0.16; 'from:addr:skip': 0.16; 'porting': 0.16; 'sorts': 0.16; 'stuff.': 0.16; 'term.': 0.16; 'sender:addr:gmail.com': 0.17; 'wrote:': 0.18; 'thanks.': 0.20; 'feb': 0.22; 'cc:addr:python.org': 0.22; 'certainly': 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; 'that.': 0.31; 'option.': 0.31; 'another': 0.32; 'agree': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; '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; 'easy': 0.60; 'name': 0.63; 'our': 0.64; 'different': 0.65; 'great': 0.65; 'fire': 0.65; 'to:addr:gmail.com': 0.65; 'blame.': 0.84; 'certain,': 0.84; 'internally.': 0.84; 'subject:skip:_ 30': 0.84 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OEGYGI4V4/BYJpINxekj/PKjoIlTWcaZtAw4QJRAtvQ=; b=Qmbg+iO3fqcrWcAqinEQlksJM4utrWoWIv3SN3PjcqtjcoGt47J0x2LYJ2tZhLNuyc uC4QP+bFVvNjh7P1byHpoyZ27mhY12NEBUZPH1rpPmABbopYjOUrzRAP+CS1zSD9pfhO ayawfW73Tzf58A1+VMj99r9EDjpZr3BGRsA99NATx/rveejUBQ5Xh6rjRcWvWz6Se0wg vP9BB7u59YJ99kSUZM8SLBWyOJJuPfSv22oNJJfcJa92ly78ohya95/bZAo7XH+fexR/ TSZilprfgYKGRqQLKCPpi1qygGyOL2L+hqSShmGAL5THf2S8JpAVaKQDpYLFx5FwU/lo Ufww== MIME-Version: 1.0 X-Received: by 10.221.26.10 with SMTP id rk10mr29991870vcb.0.1391453982456; Mon, 03 Feb 2014 10:59:42 -0800 (PST) Sender: skip.montanaro@gmail.com In-Reply-To: References: Date: Mon, 3 Feb 2014 12:59:42 -0600 X-Google-Sender-Auth: 3_Pqq227XaudWhQaXFu6H70p8Yo Subject: Re: undefined symbol: _PyUnicodeUCS4_AsDefaultEncodedString From: Skip Montanaro To: Chris Angelico Content-Type: text/plain; charset=UTF-8 Cc: Python 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: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1391453990 news.xs4all.nl 2855 [2001:888:2000:d::a6]:35477 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:65364 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. > 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. Skip