Search Criteria
Package Details: python-pytest-recording 0.13.2-4
Package Actions
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.71 |
First Submitted: | 2022-03-22 09:59 (UTC) |
Last Updated: | 2025-04-04 14:21 (UTC) |
Dependencies (12)
- python (python37AUR, python311AUR, python310AUR)
- python-pytest
- python-vcrpy (python-vcrpy-gitAUR)
- python-build (make)
- python-hatchling (python-hatchling-gitAUR) (make)
- python-installer (make)
- python-coverage (check)
- python-pytest-httpbin (check)
- python-pytest-mock (check)
- python-requests (check)
- python-werkzeug (check)
- python-pycurl (optional) – Block pycurl-based network connections
Required by (8)
- python-habanero (check)
- python-llm-openrouter (check)
- python-logfire (check)
- python-logfire-api (check)
- python-pydantic-ai (check)
- python-pydantic-ai-examples (check)
- python-pydantic-ai-slim (check)
- python-pydantic-graph (check)
Latest Comments
1 2 Next › Last »
gesh commented on 2025-04-04 15:15 (UTC)
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.medaminezghal commented on 2025-04-04 13:36 (UTC)
@gesh I've already done a pull requests in the GitHub
gesh commented on 2025-04-04 13:01 (UTC)
... I don't know if I invoked
makepkg
incorrectly before, but I'm seeing the failure now. It's surprising, I'll pull in your PR if I can't find the root problem.Thanks for reporting this!
medaminezghal commented on 2025-04-03 19:23 (UTC)
@gesh use makepkg -sf (with installed pretty plugin) and it will fail
gesh commented on 2025-03-30 08:54 (UTC)
@medaminezghal Can't reproduce your test failure, even on a system with python-pytest-pretty installed. Please check if
pkgctl build -c
on your system still fails.medaminezghal commented on 2025-03-18 08:11 (UTC)
@gesh you can add this prepare function to make the test run:
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 thepycurl
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.
1 2 Next › Last »