Hi Dmitry,
On Wed, Oct 17, 2018 at 05:22:53PM +0300, Dmitry Shachnev wrote:
> > I need to admit I have not found out how to use it properly and thus I
> > simply removed the module in question manually[1]. I admit I'd prefer a
> > better solution as well and since it seems to happen
Hi Andreas,
On Tue, Oct 16, 2018 at 09:08:43AM +0200, Andreas Tille wrote:
> I can reproduce the wrongly placed / duplicated modules. Its the same
> observation I made with lmfit-py[1]. While lintian recommends the usage
> of dh_python3
>
> I need to admit I have not found out how to use it
Hi Fred,
On Mon, Oct 15, 2018 at 06:51:09PM +, PICCA Frederic-Emmanuel wrote:
> Hello Andreas,
>
> > Patches are welcome (I have no idea what the construct is doing neither
> > how to replace it with something valid).
>
> > Patch welcome as well - preferably as commit to Git.
>
> done but
Picca,
Hi PICCA Frederic-Emmanuel,
> Hello, here a diff between the python3.6 and python3.7 modules
Please use "unified" (ie. diff -u, possibly diff -urNad) over old-style
diffs in future
> < ord(sup): normal for (normal, sup) in TO_SUPERSCRIPT.items()}
> > ord(sup): normal for
Hi,
On Mon, Oct 15, 2018 at 09:40:27AM +, PICCA Frederic-Emmanuel wrote:
> I found in the code a string with a ur''
>
> This is the problematic line.
>
> I do not know if this is a valid string construction.
Patches are welcome (I have no idea what the construct is doing neither
how to
On Mon, Oct 15, 2018 at 09:40:27AM +, PICCA Frederic-Emmanuel wrote:
> I found in the code a string with a ur''
>
> This is the problematic line.
>
> I do not know if this is a valid string construction.
Under Python 2 it is.
Under Python 3 it is not.
u'test' is valid but
On Fri, Oct 12, 2018 at 06:19:00PM +0200, Piotr Ożarowski wrote:
> [PICCA Frederic-Emmanuel, 2018-10-12]
> > to my opinion, the code is modify in place with 2to3.
> > So the code on the source after the configuration is already converted to
> > python3.
> > And during the build process, with
[PICCA Frederic-Emmanuel, 2018-10-12]
> to my opinion, the code is modify in place with 2to3.
> So the code on the source after the configuration is already converted to
> python3.
> And during the build process, with python2 the code is copied as it in the
> .pybuild place for python2
> with
Andreas,
> Before I discuss this with upstream I'd like to share another observation:
> There is some 2to3 magic applied to the source code which has the effect
> that
Assuming it's upstream's 2to3 magic, then I would speak to them. Alas,
I am new to this package too — good luck and I hope I was
Hi again,
On Fri, Oct 12, 2018 at 02:44:26PM +0200, Andreas Tille wrote:
> >
> > > > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line
> > > > 946, in
> > > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
> >
> > Please always provide a minimal
Hi Chris,
On Fri, Oct 12, 2018 at 12:32:18PM +0100, Chris Lamb wrote:
>
> > > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line
> > > 946, in
> > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
>
> Please always provide a minimal testcase,
Andreas,
> > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946,
> > in
> > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
Please always provide a minimal testcase, otherwise people have to do a
lot of work simply to get where you are..
$ cat
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
13 matches
Mail list logo
