Arch Linux User Repository

I don't agree with all the points you made, but I'm not dogmatic about it, so I don't think further arguing is necessary. Thank you for your efforts and happy holidays!

Checks do not make sense, it will fail anyway. If I did not comment it out then there can be lots of comments "doesnt build" where people don't even read/post output. This way it at least builds, I will soon add install hook with message, I first need to check my other packages that failed to build with python 3.13, I hope people will read it.

Python 311 package DOES NOT provide python. Maintainer of that particular package is wrong and stubborn.
If this were to have python<3.13 depends, then here would also be lots of comments looking like "omg what do I do, cant upgrade!"
That would also mean you would need to rebuild python deps for X package with python311 or otherwise your software will not run. I think that current approach is wrong, but it is least wrong, I hope my decision makes slightly more sense now.

@micwoj92 may I also ask why you disabled the checks for this package? They fail correctly when the lib2to3 module is not present. I would suggest re-enabling them and, as I already said, updating the dependency to python<3.13. Anyone who wants to tinker around would have to change the PKGBUILD deliberately, so there's no room for confusion.

@micwoj92 this was not meant to be any kind of advice, but I can see how it came across wrong. I'm fully aware this package is not compatible with Python 3.13, I read the same issue you linked. What I explained was merely a temporary workaround that solved my problem, and not a solution anyone should rely on. I'm sorry for the confusion, I should've made that more clear.

I also want to advise anyone relying on a package that depends on python-future to go talk to the respective upstream maintainers about dropping the dependency, that's what I did. Actually, I suppose a lot of projects could easily limit the dependency to the future part that's only needed when using Python 2.x.

Regarding your consideration of emptying this package, why not just update the dependency to python<3.13? After all, there's Python 3.11 available in the AUR.

@gwuensch this is terrble advice.

This pkg will likely not be compatible with 3.13:
https://github.com/PythonCharmers/python-future/issues/640
https://python-future.org/overview.html#status

$ futurize 
Traceback (most recent call last):
  File "/usr/bin/futurize", line 5, in <module>
    from libfuturize.main import main
  File "/usr/lib/python3.13/site-packages/libfuturize/main.py", line 73, in <module>
    from lib2to3.main import warn, StdoutRefactoringTool
ModuleNotFoundError: No module named 'lib2to3'

$ pasteurize 
Traceback (most recent call last):
  File "/usr/bin/pasteurize", line 5, in <module>
    from libpasteurize.main import main
  File "/usr/lib/python3.13/site-packages/libpasteurize/main.py", line 44, in <module>
    from lib2to3.main import main, warn, StdoutRefactoringTool
ModuleNotFoundError: No module named 'lib2to3'

If you think you need this, please talk with package maintainers for package/upstream to fix for python3.13+ compatibility. There are many dead python packages in aur that can be purged imo.
I consider just adding .install file with a warn/error so more people see or make this package completely empty to not give false premise.

Copying the lib2to3 module from the Python 3.12 release to the new /usr/lib/python3.13/ directory works for now. I was able to build the package that way at least. Haven't tested any further.

Build fails at the check stage, because lib2to3 was removed from python 3.13 (was marked deprecated since 3.9)

============================= test session starts ==============================
platform linux -- Python 3.13.1, pytest-8.3.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /build/python-future/src/future-1.0.0
configfile: pytest.ini
collecting ... collected 99 items / 1 error

==================================== ERRORS ====================================
_____________ ERROR collecting tests/test_past/test_translation.py _____________
ImportError while importing test module '/build/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'
=============================== warnings summary ===============================
build/lib/future/backports/test/support.py:1945
  /build/python-future/src/future-1.0.0/build/lib/future/backports/test/support.py:1945: SyntaxWarning: invalid escape sequence '\d'
    m = re.match("2.6.(\d{1,2})", kernel_version)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
ERROR tests/test_past/test_translation.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
========================= 1 warning, 1 error in 0.16s ==========================