Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python Subject: Re: Salvaging pylibtiff to Debian Python team or removing it from Debian? Date: Tue, 25 Oct 2016 09:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 25 07:07:55 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.211 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, RP_MATCHES_RCVD=-0.311] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/14299 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20161025070725.GA3618@an3as.eu Approved: robomod@news.nic.it Lines: 49 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 25 Oct 2016 09:07:25 +0200 X-Original-Message-ID: <20161025070725.GA3618@an3as.eu> X-Original-References: <20161021073624.GA22048@an3as.eu> <20161022054437.jfeex3xiuzy4bj6o@gnuservers.com.ar> Xref: csiph.com linux.debian.maint.python:8955 Uploaded with the fixes below as Maintainer Debian QA Group On Sat, Oct 22, 2016 at 07:44:37AM +0200, Maximiliano Curia wrote: > ¡Hola Andreas! > > El 2016-10-21 a las 09:36 +0200, Andreas Tille escribió: > >the former maintainer of pylibtiff inside Debian Med team Mathieu > >Malaterre does not care for the package any more and thus I tried my luck > >to salvage it. I have no personal interest in this package nor does it > >have any rdepends. There is no direct connection to the Debian Med topic > >but since there are some users according to popcon[1] it might be worth > >saving. > > I won't be able to work on this in the foreseeable future, but I can > probably help with the mentioned errors. > > > File "/usr/lib/python2.7/dist-packages/libtiff/libtiff_ctypes.py", line > >36 print 'You should add %r to PATH environment variable and reboot.' % > >(os.path.dirname (lib)) > >^ SyntaxError: invalid syntax > > This looks valid, but probably fails if using: > from __future__ import print_function > you can probably fix this by adding the parenthesis needed for the function > invocation: > print('You should add %r to PATH environment variable and reboot.' % (os.path.dirname (lib))) > > > File "/usr/lib/python2.7/dist-packages/libtiff/optparse_gui.py", line 201 > >print(msg, file=sys.stderr) ^ SyntaxError: invalid > >syntax > > This is probably failing because of a missing: > from __future__ import print_function > at the beginning of the file (it needs to be added before any other import). > > In python2 print is a statement that you use as print "Hi", in python3 it's a > function that you use as print("Hi"), using the __future__ snippet you can > use (in python 2.7) print as a function, this is generally a good idea as it > eases the migration to python3 process. > > Happy hacking, > -- > "If you have too many special cases, you are doing it wrong." -- Craig Zarouni > Saludos /\/\ /\ >< `/ -- http://fam-tille.de