Package Details: python-schema 0.6.6-2

Git Clone URL: https://aur.archlinux.org/python-schema.git (read-only)
Package Base: python-schema
Description: Python module to validate and convert data structures.
Upstream URL: https://github.com/keleshev/schema
Licenses: MIT
Submitter: flying-sheep
Maintainer: flying-sheep (Felixoid)
Last Packager: flying-sheep
Votes: 4
Popularity: 0.722656
First Submitted: 2012-10-23 19:04
Last Updated: 2017-12-28 15:09

Dependencies (4)

Sources (1)

Latest Comments

flying-sheep commented on 2017-12-28 16:46

there’s no reason for a build step in a pure python package.

a compiled one, sure, but if setup.py install does little more than copying files, why bother?

Felixoid commented on 2017-12-28 16:15

But build_${package_name} doesn't work:

==> Starting prepare()...
==> Starting check()...
………
Ran 0 tests in 0.000s

OK
==> Entering fakeroot environment...
==> Starting package_python2-schema()...
running install
running build
running build_py

So, is it possible to build packages separately?

You could check it with python-acme-git package

Eschwartz commented on 2017-12-28 15:02

BTW please use the following for github sources, to prevent problems when using a shared $SRCDEST with other packages that also use $pkgver.tar.gz with the same pkgver:

source=("$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz")

And you should also use a build() function that runs $python setup.py build -- similar to running make in build, before running make check/install in the check()/package() functions.

flying-sheep commented on 2017-12-28 14:49

OK, it is done!

Eschwartz commented on 2017-12-28 13:27

flying-sheep,

There is no such thing as a non-global makedepends, in part because there is no way to build only one component of a split package.

Felixoid commented on 2017-12-28 13:20

or, maybe, could you make me co-maintainer?

Felixoid commented on 2017-12-28 13:18

The silence was so long... =)

Sorry, I have not enabled notifications here and remembered about this package just now.

Here diff between PKGBUILDs https://pastebin.com/RW8CedaR

And there is ready PKGBUILD https://pastebin.com/9v2Z7cFM

I'll send request for remove python2-schema right now

flying-sheep commented on 2017-03-07 13:39

yes, sure! sorry for the long delay. i’m ready when you are, you just have to file a deletion request for your package.

maybe you can also help. i have:

package_python2-schema() {
makedepends=(python2-setuptools python2-pytest)
depends=(python2)

}

but in the .SRCINFO, only the depends appears. I don’t want to have a global makedepends array, as people should be able to install the python 3 version without installing python2-setuptools.

Felixoid commented on 2017-02-07 18:33

Hi!
I adopted python2-schema just hour ago and try to make one source for both python*-schema. But now I see also separated python-schema.

But PKGBUILD ready and it is a pity to throw out.

Maybe you want to merge it to this package and then I drop python2-schema?

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python2-schema

flying-sheep commented on 2016-11-16 08:39

hi, i updated it, thanks for your help.

for the future: i think the best way to download python packages is via files.pythonhosted.org, which has the same URL API as pypi.python.org had.

files on github don’t necessarily match the real package versions on pypi/files.pythonhosted.org, so those are the canonical package files.

All comments