Package Details: python-future 1.0.0-2

Git Clone URL: https://aur.archlinux.org/python-future.git (read-only, click to copy)
Package Base: python-future
Description: Clean single-source support for Python 3 and 2
Upstream URL: https://python-future.org/
Licenses: MIT
Provides: futurize, pasteurize
Submitter: carsme
Maintainer: micwoj92
Last Packager: micwoj92
Votes: 1
Popularity: 1.00
First Submitted: 2024-12-22 16:15 (UTC)
Last Updated: 2024-12-23 01:21 (UTC)

Dependencies (6)

Required by (211)

Sources (1)

Latest Comments

micwoj92 commented on 2024-12-23 01:21 (UTC)

@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.

gwuensch commented on 2024-12-23 00:11 (UTC) (edited on 2024-12-23 00:11 (UTC) by gwuensch)

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.

n4r3n commented on 2024-12-22 21:42 (UTC)

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