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 chris.jerdonek, eric.araujo, ezio.melotti, xdegaye
Date 2012-09-28.22:58:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It doesn't necessary have to be limited to methods, anything duplicate might turn out to be a bug.  If the script doesn't mix scopes there shouldn't be too many false positives, and if they are it shouldn't be a big deal if they are reported on the changed file by `make patchcheck`.

> I'm not sure if there is ever a use case for duplicate
> method names.  Is there?

Nothing that can't be done in a more elegant way afaict.

It might make sense for variables though, where you have e.g.:

foo = do_something(x)
foo = do_something_more(foo)
Date User Action Args
2012-09-28 22:58:56ezio.melottisetrecipients: + ezio.melotti, eric.araujo, chris.jerdonek, xdegaye
2012-09-28 22:58:56ezio.melottisetmessageid: <>
2012-09-28 22:58:56ezio.melottilinkissue16079 messages
2012-09-28 22:58:56ezio.melotticreate