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 paul.j3
Recipients Leo Singer, Marcel H2, bethard, eli.bendersky, evan_, josh.r, markgrandi, moritz, naufraghi, palaviv, paul.j3, r.david.murray, sedrubal
Date 2018-09-09.17:03:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It's been sometime since I looked at this issue.  

The main sticking point is passing unittests, and ensuring that there are no backward compatibility issues.

But, since FileType is a standalone class, anyone could put a corrected version in their own workspace without modifying their stock version.  The 'type' parameter is designed for this kind of flexibility - it accepts any callable, whether a function, or a class with a __call__ method.
Date User Action Args
2018-09-09 17:03:17paul.j3setrecipients: + paul.j3, bethard, naufraghi, r.david.murray, eli.bendersky, moritz, markgrandi, josh.r, palaviv, evan_, sedrubal, Marcel H2, Leo Singer
2018-09-09 17:03:17paul.j3setmessageid: <>
2018-09-09 17:03:17paul.j3linkissue14156 messages
2018-09-09 17:03:17paul.j3create