Package Details: python2-launchpadlib 1.10.6-1

Git Clone URL: (read-only, click to copy)
Package Base: python2-launchpadlib
Description: A free Python library for scripting Launchpad through its web services interface.
Upstream URL:
Licenses: LGPL3
Conflicts: launchpadlib
Provides: python2-launchpadlib
Submitter: ValHue
Maintainer: ValHue
Last Packager: ValHue
Votes: 1
Popularity: 0.000001
First Submitted: 2016-03-22 18:06
Last Updated: 2018-11-10 10:23

Latest Comments

1 2 Next › Last »

ValHue commented on 2019-04-15 09:36

@j_4321, In agreement. I tried to leave a record in the comments so nobody tried to install the python3 version.

My problem now is python2-keyring that is no longer maintained because in the repo community there is python-keyring which, in theory, is compatible with both versions of python, but it does not work for me. I suppose that before the abandonment of memaker on the part of its creators and the antiquated of these bookstores and the own python2, in the end I will abandon all of them ...

Best regards..

j_4321 commented on 2019-04-15 09:28

@ValHue Since your package installs the python2 version, I changed my PKGBUILDs to build only the python3 versions (anyway I don't think I could have uploaded a PKGBUILD building python-launchpadlib and python2-launchpadlib since python2-launchpadlib is already available in AUR.)

ValHue commented on 2019-04-15 08:06

@j_4321, Are you sure? I have checked it more than once and your package only installs the python3 version of the libraries.And of course, memaker, the program I used with python2-launchpadlib does not detect python-launchpadlib

j_4321 commented on 2019-02-19 16:55

@gour, @ValHue python-launchpadlib and its dependencies are now available in AUR:

ValHue commented on 2019-02-19 14:48

@j_4321, I think yes, that would be the right thing to do.

In the official repo we find, for example, python-dbus and pyhton2-dbus; python-django and python2-django; etc...

j_4321 commented on 2019-02-19 12:50

@ValHue Just to be sure I have understood correctly, the idea is that I publish separately a python3-only version of the packages (i.e. python-launchpadlib, python-lazr-uri ...) instead of PKGBUILDs which compile both the python 2 and python 3 versions?

ValHue commented on 2019-02-19 12:30

Sorry for the delay, I'm very busy lately and I have not been able to answer the mail, so I did not see the notifications of your comments.

I have reviewed the PKGBUILDS of @j_4321 and I find them correct, I would publish them in AUR directly.

Instead of adapting these packages from python2 to python3, it would be convenient to create new ones and upload the PKGBUILD. The current version of python2 is currently only used for one package, but I think it is the right decision.

Since @j_4321 has done all the work, it should be he who publishes them.

I remain at your disposal.

j_4321 commented on 2019-02-19 10:47

@gour I do not plan to submit to AUR right now because my packages are partly redundant with this one and its dependencies. However I sent an email some time ago to ValHue with my patches to adapt the PKGBUILDs to python 3 but I never received any reply.

gour commented on 2019-02-19 10:15

@j_4321 do you plan to submit them to AUR?

j_4321 commented on 2019-02-18 08:50

@gour I needed python3 support too so I wrote the PKGBUILDs for launchpadlib and its dependencies. You can find them here: