[issue14977] mailcap does not respect precedence in the presence of wildcards

Changes by Michael Lazar <lazar.michae...@gmail.com>: Added file: http://bugs.python.org/file43706/mailcap_v3.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: Whoops -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14977> ___ ___ Python-bugs-list

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: I can certainly do that. Although in addition to adding a keyword argument, we would also have to change the return signature to switch between modes like this: if lineno is None: return caps else: return caps, lineno Overall I'm

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: That works for me, patch updated to match your suggestion. So to recap, the proposed fix implements the following changes to the api: getcaps() The returned dict now has an additional `lineno` field. There's a *slim* chance that this could break behavior

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: Got it, I found some examples and it didn't look too complicated so I took a shot at it. Is there anything else that needs to be added? Does the documentation need to be updated at all? btw, thanks for the rapid iteration. I appreciate you taking the time

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: Submitting an updated patch; simplified the implementation and updated test_mailcap.py -- Added file: http://bugs.python.org/file43695/mailcap_v2.patch ___ Python tracker <rep...@bugs.python.org>

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: Hello. In my opinion this is a pretty major deficiency. I was trying to add definitions to my ~/.mailcap file (which should take priority over system mailcap files) but they weren't getting applied because of the wildcard bug. This was prohibiting me from

[issue14977] mailcap does not respect precedence in the presence of wildcards

Michael Lazar added the comment: Alright thanks, I've submitted a patch -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14977> ___ __

[issue14977] mailcap does not respect precedence in the presence of wildcards

Changes by Michael Lazar <lazar.michae...@gmail.com>: -- keywords: +patch Added file: http://bugs.python.org/file43682/mailcap.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue31348] webbrowser BROWSER with MacOSXOSAScript type

New submission from Michael Lazar: Hello, I have found that [1] is an open issue, but I have discovered what appears to be a completely separate bug than the one described in that ticket. The issue is that there is no way to specify a MacOSXOSAScript browser using the BROWSER variable

[issue32861] urllib.robotparser: incomplete __str__ methods

New submission from Michael Lazar <lazar.michae...@gmail.com>: Hello, I have stumbled upon a couple of inconsistencies in urllib.robotparser's __str__ methods. These appear to be unintentional omissions; basically the code was modified but the string methods were never updat

[issue32861] urllib.robotparser: incomplete __str__ methods

Change by Michael Lazar <lazar.michae...@gmail.com>: -- keywords: +patch pull_requests: +5500 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue38656] mimetypes for python 3.7.5 fails to detect matroska video

Michael Lazar added the comment: Greetings, I just encountered this issue [0] and I agree with the sentiment that the documentation is currently misleading. Particularly, > By default, it provides access to the same database as the rest of this > module. The initial database is