Fixing issue #2 related to usage of six.moves.range #5
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.
https://six.readthedocs.io/#module-six.moves (Renamed modules and attributes compatibility)
rangeinsix.movesrefers to xrange in python 2 and range in python 3In my opinion,
range(self.GetColumnCount())[::-1]is not a proper usage.Though this works in python 3 but it crashes in python 2.
https://www.geeksforgeeks.org/range-vs-xrange-python/
This webpage explains the use of xrange.
In python 2, it throws the error:
TypeError: sequence index must be integer, not 'slice'