mailcap top level wildcard support

[pacien]

BPO	38126
Nosy	@warsaw, @bitdancer, @pacien

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-09-12.02:18:26.454>
labels = ['type-bug', 'expert-email']
title = 'mailcap top level wildcard support'
updated_at = <Date 2019-09-12.02:18:26.454>
user = 'https://github.com/pacien'

bugs.python.org fields:

activity = <Date 2019-09-12.02:18:26.454>
actor = 'pacien'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2019-09-12.02:18:26.454>
creator = 'pacien'
dependencies = []
files = []
hgrepos = []
issue_num = 38126
keywords = []
message_count = 1.0
messages = ['352038']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'pacien']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38126'
versions = []

[pacien]

given ~/.mailcap containing:
*/*; xdg-open "%s"

>>> mailcap.findmatch(mailcap.getcaps(), 'application/pdf', filename='thing.pdf')
returns: (None, None)
instead of: ('xdg-open "thing.pdf"', {'view': 'xdg-open "%s"', 'lineno': 0})

---

While top-level wildcards aren't defined in RFC1524, most other tools and programs (including mutt for example) handle them properly.

Entries of the form of "*; someprogram" or "*/*; someprogram" are useful for fallbacks when no other more precise type can be found.

[brettcannon]

Closing as mailcap is slated for deprecation (#91217).