On Tue, Oct 16, 2018 at 07:55:40AM +0100, ghisv...@gmail.com wrote:
> > > I suppose the main module is still named "matplotlib" not
> > > "matplotlib3" in version 3 onwards? So using python3-matplotlib3
> > > would
> > > be a breach of policy.
> >
> > Probably.
>
> Described in Section 2.2 of th
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 n
On Tue, 2018-10-16 at 09:00 +0200, Andreas Tille wrote:
> On Tue, Oct 16, 2018 at 07:55:40AM +0100, ghisv...@gmail.com wrote:
> > > > I suppose the main module is still named "matplotlib" not
> > > > "matplotlib3" in version 3 onwards? So using python3-
> > > > matplotlib3
> > > > would
> > > > be
ghisv...@gmail.com writes:
> Indeed. Note that NumPy has already published plans to become Python 3
> only in the near future, so the deprecation of Python 2 in the
> scientific stack will happen eventually.
>
> I just don't think it should be rushed into the Buster release cycle.
If we really wan
On Tue, 2018-10-16 at 09:38 +0200, Ole Streicher wrote:
> ghisv...@gmail.com writes:
> > Indeed. Note that NumPy has already published plans to become
> > Python 3
> > only in the near future, so the deprecation of Python 2 in the
> > scientific stack will happen eventually.
> >
> > I just don't t
Hi Ghis,
On 16.10.18 08:30, ghisv...@gmail.com wrote:
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.pyplo
On Tue, 2018-10-16 at 10:16 +0200, Steffen Möller wrote:
> Hi Ghis,
>
> On 16.10.18 08:30, ghisv...@gmail.com wrote:
> > 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
> > > seem
Let me ask you this: where is the rush to package this machine learning
library? Could it wait after the Buster release cycle, where we might
be in a more comfortable position to upgrade matplotlib?
The short answer is yes. The almost as short one is "Conda has it
already, use that". The sligh
ghisv...@gmail.com writes:
> Don't get me wrong, I am all in favour for a modern stack, including
> Python 3.
>
> However, upgrading NumPy et al. to their Python 3 only versions,
> introducing new legacy packages for Python 2, and patching the large
> collection of packages relying on the Python 2
On Tue, 2018-10-16 at 10:42 +0200, Steffen Möller wrote:
> > > Let me ask you this: where is the rush to package this machine
> > > learning
> > > library? Could it wait after the Buster release cycle, where we
> > > might
> > > be in a more comfortable position to upgrade matplotlib?
> > The short
On Tue, 2018-10-16 at 11:45 +0300, Arto Jantunen wrote:
> ghisv...@gmail.com writes:
> > Don't get me wrong, I am all in favour for a modern stack,
> > including
> > Python 3.
> >
> > However, upgrading NumPy et al. to their Python 3 only versions,
> > introducing new legacy packages for Python 2,
ghisv...@gmail.com writes:
> On Tue, 2018-10-16 at 11:45 +0300, Arto Jantunen wrote:
>> ghisv...@gmail.com writes:
>> > Don't get me wrong, I am all in favour for a modern stack,
>> > including
>> > Python 3.
>> >
>> > However, upgrading NumPy et al. to their Python 3 only versions,
>> > introduc
On Tue, 16 Oct 2018 at 22:11, wrote:
> On Tue, 2018-10-16 at 11:45 +0300, Arto Jantunen wrote:
> > ghisv...@gmail.com writes:
> > > Don't get me wrong, I am all in favour for a modern stack,
> > > including
> > > Python 3.
> > >
> > > However, upgrading NumPy et al. to their Python 3 only version
Quoting Steffen Möller :
Now, I am tempted to create a package matplotlib3 instead of forcing
everyone to update from this long term release (see
https://matplotlib.org/).
Any opinions from your sides?
I wonder, whether it's easier to wait for buster and then create an
orange backport? I'm
> Now, I am tempted to create a package matplotlib3 instead of forcing
please dont. the right course of action is:
- fork src:matplotlib2 from src:matplotlib to only provide the python2 package
- update src:matplotlib to upstream 3.x to provide only py3k modules
(and since there was also a discus
15 matches
Mail list logo
