Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: =?UTF-8?B?w4lyaWM=?= Newsgroups: linux.debian.maint.python Subject: Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Date: Fri, 05 Jan 2024 18:00:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 5 16:52:50 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.21 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, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .netwok. - helo: .smtp-1908.mail.infomaniak. - helo-domain: .infomaniak.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Greylist: delayed 562 seconds by postgrey-1.36 at bendel; Fri, 05 Jan 2024 16:52:30 UTC MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Infomaniak-Routing: alpha X-Mailing-List: archive/latest/21343 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a229ffa9-fc19-4623-aad2-830fd39d74d2@netwok.org Approved: robomod@news.nic.it Lines: 24 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 5 Jan 2024 11:42:39 -0500 X-Original-Message-ID: X-Original-References: <761c5e78-397c-4731-84cd-4548f75530e0@goirand.fr> Xref: csiph.com linux.debian.maint.python:15393 Le 04/01/2024 à 11:51, Thomas Goirand a écrit : > On 1/4/24 00:30, Alexandre Detiste wrote: >> The better solution is to remove python3-future altogether. > > I very much agree with this. Most of the time, it's simply patching out > stuff like: > > from __future__ import Not quite: - __future__ imports are used to tell the Python compiler to enable new syntax, and there is a __future__ module in the standard library providing run-time metadata about these syntax features - python3-future is a normal third-party package (https://pypi.org/project/future/) that provides future and past modules to help 2-3 or 3-2 compatibility, and scripts to convert code: these would take more effort to remove than __future__ imports, and should probably be patched upstream (by removing support for Python 2 and older Python 3 versions) Cheers