Package Details: python-pykwalify 1.7.0-1

Git Clone URL: (read-only)
Package Base: python-pykwalify
Description: Python lib/cli for JSON/YAML schema validation
Upstream URL:
Licenses: MIT
Provides: pykwalify
Submitter: Stunkymonkey
Maintainer: Stunkymonkey
Last Packager: Stunkymonkey
Votes: 5
Popularity: 0.027292
First Submitted: 2017-08-22 20:12
Last Updated: 2018-12-11 23:20

Latest Comments

Stunkymonkey commented on 2018-08-23 10:09

@polyzen it is done

polyzen commented on 2018-08-21 02:57

Please add --skip-build to the install as it's already built by then. Also you might as well use just package() {.

devopsdeluxe commented on 2018-08-10 16:28

Patch for v1.6.1:

function patch_pykwalify() {
  if ! curl -L -o v1.6.1.patch; then
    return 1
  git apply v1.6.1.patch
  git diff

Stunkymonkey commented on 2018-04-29 19:21

There is zero reason for these tests to be running on end user machines

The Main reason is, when someone is not installing updates any more and still uses packages from aur.

axthra00304 commented on 2018-04-26 19:53

@Stunkymonkey Splitting it into python 2 and python 3 is a good start, but my point was that the checks need to be run at build time, meaning they happen before deploying. You can also run the tests as part of a release CI.

There is zero reason for these tests to be running on end user machines, because all that happens if they fail is that it breaks that person's install flow, even if the failure is some weird thing like the documentation built wrong. It also adds a whole bunch of unnecessary dependencies that are not needed to actually run the package.

Stunkymonkey commented on 2017-11-20 23:15

I have not written pykwalify myself. So I definitely want to make sure the package works. Therefore I will not disable the checks.

having the python2 deps is not great. so i splited the package into two separate ones. I hope this satisfies your needs :-)

axthra00304 commented on 2017-11-20 17:44

I think this should not be running the tests as part of the build process. It's creating a bunch of runtime dependencies on test code, for one thing.

The other thing is that python-pykwalify should not depend on a bunch of python 2 packages. I think that's also a consequence of the fact that it's running the full test suite at install time. This is not common among python packages.

Can you drop all the check and python 2 dependencies from this package?