Arch Linux

Updated in case of PKGBuild Guidelines

I did create https://aur.archlinux.org/packages/python-keyring/, which works fine now.

Indeed, thanks for reporting.

Although there seems to be a python3 version python-keyring, its build tests are currently failing (see [1]). I cannot validate if [2] works properly and will therefore disown the package so someone with more proficient knowledge can pick it up.

[1] https://travis-ci.org/jaraco/keyring
[2] http://pastebin.com/H7hLW506

error: target not found: python-keyring

sorry, I am not using mercurial in anger anymore... feel free to pick it up.

-s

pkgver=0.4.5

For those who still have problems with a missing ez_setup module, i've made an aur package out of it (http://aur.archlinux.org/packages.php?ID=46515).
Fixed my problems with a python package of mine i was updating.

Ok, thanks :)

It is a stupid question but since mercurial is working with python2, this package (and my tentative to make it exists) is useless, right?

Anyway, after discussing with the author of python-mercurial_keyring, we decided not to change its code, since it would break compatibility with python 2.4 and 2.5 which are still supported by mercurial.

migrated the package to python3

for python2, please use python2-mercurial_keyring.

cheers,
sebastien.

Hi, when you will want to make a python3 version of the module, you will find a patched version here:
http://bitbucket.org/v_noel/mercurial_keyring/downloads (0.4.3)

> Also, notice that you have to depends on python2-distribute
done.

yes it works but maybe not everyone want to use python-distribute :)

Also, notice that you have to depends on python2-distribute, since they updated the package.

it worked for me (I just had to reinstall python-distribute)

Actually, I made a little mistake, I think it would be safer to have setuptools as a makedepends instead of python-distribute.
The last would be a requirement if we were using python 3 :)

Sorry!

updated, thanks.

Here is python2 PKGBUILD:

pkgname=python-mercurial_keyring
pkgver=0.4.2
pkgrel=1
pkgdesc="Mercurial Keyring Extension"
arch=('i686' 'x86_64')
url="http://pypi.python.org/pypi/mercurial_keyring"
license=('BSD'),
makedepends=('python-distribute')
depends=('python-keyring' 'python2')
source=(http://pypi.python.org/packages/source/m/mercurial_keyring/mercurial_keyring-$pkgver.tar.gz)
md5sums=('ef2aaadb323e11115a21b110e405e5f9')

build() {
cd $startdir/src/mercurial_keyring-$pkgver
PYTHON=python2
python2 setup.py install --root=$pkgdir || return 1
}

This could be a patch to wait until they patch upstream:

sed -i -e 's/except \(.*\),\(.*\):/except \1 as \2:/'

(by the way, 0.4.2 is out :)

So, I checked and setuptools for python3 is provided by python-distribute (which is not installed for python3, so in the end it is unusable for now…).

mercurial keyring will need anyway a patch to be compilable under python (and being still compatible with python 2.7 of course :)

See: http://bitbucket.org/Mekk/mercurial_keyring/issue/4/add-python3-support

Did you do something special with this last revision?

Because it is still calling python and I get this error:
Traceback (most recent call last):
File "setup.py", line 5, in <module>
from setuptools import setup, find_packages
ImportError: No module named setuptools

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "setup.py", line 7, in <module>
from ez_setup import use_setuptools
ImportError: No module named ez_setup

Hi, I think the PKGBUILD should be changed to use python2 or be adapted for python-3!