Package Details: python-gpapi 0.4.4-1

Git Clone URL: https://aur.archlinux.org/python-gpapi.git (read-only, click to copy)
Package Base: python-gpapi
Description: Google Play Unofficial Python API
Upstream URL: https://github.com/NoMore201/googleplay-api
Licenses: GPL3
Submitter: fordprefect
Maintainer: fordprefect (lightdot)
Last Packager: fordprefect
Votes: 6
Popularity: 0.000000
First Submitted: 2017-10-07 22:23 (UTC)
Last Updated: 2020-02-11 11:49 (UTC)

Latest Comments

1 2 Next › Last »

abouvier commented on 2018-09-10 15:36 (UTC)

It works :p

fordprefect commented on 2018-09-10 15:26 (UTC)

@doskoi: updated. please test and report.

abouvier commented on 2018-09-10 15:01 (UTC)

Plot twist, the API now use python-cryptography! And doesn't seem to need python-clint anymore.

lightdot commented on 2018-09-01 08:45 (UTC)

The good news is that they've also added the python2-pycryptodome, so we can keep the python 2 version of gpapi going. Not that anyone is likely to be testing it, let alone using it, but hey...

In any case, python-gpapi should now be pulling the python-pycryptodome by default (as it still provides python-crypto), without actually updating the PKGBUILD. I'll make the change explicit with the next update.

abouvier commented on 2018-08-31 17:48 (UTC) (edited on 2018-08-31 17:54 (UTC) by abouvier)

The python-crypto package has been removed from the official repository today.

lightdot commented on 2018-06-25 14:33 (UTC)

Sorry guys, it turns out that even my chroot environment is pulling python-pycryptodome in so I didn't notice the issue is this acute. I'll look into this.

yan12125 commented on 2018-06-24 02:29 (UTC)

Also, pycryptodome is preferred by the author NoMore201: https://github.com/NoMore201/googleplay-api/commit/e1cc147db466515b503d44f8256597c350a6df8d

yan12125 commented on 2018-06-24 02:27 (UTC)

@lightdot: currently gplaycli (a program uses gpapi) does not work out-of-box:

$ gplaycli 
Traceback (most recent call last):
  File "/usr/bin/gplaycli", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3095, in <module>
    @_call_aside
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3079, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3108, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 570, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 888, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 774, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pycryptodome' distribution was not found and is required by gpapi

lightdot commented on 2018-06-23 20:02 (UTC)

Is there a technical reason for this? I don't have a strong preference but I'd like to hear why specifically is this recommended.

1 2 Next › Last »