Arch Linux User Repository

Do not post check errors here. Python-future package is not compatible with Python 3.13. If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Thanks, that's similar to what I've been doing. First try to build, check with namcap. If it says that Dependency included, but may not be needed ('python-future') there are big chances that it can just be removed. Not foolproof, but worked for me in >95% cases for this particular issue.

That is not entirely true about __future__. There were 2 additions in 3.x series: https://docs.python.org/3/library/__future__.html#module-contents

Also because of the "nameclash" I've seen few cases like this where import __future__ was added and at the same time needlessly added future to install_requires.

If someone cared then these would have been fixed already.

You're probably right, thanks for the answer. Nonetheless, if anyone still wants to bother checking which packages actually require python-future, I've updated my previous comment with some info on what to look for.

I did, more or less.
For passhole I submited orphan request. But if package was broken for many years, dead upstreams, no aur pkg activity then I submit deletion requests. If someone cared then these would have been fixed already. @dreieck did a great job with sending reminders comments on packages that still required python-future and it was almost a year ago. So people should not act surprised when something is deleted after being broken* for 1 year.

From that round of requests:
Deletion: yandex-tank splatnet2statink python-postpic python-perspective python-pyevmasm python-conda-verify python-conda-build nemesyst-git mavlink ardupilot-copter-sitl
Orphan: rmtoo python-kicadmodtree-git python-gogs-client python-coq-jupyter python-bayesicfitting passhole greatfet-git funky-git

• with broken I mean that this very package fails to build without intervention. Another way to send a "reminder".

Before filing deletion requests, have you checked these packages are actually “irreparably broken” and not just incorrectly packaged? Two packages I was using wrongly specified python-future as a dependency, even though it was never required when using Python 3.x.

I actually just randomly picked a package relying on python-future (passhole), and it's the same thing. I wouldn't be surprised if more packagers (or upstream maintainers!) did the same mistake.

General rule: If a package does not use the past package (which is included with future), it very likely doesn't actually require python-future on Python 3.x. Any __future__ statements which would be needed on Python 2.x are simply ignored by Python 3.x.

Required by 27 now with few deletion requests pending.

No, rather drop/update packages that depend of it 28 left. For python 3.13 this works, but 3.14 it might not.

@micwoj92 if you're still interested in updating this to work, here's a patch I just used locally:

diff --git a/PKGBUILD b/PKGBUILD index 9a65199d..55069fe5 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -11,7 +11,7 @@ pkgdesc="Clean single-source support for Python 3 and 2"  url="https://python-future.org/"  arch=('any')  license=('MIT') -depends=('python') +depends=('python' 'python-fissix')  provides=('futurize' 'pasteurize')  checkdepends=('python-requests' 'python-pytest')  makedepends=('python-build' 'python-installer' 'python-setuptools' 'python-wheel') @@ -40,3 +40,11 @@ package() {    install -D -m644 LICENSE.txt \      "$pkgdir"/usr/share/licenses/$pkgname/LICENSE.txt  } + +prepare() { +  cd "$srcdir"/future-$pkgver +  # Only touch likely text/code files to reduce noisy warnings +  find . -type f \( -name "*.py" -o -name "*.pyi" -o -name "*.txt" -o -name "*.rst" -o -name "*.cfg" \) \ +    -exec sed -i 's|lib2to3|fissix|g' {} + +} 

Leave it here and removing these package on my machine

ImportError while importing test module '/home/ali/.cache/yay/python-future/src/future-1.0.0/tests/test_past/test_translation.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.13/importlib/__init__.py:88: in import_module     return _bootstrap._gcd_import(name[level:], package, level) tests/test_past/test_translation.py:21: in <module>     from past.translation import install_hooks, remove_hooks, common_substring build/lib/past/translation/__init__.py:44: in <module>     from lib2to3.pgen2.parse import ParseError E   ModuleNotFoundError: No module named 'lib2to3' 

@frankspace the pkg is installed via your fix.

Thanks @frankspace, I will check this and push update soon.