Python3 compatibility and misc fixes in parseCoord #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- map() returns a iterable which is not sliceable. - Fix a bug where the coordinate vector could be resized. - Better error reporting. Signed-off-by: Maël Kerbiriou <m431.kerbiriou@gmail.com>
Owner
|
Thanks for fixing that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
[1,2][0:3] == [1,2](doesn't raise)p = [None]*3 ; p[0:3] = [1,2] ; assert len(p) == 2(resizes a slice in place)I don't have a setup right now for testing on a real printer. Reading the documentation, I'm not entirely sure in which cases different numbers of coordinates should be tolerated.