From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-keys:master commit in: gkeys/
Date: Tue, 27 May 2014 20:56:40 +0000 (UTC) [thread overview]
Message-ID: <1400953128.4141af80341062e6b6db0b636a05988fa09e1f9f.dol-sen@gentoo> (raw)
commit: 4141af80341062e6b6db0b636a05988fa09e1f9f
Author: Pavlos Ratis <dastergon <AT> gentoo <DOT> org>
AuthorDate: Sat May 24 17:26:19 2014 +0000
Commit: Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sat May 24 17:38:48 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-keys.git;a=commit;h=4141af80
subclass __new__ to make both gkeys and gkeyldap work properly
---
gkeys/config.py | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gkeys/config.py b/gkeys/config.py
index b20d5cd..9d629b7 100644
--- a/gkeys/config.py
+++ b/gkeys/config.py
@@ -130,6 +130,13 @@ class GKEY(namedtuple('GKEY', ['nick', 'name', 'keyid', 'longkeyid',
'keydir', 'fingerprint'])):
'''Class to hold the relavent info about a key'''
+ # subclass __new__ to make both gkeys and gkeyldap work properly
+ # delete it when keyid and longkeyid are removed from LDAP
+ def __new__(cls, nick=None, name=None, keydir=None, fingerprint=None,
+ keyid=None, longkeyid=None):
+ return super(GKEY, cls).__new__(cls, nick, name, keydir, fingerprint,
+ keyid, longkeyid)
+
field_types = {'nick': str, 'name': str, 'keyid': list,
'longkeyid': list, 'keydir': str, 'fingerprint': list}
field_separator = "|"
next reply other threads:[~2014-05-27 20:56 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 20:56 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-01 15:16 [gentoo-commits] proj/gentoo-keys:master commit in: gkeys/ Brian Dolbec
2015-08-09 3:44 Robin H. Johnson
2014-12-24 20:05 Brian Dolbec
2014-12-24 19:59 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-12-22 23:11 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-08-20 3:55 Brian Dolbec
2014-06-01 15:25 Brian Dolbec
2014-06-01 15:25 Brian Dolbec
2014-06-01 15:25 Brian Dolbec
2014-05-28 2:21 Brian Dolbec
2014-05-28 2:21 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-27 20:56 Brian Dolbec
2014-05-17 18:13 Brian Dolbec
2014-03-01 17:50 Pavlos Ratis
2014-03-01 17:50 Pavlos Ratis
2014-03-01 17:49 Pavlos Ratis
2014-03-01 0:07 Brian Dolbec
2014-02-28 23:56 Brian Dolbec
2014-02-28 20:21 Brian Dolbec
2013-11-17 7:39 Brian Dolbec
2013-11-17 7:39 Brian Dolbec
2013-11-17 7:39 Brian Dolbec
2013-11-17 7:39 Brian Dolbec
2013-11-17 7:39 Brian Dolbec
2013-11-15 9:16 Brian Dolbec
2013-07-16 0:50 Brian Dolbec
2013-07-16 0:50 Brian Dolbec
2013-07-16 0:50 Brian Dolbec
2013-07-16 0:50 Brian Dolbec
2013-07-16 0:50 Brian Dolbec
2013-07-06 19:02 Brian Dolbec
2013-07-06 19:02 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2013-06-23 7:13 Brian Dolbec
2012-12-10 4:56 Brian Dolbec
2012-12-10 4:56 Brian Dolbec
2012-12-10 3:26 Brian Dolbec
2012-12-10 3:26 Brian Dolbec
2012-12-10 3:26 Brian Dolbec
2012-12-10 3:26 Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1400953128.4141af80341062e6b6db0b636a05988fa09e1f9f.dol-sen@gentoo \
--to=brian.dolbec@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox