Le jeudi 07 avril 2022 à 10:49 +0100, Julian Gilbey a écrit :
> > > At present, the Debian python3-qtpy package depends on 17
> > > python3-pyqt5* packages, which seems to be at odds with the
> > > intention
> > > of the package to be Qt-package agnostic. It seems that it would
> > > be
> > > clea
Hi Julian,
Le mercredi 06 avril 2022 à 22:01 +0100, Julian Gilbey a écrit :
> I've just uploaded the latest version of QtPy (source: python-qtpy,
> binary: python3-qtpy). But I'm disturbed by the dependency list.
Thank you for taking care of it.
> QtPy is a wrapper for PyQt5, PyQt6, PySide2 and
Le samedi 28 mars 2020 à 11:22 +0100, Christian Kastner a écrit :
> The Python 2 removal page [1] states that existing python-$foo-doc
> packages should not be renamed to python3-$foo-doc.
>
> But what about new packages? I have a package in NEW that provides
> python3-tpot, but should the doc pac
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,
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 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
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
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
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
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
10 matches
Mail list logo
