Hey Eric,
Thanks for your reply.
1) The whole point of checks/test cases are to make sure that the package works correctly. If the whole point is to do --nocheck defeats the purpose of running testcases in the first place.
2) The whole point of  asking to add a git flag is so that there can be a pypi version in the case this fails or for someone like me who would use it as a part of starlette and would need the stable release of pypi.
3)The first comment about failing assertion is at 2019-12-20 11:13  hence I assumed that you were unavailable.
Thanks and Regards

Tony Benoy
I'd recommend you encrypt mails sent to me. You can find my pgp key at https://tinyurl.com/y9v2mrt9
On Mar 1 2020, at 9:19 am, Eric Berquist <pentavalentcarbon@gmail.com> wrote:
1. Tests are not failing, and if they were, you could use `--nocheck`.
2. Just because the package source comes from a release tarball put on GitHub doesn't make it a `-git` version.
3. Just because the maintainer doesn't respond after 5 days doesn't mean they're unavailable.

On Tue, Feb 25, 2020 at 2:09 PM <notify@aur.archlinux.org> wrote:
tonybenoy [1] filed an orphan request for python-pydantic [2]:

The package is broken as tests is failing. Also the package is a git
version and not from pypi. Also I have a package python-fastapi which
is dependent on pydantic. I dont think the maintainer is avaliable.

[1] https://aur.archlinux.org/account/tonybenoy/
[2] https://aur.archlinux.org/pkgbase/python-pydantic/