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 pyth
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.
I also dound that you need to remove the sys.path modifications from the
conf.py.
this can cause some troubles during the build.
Cheers.
Fred
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 extraneo
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 repl
I think that the real problem with the current build is that the conf.py file
change the sys.path.
this is why we see this syntax eror.
sphinx pick the wrong path.
I can not work on this now..., I am not in fron of a Debian box nor have
access to one todays...
Cheers
Fred
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 now, we need to understand why lintian complain about python module at
the wrong place before uploa
Hello, here a diff between the python3.6 and python3.7 modules once updated
via 2to3.
r:/tmp$ diff core*
174c174
< for (variance, tag) in zip(variances, tags))
---
> for (variance, tag) in list(zip(variances, tags)))
181c181
< for (coords, value) in zip(trans
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 (normal,
Hello,
I am keeping me busy packaging the Orange machine learning library that
seems nice (https://orange.biolab.si/#Orange-Features). Now, the test
routines demand a matplotlib.pyplot module that is not in version 2 that
we feature. Version 3 is the current stable release.
Now, I am tempted
On Mon, 2018-10-15 at 22:44 +0200, Steffen Möller wrote:
> Hello,
>
> I am keeping me busy packaging the Orange machine learning library
> that
> seems nice (https://orange.biolab.si/#Orange-Features). Now, the
> test
> routines demand a matplotlib.pyplot module that is not in version 2
> that
On Tue, Oct 16, 2018 at 07:30:55AM +0100, ghisv...@gmail.com wrote:
> > Any opinions from your sides?
>
> How is that going to work without creating package conflicts?
>
> I suppose the main module is still named "matplotlib" not
> "matplotlib3" in version 3 onwards? So using python3-matplotlib3
On Tue, 2018-10-16 at 08:46 +0200, Andreas Tille wrote:
> On Tue, Oct 16, 2018 at 07:30:55AM +0100, ghisv...@gmail.com wrote:
> > > Any opinions from your sides?
> >
> > How is that going to work without creating package conflicts?
> >
> > I suppose the main module is still named "matplotlib" no
12 matches
Mail list logo
