Package Details: python-future 1.0.0-4

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: 6
Popularity: 3.38
First Submitted: 2024-12-22 16:15 (UTC)
Last Updated: 2025-01-02 15:16 (UTC)

Dependencies (8)

Sources (1)

Pinned Comments

micwoj92 commented on 2025-01-02 21:47 (UTC)

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.

Latest Comments

1 2 Next › Last »

Aliee commented on 2025-01-16 11:10 (UTC)

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'

fam007e commented on 2025-01-14 21:02 (UTC)

@frankspace the pkg is installed via your fix.

micwoj92 commented on 2025-01-13 17:22 (UTC)

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

frankspace commented on 2025-01-13 12:23 (UTC)

@fam007e, please test the fix I posted below.

fam007e commented on 2025-01-13 12:06 (UTC) (edited on 2025-01-13 12:06 (UTC) by fam007e)

Is this no longer going to work for me as this error is popping up for a few days now:

removing build/bdist.linux-x86_64/wheel
Successfully built future-1.0.0-py3-none-any.whl
==> Starting check()...
==================================================================================== test session starts ====================================================================================
platform linux -- Python 3.13.1, pytest-8.3.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase(PosixPath('/home/fam007e/.cache/yay/python-future/src/future-1.0.0/.hypothesis/examples'))
rootdir: /home/fam007e/.cache/yay/python-future/src/future-1.0.0
configfile: pytest.ini
plugins: anyio-4.7.0, hypothesis-6.123.13, xdist-3.6.1, typeguard-4.4.1
collected 99 items / 1 error                                                                                                                                                                

========================================================================================== ERRORS ===========================================================================================
___________________________________________________________________ ERROR collecting tests/test_past/test_translation.py ____________________________________________________________________
ImportError while importing test module '/home/fam007e/.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'
===================================================================================== warnings summary ======================================================================================
build/lib/future/backports/test/support.py:1945
  /home/fam007e/.cache/yay/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.61s ================================================================================
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: python-future-exit status 4

frankspace commented on 2025-01-12 17:06 (UTC) (edited on 2025-01-12 17:07 (UTC) by frankspace)

The python-fissix package in the official repos provides a drop-in substitute for lib2to3. I am not clever enough to know whether the various SyntaxWarning warnings are important, but this will both compile and pass checks by adding python-fissix as a dependency and adding the following to the PKGBUILD:

prepare() {
  cd "$srcdir"/future-$pkgver
  find . -type f -name "*.*" -exec sed -i 's|lib2to3|fissix|g' {} +
}

I'm not disputing that projects shouldn't be using this anymore, but at least one that I use seems to be abandoned, so getting them to do so may be infeasible. Using fissix seems to work in the meantime.

carlosal1015 commented on 2025-01-07 15:07 (UTC) 

==> Starting check()...
============================= 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.23s ==========================
==> ERROR: A failure occurred in check().
    Aborting...

elatllat commented on 2025-01-04 20:27 (UTC)

I don't know why "python-future" is installed by default, but it's now breaking system upgrades so I removed it.

yay -R python-future

I assume pacman etc will work fine with just "python" currently at v3.13.1-1

micwoj92 commented on 2025-01-02 21:47 (UTC)

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.

1 2 Next › Last »