Path: csiph.com!news.mixmin.net!weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod From: James Addison Newsgroups: linux.debian.maint.python Subject: Re: Matplotlib 3.10.0 for trixie? Date: Sat, 12 Apr 2025 15:10:01 +0200 Message-ID: References: X-Original-To: Nilesh Patra X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Apr 12 13:06:11 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.1 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .jp-hosting. - helo: .mail-ej1-x62d.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Forwarded-Encrypted: i=1; AJvYcCW7s1SELSNs44yXDlGCANrBbMElZglUGCrWfDt+p73Dl+pRRfw8o++Do/ajU9tF60QGYgBBzNe3RtsWkkaX@lists.debian.org X-Gm-Message-State: AOJu0YzmYDTzSRqkjWYmJhGMdss/92GHXPYYyXz2vxXJdakSmPFoAWBe HhLywUnFib3pNjE/YWVweWttfW8Es0EeomMMYbg0568ZRkZDYsw4lHAhzwhNkDZNhxjw+r1Tyek +O0r71ilDd1fFRAVob4NO7+BSlQN+sxANVj+f X-Gm-Gg: ASbGncuGtdyM+O9q+aHn3DNqrRlVjGYNdpekChSUlh3RG1n83DAstORVshNxmZ80/v6 5BTfF0xOJ25cfNRaV9ANKAwqQB24tEIligGeYTW8HjfqSNK8WKFg7O/J8uppdazJv7e69F8z0c5 mrF40RfkcjmRVoMhK2dyFn8Q== X-Google-SMTP-Source: AGHT+IHnm5KHe3fsbw0fBCQOFUUVmy7FviMQTsMCnKkKAOiV0IFjTascsLFy7Uu6rIBgIWosorexA0Grjcw0XcmWTgs= X-Received: by 2002:a17:907:3d0c:b0:aca:c699:8d3a with SMTP id a640c23a62f3a-acad34c34a8mr533466066b.22.1744462110642; Sat, 12 Apr 2025 05:48:30 -0700 (PDT) MIME-Version: 1.0 X-Gm-Features: ATxdqUFH_yUrjRC82aZ1IOZNVQhgkWJa1hf6_xHT0RqV0CHsVuj1BolH5TyxLo8 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/22971 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CALDQ5Ny_oBD+ePM=XEW7qJC4u6moQvtBHjPfo9ZU9ntbrRE89w@mail.gmail.com Approved: robomod@news.nic.it Lines: 41 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Alexandre Detiste , debian-python@lists.debian.org X-Original-Date: Sat, 12 Apr 2025 12:48:20 +0000 X-Original-Message-ID: X-Original-References: <29b74bd1-2181-4bf3-81a6-003cab5df87f@debian.org> <84b7b620-6f18-4f54-a13d-bb38ae0ee839@fsfe.org> <73CF4D23-2E84-40DB-9EBE-D74E9585ED00@riseup.net> <6d4e26d0-5fbd-4893-9264-1fb255111404@riseup.net> <418B4F61-1ADC-49EE-9946-9D31623456CD@riseup.net> <332450BD-FF2D-4BCC-A313-90809A0DB09D@riseup.net> Xref: csiph.com linux.debian.maint.python:16850 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 files see [1]. However, this was not > handled properly via maintscripts so that'd mean over-writing user-modified /etc/matplotlibrc. Ah; what is the problem related to the maintscripts? The /etc/matplotlibrc file is considered a config file by apt/dpkg (it is not removed unless a purge is requested), so I was hoping that shipping a default/unmodified matplotlibrc in an updated 3.10 upload (as Alex suggests in his thread) would provide a useful additional conflict-resolution step for anyone who has modified theirs. > The backend detection logic is now better and I feel we should get rid of the "yield '/etc/matplotlibrc'" in > [1] and also stop shipping the conffile both and add in a rm_conffile to remove previously > installed /etc/matplotlibrc. I don't have a strong opinion about this part, although when in sysadmin mode, I do tend to go looking in /etc first to find config files. On the other hand, we wouldn't be the first package to read config files from elsewhere on the filesystem - pipewire springs to mind as another case where default config files are located under /usr/share, for example. > Probably also a d/NEWS to inform the sysadmin that this no longer works. It does not make > sense to me for a python lib to have a conffile. +1 to a NEWS entry. I'm not so sure about removing the conffile entirely yet, though. I think it may be safer to treat it as a feature deprecation, allowing time for feedback about any use cases that seem to require it and/or for users to migrate to alternatives. Regards, James