Author vstinner
Recipients larry, serhiy.storchaka, tashrifbillah, vstinner
Date 2018-11-06.20:46:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1541537200.62.0.788709270274.issue35178@psf.upfronthosting.co.za>
In-reply-to
Content
> Typo/trivial mistake in warnings.py (may be related to 2.x to 3.x conversion)

It's not a typo: it's that my change now requires the last argument of formatwarning() to be a keyword argument called 'line'.

The error comes from numpy.

But I'm fine to now require that the last formatwarning() argument is called 'line' and pass its value as an positional argument, not as a keyword argument.

In that case, I would like to see an unit test to check that replacing warnings.formatwarning() with a new function and the last parameter of this function is not called 'line' still works.
History
Date User Action Args
2018-11-06 20:46:40vstinnersetrecipients: + vstinner, larry, serhiy.storchaka, tashrifbillah
2018-11-06 20:46:40vstinnersetmessageid: <1541537200.62.0.788709270274.issue35178@psf.upfronthosting.co.za>
2018-11-06 20:46:40vstinnerlinkissue35178 messages
2018-11-06 20:46:40vstinnercreate