This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gnofi
Recipients gnofi
Date 2010-04-22.00:47:51
SpamBayes Score 1.5709656e-13
Marked as misclassified No
Message-id <1271897273.03.0.77391363509.issue8496@psf.upfronthosting.co.za>
In-reply-to
Content
The lookup method in the Python 3.2 mailcap module still uses filter as if it will return a list, like it did in Python 2. If a value for the "key" argument is passed to the method, the method will return a filter iterator rather than a list.

I discovered this while running a test I created for mailcap. It's not checked in yet. See Issue6484.

This is probably low priority because mailcap.lookup() is an internal method. It is used by mailcap.findmatch(), which actually handles the filter iterator gracefully. Nevertheless, I don't think it should return a different type based on whether the key argument is passed. The fix is simple enough.
History
Date User Action Args
2010-04-22 00:47:53gnofisetrecipients: + gnofi
2010-04-22 00:47:53gnofisetmessageid: <1271897273.03.0.77391363509.issue8496@psf.upfronthosting.co.za>
2010-04-22 00:47:51gnofilinkissue8496 messages
2010-04-22 00:47:51gnoficreate