> /etc/matplotlibrc.
We have another example:
pip reads /etc/pip.conf and it's really useful to document there
what the company proxy is named.
So reverting the old patched /etc/matplotlibrc to upstream
pristine config was a first step in right direction;
I agree it should be removed later.
I
On 12 April 2025 6:18:20 pm IST, James Addison wrote:
>Hi Nilesh, Alex,
>
>Responding to the first point only, at the moment:
>
>On Sat, 12 Apr 2025 at 07:39, Nilesh Patra wrote:
>> [ ... snip ... ]
>> 1. matplotlib has historically shipped /etc/matploblibrc to forc
On Sat, 12 Apr 2025 at 20:37, James Addison wrote:
>
> On Sat, 12 Apr 2025 at 18:18, Alexandre Detiste
> wrote:
> >
> > In a later step we could discard unmodified config files based on a list of
> > md5sum of what shipped in stable release.
> >
> > So only users of default settings would get th
On Sat, 12 Apr 2025 at 18:18, Alexandre Detiste
wrote:
>
> In a later step we could discard unmodified config files based on a list of
> md5sum of what shipped in stable release.
>
> So only users of default settings would get the new default settings.
Ok; and it seems the relevant query term /
:
> Hi Nilesh, Alex,
>
> Responding to the first point only, at the moment:
>
> On Sat, 12 Apr 2025 at 07:39, Nilesh Patra wrote:
> > [ ... snip ... ]
> > 1. matplotlib has historically shipped /etc/matploblibrc to force tkagg
> and patched the code
> > to use
Hi Nilesh, Alex,
Responding to the first point only, at the moment:
On Sat, 12 Apr 2025 at 07:39, Nilesh Patra wrote:
> [ ... snip ... ]
> 1. matplotlib has historically shipped /etc/matploblibrc to force tkagg and
> patched the code
> to use this if there are no user defined rc
ional /etc/matplotlibrc , /etc/git...
to provision system defaults, maybe other do so)
2.
Yes, MPL should be fixed here.
The idea to ask people to remove gedit to work around problem looks weird ;-)
Greetings
Le sam. 12 avr. 2025 à 09:39, Nilesh Patra a écrit :
>
> Hi Alex, James, all,
>
Hi Alex, James, all,
Seems matplotlib migrated to testing now. I was thinking if it makes sense to do
an incremental 3.10.1+dfsg1-3 release.
There are 2 things that bother me that could be fixed in this release:
1. matplotlib has historically shipped /etc/matploblibrc to force tkagg and
Thank you !
Le dim. 30 mars 2025 à 13:32, Nilesh Patra a écrit :
> > python-maggma_0.70.0-3_unstable.log
>
> Failure due to missing dependencies
> (pyproject_hooks._impl.BackendUnavailable: Cannot import
> 'setuptools.build_meta')
+ python3-setuptools easy to fix, only wondering why it didn't
Hi Lucas,
On 30/03/25 1:35 pm, Lucas Nussbaum wrote:
> Sorry for not replying earlier. I see that you uploaded matplotlib 3.10
> to unstable in the meantime. I did a rebuild of unstable two days ago,
> and did not notice anything specific related to matplotlib.
>
> The build fai
hould solve majority of issues.
> >
> >Only five autopkgtest failing and already two packages fixed !
> >
> >Can we ask $someone to rebuild everything from unstable that
> >depends on matplotlib against this new version ?
> >(to see what fails)
>
> Sinc
remaining which hangs
> > on arm64 but works fine on amd64.
> >
> > On a brief look, it does not really look related to matplotlib.
> >
> > It could be great to try it out with current matplotlib on arm64 in debci
> > like environment. If it hangs, we can just
majority of issues.
>>
>> Only five autopkgtest failing and already two packages fixed !
>
> I cleaned up 2 more. Now there is only one mdanalysis remaining which hangs
> on arm64 but works fine on amd64.
>
> On a brief look, it does not really look related to matp
already two packages fixed !
I cleaned up 2 more. Now there is only one mdanalysis remaining which hangs on
arm64 but works fine on amd64.
On a brief look, it does not really look related to matplotlib.
It could be great to try it out with current matplotlib on arm64 in debci like
environment. If
already two packages fixed !
>
>Can we ask $someone to rebuild everything from unstable that
>depends on matplotlib against this new version ?
>(to see what fails)
Since there is no as such ABI for this, which other modules use, so it won't be
a transition per se as far as I understa
ed do
not show up. On that entire page, you
will mostly find packages that are _failing_. It is also not correct (or even
believable) that only 5 packages in the whole archive ever
depend on matplotlib for tests given this is a very popular plotting library.
So that statement is incorrect.
hm
failing and already two packages fixed !
pseudo-excuses shows only 5 packages running tests and of them, all 5 packages
are failing - I'd rephrase this as 100% of the packages that manually declared
python3-matplotlib in Testsuite-Triggers had failing tests.
When I saw the list yesterda
ntire page, you
will mostly find packages that are _failing_. It is also not correct (or
even believable) that only 5 packages in the whole archive ever
depend on matplotlib for tests given this is a very popular plotting
library.
So that statement is incorrect.
hmm, ok, I'm very happy to be
-excuses shows only 5 packages running tests and of them, all 5
packages are failing - I'd rephrase this as 100% of the packages that
manually declared python3-matplotlib in Testsuite-Triggers had failing
tests.
Of course autopkgtest only tests packages that explicitly depend on
python3-matpl
e that
depends on matplotlib against this new version ?
(to see what fails)
I might remember there was a free-service instance available
somewhere but wouldn't mind some hand-holding.
Greetings
Alexandre
On 17 March 2025 3:01:31 am IST, Alexandre Detiste
wrote:
>Hey,
>
>It uses Wayland now ! (or I mean automagically)
In all previous versions, the Tkagg backend was being forced in
/etc/matplotlibrc.
I removed that enforcing in this upload and let matplotlib do the work of
the CI results too.
The list is already much smaller than for the previous version bump.
Thank you
Le dim. 16 mars 2025 à 15:52, Nilesh Patra a écrit :
> Quick update: Uploaded matplotlib 3.10.1 with Jay's patch and a fix
> to not set backend to Tkagg system-wide (in /etc/matplotlib
Quick update: Uploaded matplotlib 3.10.1 with Jay's patch and a fix
to not set backend to Tkagg system-wide (in /etc/matplotlibrc).
I will check the pseudo-excuses on britney in around week. Hopefully, this
upload should solve majority of issues.
Thanks,
Nilesh
Hi James,
On 13 March 2025 4:05:04 am IST, James Addison wrote:
>On Tue, 11 Mar 2025 at 13:15, Nilesh Patra wrote:
>> [ ... snip ... ]
>> @Alexandre or someone else, could you please help w validating the fix or
>> upload a -3
>> to experimental?
>>
>>
On Tue, 11 Mar 2025 at 13:15, Nilesh Patra wrote:
> [ ... snip ... ]
> @Alexandre or someone else, could you please help w validating the fix or
> upload a -3
> to experimental?
>
> [1]
> https://github.com/matplotlib/matplotlib/commit/f45707d9e6111a83d2c741530cbff2b
is does
> not look
> like a packaging error to me but please review!
Jay was very kind to investigate here and supplied w a patch[1] and a PR [2].
Unfortunately, I do not have the environment to repro this reliably, nor have my
yubikey to actually upload this to experimental.
@Alexandre or someon
On 23/02/25 6:03 pm, Nilesh Patra wrote:
>
>
> On 23/02/25 05:19, Alexandre Detiste wrote:
>> There was a cyclic bootstrap relationship between this and ... Pandas (?)
>> in the Numpy transition that was handled swiftly in the Pandas side
>> but I thing we are a now far enough in Numpy transit
On Sun, 23 Feb 2025 at 18:24, James Addison wrote:
> [ ... snip ... ]
> I've built matplotlib 3.10 from experimental (including the no-PFB
> patch from the exp2 upload) successfully and have been able to use
> that to rebuild the astropy-doc package; as a result I think I'
On Sat, 22 Feb 2025 at 23:49, Alexandre Detiste
wrote:
> [ ... snip ... ]
> James : do you want to help ;-) You can merge your own MR if you feel
> confident.
>https://salsa.debian.org/python-team/packages/matplotlib/-/merge_requests/6
Thank you, Alexandre and Nilesh! I think
On 23/02/25 05:19, Alexandre Detiste wrote:
There was a cyclic bootstrap relationship between this and ... Pandas (?)
in the Numpy transition that was handled swiftly in the Pandas side
but I thing we are a now far enough in Numpy transition the reopload
3.8 to unstable with the accumulated fi
Hi Alexandre
But 3.8 does not even build most of the days
Trying rerun the Salsa CI does not help because log is too long and truncated.
The full log from salsaci is available in the artifacts section of the
project on salsa:
https://salsa.debian.org/python-team/packages/matplotlib
Hi all, Hi Alexandre,
There's approximately 2 months of time still for soft freeze. I believe we
have enough time for a matplotlib update (and transition to testing).
Should we go for it? I will try to spend some hours tonight to see how much
work this may be.
Thanks,
Nilesh
On Mon, Jul 22, 2024 at 11:40:23AM +0200, Alexandre Detiste wrote:
> Hi Nilesh,
>
> I joined Astro team and took care of matplotlib rdeps there.
>
> I'm struggling with basemap... I don't understand how
> this multi-package with it's 3 setup.py works.
> It&#x
On Wed, Mar 20, 2024 at 10:32:04AM +0900, ciel wrote:
> Alexandre-san,
>
> Sorry, it seems like I cannot contribute this because (at least) I'm
> pretty not sure if I can transplant this line properly:
>
> ```
> ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
> echo "backend : TkAgg" > ma
ty-ng/debian/rules
> 25 lmfit-py/debian/rules
> 21 logbook/debian/rules
> 28 logilab-constraint/debian/rules
> 35 love/debian/rules
> 21 ltris/debian/rules
> 15 lua-lpeg/debian/rules
> 13 magic-wormhole/debian/rules
>206 matplotlib/debian/rules
>
ook/debian/rules
28 logilab-constraint/debian/rules
35 love/debian/rules
21 ltris/debian/rules
15 lua-lpeg/debian/rules
13 magic-wormhole/debian/rules
206 matplotlib/debian/rules
14 mdp/debian/rules
18 microsoft-authentication-library-for-python/debian/rules
56 minet
: https://github.com/yt-project/cmyt
* License : BSD-3-Clause
Programming Lang: Python
Description : Matplotlib colormaps from the yt project
cmyt integrates with matplotlib in a similar fashion to cmocean or cmasher
It is a new build dependency of the "yt" packa
://github.com/sunpy/mpl-animators
* License : BSD-3-Clause
Programming Lang: Python
Description : An interative animation framework for matplotlib
The mpl_animators package provides a set of classes which allow the easy
construction of interactive matplotlib widget based animations. “Out of
github.com/anntzer/mplcursors
* License : MIT
* Vcs : https://salsa.debian.org/sudip/mplcursors
Section : python
It builds those binary packages:
python3-mplcursors - Interactive data selection cursors for Matplotlib
To access further information about this packa
o a discussion about numpy)
- make src:python-numpy provide only python2 package
- fork src:numpy from src:python-numpy to provide only python3 modules.
since i'm the maintainer of both matplotlib and numpy, i'll take care
of these "transitions"
--
Sandro "morph" Tosi
My
kport? I'm sure, immediately after release, we (= Python
teams) will start to drop Python 2 support anyway. In the mean time
new versions of matplotlib and friends, as well as orange, might be
suitable for experimental, so that your packaging work doesn't need
to wait. Orange looks very inter
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
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, 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 comfor
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
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&
b.org/).
> > >
> > > 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 pyth
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 would
be a breach of policy.
Yes. We would need to freely interpret that
uot;? I never said that personally.
> Holding back normal updates especially for science packages just
> because
> we don't want to use a modern numpy/scipy/matplotlib stack is not
> really
> friendly to our users, which (in science) rely on at least "somehow"
> mo
cycle.
If we really want to then have a Python-2-numpy, why can't there be a
separate Python-2 legacy numpy source package? I do the same for
astropy.
Holding back normal updates especially for science packages just because
we don't want to use a modern numpy/scipy/matplotlib stack is no
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 u
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 pol
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 ma
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&quo
> 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 would
be a breach of policy.
Let me ask you this: where
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 Thursday, 5 July 2018 08:09:50 AEST Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I can confirm this problem in a pbuilder environment. Unfortunately I
> have no idea about the cause of the issue nor how to fix it. Any hint
> from the Debian Python team?
Looks a lot like at least
:
> Package: src:python-matplotlib-venn
> Version: 0.11.5-4
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster with "dpkg-bui
On Fri, Dec 15, 2017 at 05:22:09PM +0200, Juhani Numminen wrote:
>
> In debian/rules, are the arguments to dh_auto_test still needed? The error
> went
> away when I removed said arguments, like so:
>
> override_dh_auto_test:
> xvfb-run --auto-servernum --server-args="-screen 0 1024x768x24"
Andreas Tille kirjoitti 12.12.2017 klo 17:10:
> Hi again,
>
> On Mon, Dec 11, 2017 at 09:27:57AM +0100, Andreas Tille wrote:
>>
>> On Sun, Dec 10, 2017 at 09:05:07PM +0200, Adrian Bunk wrote:
>>> === warnings summary
>>> ===
>>> None
>>> [
Hi again,
On Mon, Dec 11, 2017 at 09:27:57AM +0100, Andreas Tille wrote:
>
> On Sun, Dec 10, 2017 at 09:05:07PM +0200, Adrian Bunk wrote:
> > === warnings summary
> > ===
> > None
> > [pytest] section in setup.cfg files is deprecated, use
tom failed with: exit code=4: cp -a
> README.rst
> /build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build && cd
> /build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build &&
> python2.7 /build/1st/python-matplotlib-venn-0.11.5/setup.py test &
test suite successfully.
Kind regards
Andreas.
On Fri, Feb 05, 2016 at 09:37:32AM +0100, Chris Lamb wrote:
Source: python-matplotlib-venn
Version: 0.11-2
Severity: serious
Dear Maintainer,
python-matplotlib-venn fails to build from source in unstable/amd64:
[..]
running test
runnin
regards
Andreas.
On Fri, Feb 05, 2016 at 09:37:32AM +0100, Chris Lamb wrote:
> Source: python-matplotlib-venn
> Version: 0.11-2
> Severity: serious
>
> Dear Maintainer,
>
> python-matplotlib-venn fails to build from source in unstable/amd64:
>
> [..]
>
>
ld && cd
> > {home_dir}/build && {interpreter} /python-matplotlib-venn-0.11/setup.py
> > test && rm README.rst" --dir .
> > I: pybuild base:170: cp -a README.rst
> > /python-matplotlib-venn-0.11/.pybuild/pythonX.Y_3.4/build && cd
&
-
>
> Date: Mon, 19 Oct 2015 19:05:55 +0100
> From: "Chris West (Faux)"
> To: Debian Bug Tracking System
> Subject: Bug#802354: python-matplotlib-venn: FTBFS: AttributeError: can't set
> attribute
> X-Debian-PR-Message: report 802354
> X-Debian-PR-Pac
king System
Subject: Bug#802354: python-matplotlib-venn: FTBFS: AttributeError: can't set
attribute
X-Debian-PR-Message: report 802354
X-Debian-PR-Package: src:python-matplotlib-venn
X-Debian-PR-Keywords: sid stretch
X-Debian-PR-Source: python-matplotlib-venn
Source: python-matplotlib-venn
Hi,
I'd like to package python-matplotlib-venn since a Debian Med package
depends from this module. I injected the packaging to
svn://anonscm.debian.org/debian-med/trunk/packages/python-mathplotlib-venn/trunk/
Unfortunately I'm running into:
.pybuild/pythonX.Y_2.7/build/matpl
On Sep 04, 2012, at 09:00 AM, Nigel Sedgwick wrote:
>Given the issue with (especially) WX, I think I will stick with Python
>2.7 for the time being.
The only suggestion I'd make is that you write your Python 2 code so that it's
easier to port to Python 3 when all your dependencies are available.
Re: Availability of Numpy, WX, Matplotlib and Scipy under Python3
=
Thanks to Thomas Kluyver and Dmitrijs Ledkovs.
On Mon, 2012-09-03 at 21:27 +0100, Thomas Kluyver wrote:
> Python 3 versions of numpy and scipy are already in whe
On 3 September 2012 21:27, Thomas Kluyver wrote:
> Hi Nigel,
>
> On 3 September 2012 14:57, Nigel Sedgwick wrote:
>> The application makes heavy use of numpy and wx and will soon make heavy
>> use of scipy, matplotlib and various other python libraries that are
>>
Hi Nigel,
On 3 September 2012 14:57, Nigel Sedgwick wrote:
> The application makes heavy use of numpy and wx and will soon make heavy
> use of scipy, matplotlib and various other python libraries that are
> widely used.
Python 3 versions of numpy and scipy are already in wheez
Dear All
Availability of Numpy, WX, Matplotlib and Scipy under Python3
=
I am a user of Debian Squeeze (6.0.5) on an AMD64 computer. I would
like to switch a mainstream development of mine from Python2.6 (or 2.7)
to Python3.1 (or 3.2
Hi Tiziano. Thanks for the report. It looks like this was closed
upstream a month or so ago:
r5977 | mdboom | 2008-08-05 12:32:44 -0700 (Tue, 05 Aug 2008) | 2 lines
Changed paths:
M /trunk/matplotlib/lib/matplotlib/axes3d.py
[ 2033106 ] Wrong exception raised (typo) in axes3d.py
Tiziano
Hello Tiziano,
On Mon, Sep 8, 2008 at 12:07, Tiziano Zito <[EMAIL PROTECTED]> wrote:
> Hi, in the package python-matplotlib I've just hit a typo in
> /usr/share/pyshared/matplotlib/axes3d.py:
>
> raise NotImplmentedError('axes3d is not supported in matplotlib-0.98.
&g
Hi, in the package python-matplotlib I've just hit a typo in
/usr/share/pyshared/matplotlib/axes3d.py:
raise NotImplmentedError('axes3d is not supported in matplotlib-0.98.
You may want to try the 0.91.x maintenance branch')
should read "NotImplementedError" instead of
On Sat, Feb 23, 2008 at 5:08 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> On Sat, Feb 23, 2008 at 4:31 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote:
> > Hi Ondrej et al.,
> >
> >
> > >
> > > Yes, I read that bug. There are more prob
On Sat, Feb 23, 2008 at 4:31 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote:
> Hi Ondrej et al.,
>
>
> >
> > Yes, I read that bug. There are more problems with matplotlib - it is
> > not lintian clean,
> > it still uses Numerics and numarray besides numpy (I
Hi Ondrej et al.,
>
> Yes, I read that bug. There are more problems with matplotlib - it is
> not lintian clean,
> it still uses Numerics and numarray besides numpy (I don't know if
> this is a feature or a bug),
>
I think upstream deprecated Numerics and numarray and
On Sat, Feb 23, 2008 at 1:22 PM, Eike Nicklas <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> On Sat, 23 Feb 2008 13:07:24 +0100 Ondrej Certik wrote:
>
> >
> > currently, matplotlib doesn't install with numpy in sid, when numpy
> > switched to gfortran and
Hi,
On Sat, 23 Feb 2008 13:07:24 +0100 Ondrej Certik wrote:
>
> currently, matplotlib doesn't install with numpy in sid, when numpy
> switched to gfortran and it conflicts with matplotlib.
>
That might also (partly) fix a bug I reassigned to matplotlib:
http://bugs.d
Hi,
currently, matplotlib doesn't install with numpy in sid, when numpy
switched to gfortran and it conflicts with matplotlib.
It seems just a recompile of matplotlib fixes the problem. I imported
matplotlib to DPMT svn:
svn://svn.debian.org/svn/python-modules/packages/matplotlib/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've packaged a new version of python-matplotlib and ipython, you can find my
packages at this address:
deb http://anakonda.altervista.org/debian packages/
deb-src http://anakonda.altervista.org/debian sources/
# apt-get install p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've packaged a new version of python-matplotlib and ipython, you can find my
packages at this address:
deb http://anakonda.altervista.org/debian packages/
deb-src http://anakonda.altervista.org/debian sources/
# apt-get install p
85 matches
Mail list logo
