Hi again, I've now stumbled upon the `export PYBUILD_DISABLE=test` some Uploader had commited. This is now deactivated in Git[2]. Any idea how to get this working?
Kind regards Andreas. [2] https://salsa.debian.org/debian/python-uncertainties On Fri, Oct 12, 2018 at 08:19:02AM +0200, Andreas Tille wrote: > Hi, > > I need help with an issue in python-uncertainties[2]. It only occures > with Python 2: > > $ python > Python 2.7.15+ (default, Aug 31 2018, 11:56:52) > [GCC 8.2.0] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from uncertainties import core > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/python2.7/dist-packages/uncertainties/__init__.py", line > 224, in <module> > from .core import * > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in > <module> > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in > <dictcomp> > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} > TypeError: ord() expected a character, but string of length 3 found > >>> > > With Python 3 everything is fine. > > Any idea what might be wrong? > > Please note that I commited a new upstream tarball to Git. It has the > same release version but pypi contains a totally different release > tarball than Github (different file site and different dirs). I was > told that the Github version works "better" but this specific error > occures for both. I'd recommend to use the current HEAD in Git anyway > since that version looks more "sensible" in some way. > > I would also love if someone would check whether dh_auto_test is working > correctly. I somehow see no sign that the test suite is executed - thus > the problem above seems to remain hidden. > > Kind regards and thanks for any help > > Andreas. > > On Thu, Oct 11, 2018 at 01:06:43PM +0200, Andreas Tille wrote: > > Hi, > > > > I'm working on bugs #906381 and #906419 of package lmfit-py which should > > be solved in the latest upstream version. As it is documented in the > > lmfit-py issue tracker[1] this latest version needs python-uncertainties > > >= 3.0 which was prepared by Federico in Git[2]. Since it did not build > > I fixed the build issues and did a team upload (if I understood David > > Paleino correctly team maintenance in DPMT is fine and thus I have set > > the team as maintainer - I hope this is fine with you. Since another > > upload will be needed (see below) I'm fine with reverting this) of the > > upstream source that was injected. > > > > According to lmfit-py upstream[3] there is some issue with the > > uncertainties release and it seems we are now dealing with the wrong > > code. I just want to let you know you about my past upload and that > > I intend to do another upload until that issue[3] is fixed. > > > > Kind regards > > > > Andreas. > > > > PS: I'd consider it sensible to move the Git repository of > > python-uncertainties from debian/ group on Salsa to > > python-team/modules if you agree but before doing so I'd love > > to hear some confirmation that this is OK and that all Uploaders > > are member of DPMT and are able to keep on commiting. > > > > > > [1] https://github.com/lmfit/lmfit-py/issues/502 > > [2] https://salsa.debian.org/debian/python-uncertainties > > [3] https://github.com/lmfit/lmfit-py/issues/502#issuecomment-428638278 > > > > -- > > http://fam-tille.de > > -- > http://fam-tille.de > > -- http://fam-tille.de