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 r.david.murray
Recipients barry, manu-beffara, michael-lazar, petri.lehtinen, r.david.murray
Date 2016-07-13.01:30:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468373442.26.0.838223431287.issue14977@psf.upfronthosting.co.za>
In-reply-to
Content
How about this: rename the existing readmailcapfile as an internal _readmailcapfile with the new signature.  Then add a backward compatible readmailcapfile with the existing signature/return value that uses a dummy value for lineno and throws away the lineno on output.  The point here is just to avoid breaking programs that are using the existing api, even though it is an internal one.  Yes, it is cruft, but backward compatibility sometimes requires cruft.  We could deprecate the old api with a message that says it is an internal method and should not be used, and see if anyone complains about it being deprecated.
History
Date User Action Args
2016-07-13 01:30:42r.david.murraysetrecipients: + r.david.murray, barry, petri.lehtinen, manu-beffara, michael-lazar
2016-07-13 01:30:42r.david.murraysetmessageid: <1468373442.26.0.838223431287.issue14977@psf.upfronthosting.co.za>
2016-07-13 01:30:42r.david.murraylinkissue14977 messages
2016-07-13 01:30:41r.david.murraycreate