[issue28593] Inconsistent itertools' predicate behaviour

Changes by Raymond Hettinger : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue28593] Inconsistent itertools' predicate behaviour

Francisco Couzo added the comment: I think removing None as a valid predicate to filterfalse would make the API simpler, but I don't know if it's worth the API change, please do close the issue if you think it's not worth it. -- ___ Python tracker

[issue28593] Inconsistent itertools' predicate behaviour

Serhiy Storchaka added the comment: Note that the predicate is optional argument in groupby but mandatory in dropwhile and takewhile. I suppose that filter and filterfalse accept None for historical reason (they precede bool). -- nosy: +serhiy.storchaka ___

[issue28593] Inconsistent itertools' predicate behaviour

Raymond Hettinger added the comment: I think that the simpler signature is better, that the None argument isn't clear, and that there aren't use cases that warrant and API churn. On your last post, it seemed that you were withdrawing the request. Can this tracker item be closed now?

[issue28593] Inconsistent itertools' predicate behaviour

Changes by Raymond Hettinger : -- Removed message: http://bugs.python.org/msg280091 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue28593] Inconsistent itertools' predicate behaviour

Raymond Hettinger added the comment: I think that the simpler signature is better, that the None argument isn't clear, and that there aren't use cases that warrant and API churn. On your last post, I seemed that you were withdrawing the request. Can this tracker item be closed now? -

[issue28593] Inconsistent itertools' predicate behaviour

New submission from Francisco Couzo: As per Terry's recommendation https://mail.python.org/pipermail/python-dev/2016-November/146791.html Currently some functions in itertools (dropwhile and takewhile), don't accept None as a predicate, but filterfalse and groupby do. I'd like your input, and