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 ezio.melotti
Recipients ezio.melotti, mark.dickinson, serhiy.storchaka
Date 2012-11-23.18:47:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353696479.35.0.845005336868.issue16543@psf.upfronthosting.co.za>
In-reply-to
Content
> Okay, but what exactly is this fixing? 

If the function parses positional args, it should say so in the error message.  If the function is never used (except for min/max) or if the error is never reported, then we have a different problem.

Even if this code is not used I don't think we can remove it, since this it's a public function, and even if we are not using it someone might be using it and benefit from the improved error message.
History
Date User Action Args
2012-11-23 18:47:59ezio.melottisetrecipients: + ezio.melotti, mark.dickinson, serhiy.storchaka
2012-11-23 18:47:59ezio.melottisetmessageid: <1353696479.35.0.845005336868.issue16543@psf.upfronthosting.co.za>
2012-11-23 18:47:59ezio.melottilinkissue16543 messages
2012-11-23 18:47:59ezio.melotticreate