Path: csiph.com!1.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: module mailcap to be removed -- how to replace ? Date: Wed, 26 Oct 2022 20:50:01 +0200 Message-ID: References: X-Original-To: Karsten Hilbert X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Oct 26 18:48:23 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.501 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: ACrzQf0pL0XMWjk44XwC5pwb++zMwv2v6++4mMMkMlWMbVwMW2yksM6X /vzU9Z3bkGzCwBHsvsF/v1/9uvilHzQJIcCkk5Y= X-Google-SMTP-Source: AMsMyM64cZ77/fAVU2atR/B6oHTUkef+lLTZFIEbdE/AfxF12dh1ePh2g3RZ2d3mjlnqLaRnZ3waEoiFtYavx+fb/4Q= X-Received: by 2002:a05:6102:dd2:b0:3aa:1ed3:2ad2 with SMTP id e18-20020a0561020dd200b003aa1ed32ad2mr9119894vst.11.1666810078352; Wed, 26 Oct 2022 11:47:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/20409 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXxE5UXwbc=HPfFOJXOEmUda2yzngyEcE7TTDc7ZJsM-tw@mail.gmail.com Approved: robomod@news.nic.it Lines: 22 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Wed, 26 Oct 2022 14:47:31 -0400 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:14557 > Python 3.11 marks "mailcap" for removal in 3.13. The > documentation speaks about "mimetypes" being a replacement, > of sorts. > > However, I can't really see how "mimetypes" helps in > replacing the functionality of "mailcap". > > Put another way: what is the suggested way of replacing that > module in existing code ? The use case is "find the viewer > for any kind of file (mimetype), as long as the system > knows". Given this decision has been made at the upstream python level, you should be asking on their support channel how they plan for current code migration (which is 2 years away). https://www.python.org/about/help/ could be a good start. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi