gpgme/lang/python/gpg/results.py, branch gpgme-1.9.0GnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.9.02016-12-01T16:28:39Zpython: Make Results have a nicer __repr__.2016-12-01T16:28:39ZTobias Muellermuelli@cryptobitch.de2016-11-30T07:47:29Zurn:sha1:db2f6c1ca3d2ef228f4ca6653d594537622c8588
* lang/python/gpg/results.py (Result.__str__): Renamed to '__repr__'
...
* lang/python/gpg/results.py (Result.__repr__): ... and added fields.
--
So that it looks a bit nicer in the Python REPL.
It looked like this before:
In [2]: gpg.core.get_engine_info()[0]
Out[2]:
<gpg.results.EngineInfo at 0x7fb23509a240>
Now the output is
In [2]: gpg.core.get_engine_info()[0]
Out[2]:
EngineInfo(file_name='/usr/bin/gpg2', home_dir=None,
protocol=0, req_version='1.4.0', version='2.1.11')
This also applies to other results, e.g. the ImportResult.
Note that the format now changed from "<Class >" to "Class()". The
Python documentation on repr states: "For many object types, including
most builtins, eval(repr(obj)) == obj."
Signed-off-by: Tobias Mueller <muelli@cryptobitch.de>
python: Rename Python module from PyME to gpg.2016-10-31T14:42:27ZDaniel Kahn Gillmordkg@fifthhorseman.net2016-10-28T20:45:49Zurn:sha1:2fac017618a76882605125b05ff1f7393fe99860
This follows weeks of discussion on the gnupg-devel mailing list.
Hopefully it will make it easier for people using Python to use GnuPG
in the future.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>