From: "Paul Varner" <fuzzyray@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:gentoolkit commit in: pym/gentoolkit/
Date: Tue, 13 Nov 2012 20:40:58 +0000 (UTC) [thread overview]
Message-ID: <1352684108.88ac4e9030ab5827d1ab4d01ee6c0aff85184d28.fuzzyray@gentoo> (raw)
commit: 88ac4e9030ab5827d1ab4d01ee6c0aff85184d28
Author: W. Trevor King <wking <AT> tremily <DOT> us>
AuthorDate: Mon Nov 12 01:35:08 2012 +0000
Commit: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
CommitDate: Mon Nov 12 01:35:08 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=88ac4e90
keyword: use Python 2/3-agnostic set notation in reduce_keywords doctest
Python 2.7 prints sets as "set([1, 2])", but Python 3.2 prints them as
"{1, 2}". Avoid having to chose by showing that the result of
reduce_keywords() is a set, and then printing the elements in a list.
---
pym/gentoolkit/keyword.py | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/pym/gentoolkit/keyword.py b/pym/gentoolkit/keyword.py
index 17b3472..a234116 100644
--- a/pym/gentoolkit/keyword.py
+++ b/pym/gentoolkit/keyword.py
@@ -95,8 +95,11 @@ def reduce_keywords(keywords):
"""Reduce a list of keywords to a unique set of stable keywords.
Example usage:
- >>> reduce_keywords(['~amd64', 'x86', '~x86'])
- set(['amd64', 'x86'])
+ >>> kw = reduce_keywords(['~amd64', 'x86', '~x86'])
+ >>> isinstance(kw, set)
+ True
+ >>> sorted(kw)
+ ['amd64', 'x86']
@type keywords: array
@rtype: set
next reply other threads:[~2012-11-13 20:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 20:40 Paul Varner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-02 22:10 [gentoo-commits] proj/gentoolkit:gentoolkit commit in: pym/gentoolkit/ Paul Varner
2014-02-22 19:28 Brian Dolbec
2013-03-12 16:06 Mike Frysinger
2013-01-04 22:23 Paul Varner
2012-12-30 20:25 Brian Dolbec
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-10-09 21:35 Paul Varner
2012-08-01 3:34 Brian Dolbec
2012-07-24 17:18 Paul Varner
2012-05-16 21:18 Paul Varner
2012-03-02 0:01 Brian Dolbec
2011-12-23 6:05 Brian Dolbec
2011-07-16 4:04 Paul Varner
2011-07-16 3:21 Paul Varner
2011-07-15 20:02 Paul Varner
2011-05-23 3:45 Brian Dolbec
2011-05-20 5:54 Brian Dolbec
2011-05-18 21:18 Brian Dolbec
2011-04-18 18:28 Paul Varner
2011-03-31 21:53 Paul Varner
2011-02-23 9:10 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=1352684108.88ac4e9030ab5827d1ab4d01ee6c0aff85184d28.fuzzyray@gentoo \
--to=fuzzyray@gentoo.org \
--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