[issue31585] Refactor the enumerate.__next__ implementation

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Added a patch for history.

--
Added file: https://bugs.python.org/file47235/enum_next.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31585] Refactor the enumerate.__next__ implementation

[Raymond Hettinger]

Raymond Hettinger added the comment:

Having separate code paths was an intentional decision.  I prefer to keep it 
that way.

--
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31585] Refactor the enumerate.__next__ implementation

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
keywords: +patch
pull_requests: +3745
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31585] Refactor the enumerate.__next__ implementation

[Serhiy Storchaka]

New submission from Serhiy Storchaka:

Currently the large and complex part of enum_next() and enum_next_long() in 
Objects/enumobject.c is duplicated. This increases the code size and makes 
harder maintaining the code. The proposed patch refactors the implementation 
and removes the code duplication.

--
components: Interpreter Core
messages: 303006
nosy: rhettinger, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Refactor the enumerate.__next__ implementation
type: enhancement
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com