Arch Linux User Repository

I'd be glad to do that, but this doesn't actually provide or replace python-terminaltables. In order for this to be used, code importing terminaltables must be changed to terminaltables3. Unfortunately, this is not a complete drop-in replacement for python-terminaltables, and it's my understanding that this is when provides/replaces would be used.

Hi, can you add provides/replaces python-terminaltables since this package supersedes it?

FYI: I have created python-terminaltables3, since the name of the module/project itself has been changed. Per the upstream developer, any instances of "terminaltables" in code should be changed to "terminaltables3", which I suspect will happen in dependent projects over time.

I am not familiar at all with AUR, but I think some change is needed to be able to install python-terminaltables.

The repository was moved from https://github.com/matthewdeanmartin/terminaltables to https://github.com/matthewdeanmartin/terminaltables3

And I had to change the build script locally to this:

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Jeff Barfield (noprobelm[at]protonmail[dot]org)

 pkgname=python-terminaltables
-_pyname=terminaltables
+_pyname=terminaltables3
 pkgver=3.1.10
 pkgrel=11
 pkgdesc="Generate simple tables in terminals from a nested list of strings"
@@ -14,7 +14,7 @@ checkdepends=('python-pytest' 'python-colorama' 'python-termcolor' 'python-color
 source=("${_pyname}-${pkgver}.tar.gz::https://github.com/matthewdeanmartin/${_pyname}/archive/v${pkgver}.tar.gz"
         python-3.8.patch
         poetry-core.patch)
-sha512sums=('84fa403cee4206b6b19de0206d89535bd2965a0796e1890dd9b0a9c6593c5f41d0d24b88ee9db426067c777712a4e810d67d4d0246496239a7a96b53a24e8174'
+sha512sums=('e68aaebbc65c46e636c980d3d187f965008d0b2badbd4dfad0da9c3eef06883c9b01853b8a0adc43f1c71863bcf249f1327d4334451bafcaf241a1effaa3144f'
             '9a33ef51cbd2854bf9acc247e2d966332229446158e7dae9cad25e03335eb9689d50b0a22234285aa56c707e6e93c12f950299efcfbe7e42ed527216090592f2'
           '4497c99e4bf54709944aff2296460728259750b6b81db549d0b06f31cd853106124c264e51f30a4b3da4e74ea662baa6f39ec48f1d58b59701fbe3e43469a543')

I hope it helps others.

This depends or make depends on python-poetry.

==> Starting build()...
* Building wheel...

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/pyproject_hooks/_impl.py", line 321, in _call_hook
    raise BackendUnavailable(data.get('traceback', ''))
pyproject_hooks._impl.BackendUnavailable: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_process.py", line 77, in _build_backend
    obj = import_module(mod_path)
          ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1126, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'poetry.masonry'

ERROR Backend 'poetry.masonry.api' is not available.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python-terminaltables-exit status 4

When I installed python-poetry, the above error disappeared.

Apply this patch to build while upstream #3 remains unresolved. With that patch saved as poetry-core.patch, simply add patch -Np1 < ../poetry-core.patch to prepare().

Hi! I do not have any problems with the current upstream, so there's no immediate request on my end to switch. Thanks for maintaining this.

Thanks for your comment, meanjollies. I forgot to regenerate the .SRCINFO after my last update in May. I just did so.

As for switching the upstream to the newly maintained version -- I recently inherited this package after it was dropped from the community repository and decided to keep using the unmaintained upstream version until I'm able to do a comprehensive review of the differences between the two and/or someone complained about missing or broken functionality. I just haven't had time to do that review yet.

Do you have any problems with the current upstream? If so I would be compelled to expedite the change, but if not I'm going to leave it this way for a while longer. I'm happy to accommodate you if you're having an issue with something specific.