Package Details: python-ass 1.0.3-1

Git Clone URL: https://aur.archlinux.org/python-ass.git (read-only, click to copy)
Package Base: python-ass
Description: A library for parsing and manipulating Advanced SubStation Alpha subtitle files.
Upstream URL: http://github.com/chireiden/python-ass
Licenses: MIT
Submitter: rekman
Maintainer: rekman
Last Packager: rekman
Votes: 0
Popularity: 0.000000
First Submitted: 2022-08-03 22:08 (UTC)
Last Updated: 2025-11-01 11:57 (UTC)

Latest Comments

rekman commented on 2024-05-26 00:05 (UTC)

@jholmer thank you for bringing this to my attention. It is due to an error in the upstream test suite (https://github.com/chireiden/python-ass/pull/23). This manifests with the python 3.11 -> 3.12 upgrade. For now I've added a workaround in prepare().

jholmer commented on 2024-05-22 17:59 (UTC)

Package is currently broken due to test failures during install.

__________ ERROR collecting tests/testass.py _________ ImportError while importing test module '/home/soichiro/.cache/paru/clone/python-ass/src/python-ass-0.5.4/tests/testass.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_ass.py:9: in <module> import ass E ModuleNotFoundError: No module named 'ass'

rekman commented on 2023-12-16 15:52 (UTC)

@a821 Thank you for the feedback. I have updated the PKGBUILD accordingly.

a821 commented on 2023-12-16 11:00 (UTC)

The PKGBUILD has issues and currently does not build in a clean chroot:

  • Please remove the prepare() function because the source is not a git repo.
  • Please add libass to depends. Also add python-pytest and python-pillow to checkdepends.
  • Consider updating the build steps to PEP 517 (see python packaging guidelines in Arch wiki).
  • Minor nitpick: remove the provides as a package provides itself.

Jcuhfehl commented on 2023-06-29 11:53 (UTC)

I'm getting a ModuleNotFoundError: No module named 'ass' error when installing the package. I presume this is because it's trying to run tests on a package that isn't installed yet.