Package Details: python-pytest-recording 0.13.3-1

Git Clone URL: https://aur.archlinux.org/python-pytest-recording.git (read-only, click to copy)
Package Base: python-pytest-recording
Description: Pytest plugin to record network interactions with VCR.py
Upstream URL: https://pypi.org/project/pytest_recording
Licenses: MIT
Submitter: AchmadFathoni
Maintainer: gesh
Last Packager: gesh
Votes: 1
Popularity: 0.112971
First Submitted: 2022-03-22 09:59 (UTC)
Last Updated: 2025-04-27 16:38 (UTC)

Latest Comments

« First ‹ Previous 1 2

medaminezghal commented on 2025-03-18 08:11 (UTC)

@gesh you can add this prepare function to make the test run:

prepare(){
    # Disable pretty plugin in pytest
    cd "${srcdir}/${_src_folder}"
    sed -i 's/\(runpytest([^)]*\)/\1, "-p no:pretty"/' tests/test_blocking_network.py
    sed -i 's/\(runpytest([^)]*\)/\1, "-p no:pretty"/' tests/test_plugin.py
    sed -i 's/\(runpytest([^)]*\)/\1, "-p no:pretty"/' tests/test_recording.py
    sed -i 's/\(runpytest([^)]*\)/\1, "-p no:pretty"/' tests/test_replaying.py
    sed -i 's/result = testdir.runpytest(, "-p no:pretty")/result = testdir.runpytest("-p no:pretty")/' tests/test_blocking_network.py
    sed -i 's/result = testdir.runpytest(, "-p no:pretty")/result = testdir.runpytest("-p no:pretty")/' tests/test_plugin.py
    sed -i 's/result = testdir.runpytest(, "-p no:pretty")/result = testdir.runpytest("-p no:pretty")/' tests/test_recording.py
    sed -i 's/result = testdir.runpytest(, "-p no:pretty")/result = testdir.runpytest("-p no:pretty")/' tests/test_replaying.py
}

This make sure that pretty plugin is disbaled for the tests. Note that adding this function won't affect the tests if pretty plugin isn't installed so you can use it in every environment. If you want, try to edit the PKGBUILD file and test it in clean chroot.

gesh commented on 2025-02-23 17:56 (UTC)

https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

tl;dr: install devtools, build using https://man.archlinux.org/man/pkgctl-build.1 (which sets up an isolated installation of Arch with just enough packages installed to build the package. I'm asking for this because it enables distinguishing between the PKGBUILD accidentally picking up a problem in your local configuration and the PKGBUILD not accounting for a legitimate difference of situations between you and me (eg, slow networks))

medaminezghal commented on 2025-02-23 17:00 (UTC)

@gesh what is the meaning of clean chroot? Because it's still fails for me.

gesh commented on 2025-02-23 15:17 (UTC)

It works for me in a clean chroot -- can you check it still fails for you there?

(I will be pushing a new pkgrel anyway, I noticed I forgot to document the pycurl optdepend and to package the license)

medaminezghal commented on 2025-02-22 14:48 (UTC)

@gesh does the check succeed? For me it's failed.

gesh commented on 2024-12-23 15:50 (UTC)

Note: Package needs to be rebuilt for Python 3.13 (a bump to pkgrel suffices)

gesh commented on 2024-09-30 15:58 (UTC) (edited on 2024-09-30 16:23 (UTC) by gesh)

Note -- given that we're not building with the python-setuptools backend, the python-wheel makedep is unnecessary. Indeed, the package is missing the build backend python-hatchling as a makedep.

« First ‹ Previous 1 2