Switch from range(len(...))
to enumerate(...)
#82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
This PR aims to switch from
range(len(...))
toenumerate(...)
to access the counter and the value from the iterables at the same time.Rationale
It is not Pythonic to use
range(len(...))
. Index based loops do not exist in Python, it uses collection iterators instead.Python includes an
enumerate
method to add a counter to an iterator. This method allows you to access both the counter and the value of the iterator at the same time. It is therefore recommended to replacerange(len(...))
withenumerate(...)
.Testing/Review Recommendations
void
Future Work
void