Path: csiph.com!pasdenom.info!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.python Subject: Re: Feedback wanted for upstream proposal to replace a patch Date: Fri, 24 Oct 2025 16:30:01 +0200 Message-ID: References: X-Original-To: Stan Ulbrych , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 24 14:23:57 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.496 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, KHOP_HELO_FCRDNS=0.4, LDO_WHITELIST=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -2.7 Old-X-Envelope-From: doko@debian.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/23316 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2003b726-aa01-474d-b060-349254d779ad@debian.org Approved: robomod@news.nic.it Lines: 24 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 24 Oct 2025 16:23:37 +0200 X-Original-Message-ID: <2003b726-aa01-474d-b060-349254d779ad@debian.org> X-Original-References: Xref: csiph.com linux.debian.maint.python:17119 On 10/24/25 15:23, Stan Ulbrych wrote: > Hello! > > We have proposed a new mechanism for improving error messages for missing > standard library modules, you can find the proposal at: > https://discuss.python.org/t/improved-errors-for-missing-standard-library-modules/104540 > please > post your feedback there, it would be greatly appreciated. > > This would allow you to replace the current patch ( > https://sources.debian.org/patches/python3.14/3.14.0-2/tkinter-import.diff/) > with a JSON file that is used during the build process. Is this only needed for standard library modules? That could be extended to *all* available modules in a distro, hinting to the installation of the corresponding package. In this case, you could build up a database of module -> package mappings like it is done for the command-not-found command. Instead of having a single json file, maybe have an approach to scan a dir for multiple json files? Matthias