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 <blah>
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