Emanuel Barry added the comment: I'm not able to trigger an assertion error when running the latest trunk in debug mode. I get a "valid" range_iterator object though, and using __reduce__ gives me direct access to `range(0, 0, 0)` (which is completely worthless).
Error or not, this should be fixed, and your patch LGTM. Thanks! (I changed the type to 'behaviour' since I can't reproduce the assertion, but it doesn't make much of a difference) ---------- nosy: +ebarry stage: -> patch review title: assertion failure in rangeobject.c -> rangeiter_new fails when creating a range of step 0 type: crash -> behavior _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28376> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
