Arch Linux User Repository

Build and tests are fine for me on clean chroot.

@gesh For me it still doesn't work. The only working release is the first one. I'm not understand why you update it if it works in clean chroot?

This is an example in failed test:

--------------------------------------------------- Captured stdout call ---------------------------------------------------
============================= test session starts ==============================
platform linux -- Python 3.14.3, pytest-8.4.2, pluggy-1.6.0
rootdir: /tmp/pytest-of-medaminezghal/pytest-2/test_recording_configure_hook0
collected 1 item
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/_pytest/main.py", line 289, in wrap_session
INTERNALERROR>     session.exitstatus = doit(config, session) or 0
INTERNALERROR>                          ~~~~^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/_pytest/main.py", line 342, in _main
INTERNALERROR>     config.hook.pytest_collection(session=session)
INTERNALERROR>     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_hooks.py", line 512, in __call__
INTERNALERROR>     return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
INTERNALERROR>            ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 120, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
INTERNALERROR>            ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 475, in traced_hookexec
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>            ~~~~~~~~~~~~~~~~~~^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_result.py", line 103, in get_result
INTERNALERROR>     raise exc.with_traceback(tb)
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_result.py", line 62, in from_call
INTERNALERROR>     result = func()
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 472, in <lambda>
INTERNALERROR>     lambda: oldcall(hook_name, hook_impls, caller_kwargs, firstresult)
INTERNALERROR>             ~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 167, in _multicall
INTERNALERROR>     raise exception
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
INTERNALERROR>     teardown.throw(exception)
INTERNALERROR>     ~~~~~~~~~~~~~~^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/_pytest/logging.py", line 788, in pytest_collection
INTERNALERROR>     return (yield)
INTERNALERROR>             ^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
INTERNALERROR>     teardown.throw(exception)
INTERNALERROR>     ~~~~~~~~~~~~~~^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/_pytest/warnings.py", line 99, in pytest_collection
INTERNALERROR>     return (yield)
INTERNALERROR>             ^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
INTERNALERROR>     teardown.throw(exception)
INTERNALERROR>     ~~~~~~~~~~~~~~^^^^^^^^^^^
INTERNALERROR>   File "/usr/lib/python3.14/site-packages/_pytest/config/__i

@medaminezhgal Your PKGBUILD changes so much, it is difficult to see what exactly it's doing. I'm going through it, but don't have much time today.

Also, I don't see what it's fixing? The package builds fine in a clean chroot.

Also also, it does not follow the guidelines, as it violates RFC0020 which recommends package sources avoid PyPI since sdists aren't always suitable for packaging and stable URLs aren't always visible. It also doesn't install the package to a venv for testing (which is needed for the tests to succeed).

Also, the choice of --disable-warnings is odd to me -- why would you hide this information from users?

However, this did show me I forgot to remove python-coverage from the checkdepends, thanks for that. Other than that, I'm not merging any of the changes in, though.

@gesh This is a PKGBUILD file that is compatible with Python package Guidelines and working fine:

# Maintainer: Gesh <gesh@gesh.uni.cx>
# Contributor: Achmad Fathoni<fathoni.id(at)gmail.com>

_name=pytest-recording
pkgname=python-$_name
pkgver=0.13.4
pkgrel=3
pkgdesc='A pytest plugin powered by VCR.py to record and replay HTTP traffic.'
arch=('any')
url="https://github.com/kiwicom/pytest-recording"
license=('MIT')
depends=('python' 'python-vcrpy' 'python-pytest')
makedepends=('python-hatchling' 'python-build' 'python-installer' 'python-wheel')
checkdepends=('python-pytest-httpbin' 'python-pytest-mock' 'python-requests' 'python-werkzeug')
optdepends=('python-pycurl: Block pycurl-based network connections')
source=("https://files.pythonhosted.org/packages/source/${_name::1}/$_name/${_name//-/_}-$pkgver.tar.gz")
sha256sums=('568d64b2a85992eec4ae0a419c855d5fd96782c5fb016784d86f18053792768c')

build() {
  cd "$srcdir"/${_name//-/_}-$pkgver
  python -m build --wheel --no-isolation
}

check() {
  local pytest_options=(
    -vv
    --disable-warnings
  )
  cd "$srcdir"/${_name//-/_}-$pkgver
  PYTHONPATH=$PWD/src pytest "${pytest_options[@]}" tests
}

package() {
  cd "$srcdir"/${_name//-/_}-$pkgver
  python -m installer --destdir="$pkgdir" dist/*.whl
  install -Dm644 LICENSE -t "$pkgdir/usr/share/licenses/$pkgname"
}

The first package release was working fine for me but the new one doesn't work anymore.

Odd, I can reproduce the issue but can't figure out why it ever worked. Thanks for flagging and fixing this!

Hello, following my previous comment, here is a patch to the PKGBUILD that fix the issue with the bad directory name:

diff --git i/PKGBUILD w/PKGBUILD
index a28c724..46bb587 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -24,18 +24,18 @@ checkdepends=(
     python-requests
     python-werkzeug
 )
-source=("$pkgname-$pkgver::${_url}/archive/refs/tags/v${pkgver}.tar.gz")
+source=("$pkgname-$pkgver.tar.gz::${_url}/archive/refs/tags/v${pkgver}.tar.gz")
 sha256sums=('979a7849e758ed1d6ba17056533c75ac901f30a420d8229342bf4c5043cb86fb')

 build() {
-    cd "$pkgname-$pkgver"
+    cd "${pkgname/python-/}-$pkgver"
     python -m build --wheel --no-isolation

     python -m installer --destdir=tmp_install dist/*.whl
 }

 check() {
-    cd "$pkgname-$pkgver"
+    cd "${pkgname/python-/}-$pkgver"

     local _site_packages
     _site_packages="$(python -c 'import site; print(site.getsitepackages()[0])')"
@@ -47,7 +47,7 @@ check() {
 }

 package() {
-    cd "$pkgname-$pkgver"
+    cd "${pkgname/python-/}-$pkgver"
     python -m installer --destdir="$pkgdir" dist/*.whl
     install -Dm644 LICENSE -t "$pkgdir/usr/share/licenses/$pkgname"
 }

Hello,

When trying to update this package as of today, I got the following error:

  -> Extracting python-pytest-recording-0.13.2 with bsdtar
==> Sources are ready.
==> Making package: python-pytest-recording 0.13.2-6 (Fri 11 Apr 2025 09:13:37 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/home/drac/.cache/yay/python-pytest-recording/PKGBUILD: line 31: cd: python-pytest-recording-0.13.2: Not a directory
==> ERROR: A failure occurred in build().

@medaminezghal I saw it, but thanks for keeping me posted on it. I've updated prepare() to use the final PR you posted for clarity's sake.

@gesh In the next version there is no need to use the prepare function as the problem is fixed from the PR in the GitHub and it has merged today.

Right - I ended up using your sed solution instead of just patching using your PR as I initially intended - upstream has diverged too far since the last release for the patch to cover all the invocations it needs to.