Package Details: python-zstd 1.5.5.1-1

Git Clone URL: https://aur.archlinux.org/python-zstd.git (read-only, click to copy)
Package Base: python-zstd
Description: ZSTD Bindings for Python
Upstream URL: https://github.com/sergey-dryabzhinsky/python-zstd
Licenses: BSD
Submitter: BigfootACA
Maintainer: maksverver
Last Packager: maksverver
Votes: 2
Popularity: 0.000000
First Submitted: 2021-03-24 14:55 (UTC)
Last Updated: 2024-02-03 20:14 (UTC)

Latest Comments

1 2 Next › Last »

gdi commented on 2024-10-12 00:38 (UTC)

There was actually a stealth update a while back to 1.5.6.0. It's under tags, now releases. https://github.com/sergey-dryabzhinsky/python-zstd/releases/tag/v1.5.6.0

Sven commented on 2023-10-05 19:05 (UTC)

1.5.5.1 is out

Dulbi commented on 2023-04-27 08:36 (UTC)

Zstd 1.5.5 is out could you please update your package ?

BigfootACA commented on 2022-09-19 05:42 (UTC)

@Dulbi sorry for later, this package was updated and removed python2

Dulbi commented on 2022-07-01 15:47 (UTC)

Could you please update the package and remove the python2 part ?

carsme commented on 2022-01-03 15:54 (UTC)

If you'd split the package (or deprecate the Python 2 version completely) you could have a PKGBUILD as simple as this:

pkgname=python-zstd
pkgver=1.5.1.0
pkgrel=3
pkgdesc="ZSTD Bindings for Python"
arch=('any')
url="https://github.com/sergey-dryabzhinsky/$pkgname"
license=('BSD')
dependes=(
  'zstd'
  'python'
)
makedepends=('python-setuptools')
checkdepends=('python-pytest')

source=("$pkgname-$pkgver.tar.gz::$url/archive/refs/tags/v$pkgver.tar.gz")
sha256sums=('be48d50dbedd136c88804cb2ee3ee6ead9e54748659664fab1e4c4d8d9886da7')

build() {
  cd "$pkgname-$pkgver"

  python setup.py build --external
}

check() {
  cd "$pkgname-$pkgver"

  python -m pytest
}

package() {
  cd "$pkgname-$pkgver"

  export PYTHONHASHSEED=0
  python setup.py install --root="$pkgdir" --optimize=1 --skip-build
  install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
}

This would use Arch's zstd instead of the one packaged with the Python package (and git repo). This would come with some pros and cons but I think this is the most proper way of packaging for a rolling release distro.

BigfootACA commented on 2022-01-03 15:08 (UTC)

@carsme i will remove python2 testing

Dulbi commented on 2022-01-03 10:44 (UTC)

I would also suggest splitting the package into 2: one for python3 and one for python2. Please also update to 1.5.1

nicoulaj commented on 2022-01-03 10:38 (UTC)

+1, can you please split this package ?

carsme commented on 2022-01-02 12:21 (UTC)

The check stage depends on the broken package python2-pytest which in turn makes this package broken.

I suggest to either remove the Python 2 testing from the check stage or to split the Python 2 build to a completely separate package.

I could help you with this if you'd make me co-maintainer.

1 2 Next › Last »