Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix whitespace during Python 2to3 migration #10978

Merged
merged 1 commit into from
Aug 10, 2020

Conversation

mmisol
Copy link
Collaborator

@mmisol mmisol commented Aug 7, 2020

Purpose

The 2to3 migration script, by design, does not take care of normalizing
whitespaces. Python 3, as opposed to Python 2, enforces that spaces and
tabs cannot be mixed. In order to get a working script, a reindentation
is performed over the migrated content. This is only done in case the
code uses tabs, otherwise there is no need to do changes to indent.

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated

Reviewers

@QilongTang @mjkkirschner

FYIs

@DynamoDS/dynamo

The 2to3 migration script, by design, does not take care of normalizing
whitespaces. Python 3, as opposed to Python 2, enforces that spaces and
tabs cannot be mixed. In order to get a working script, a reindentation
is performed over the migrated content. This is only done in case the
code uses tabs, otherwise there is no need to do changes to indent.
@@ -0,0 +1,182 @@
#! /usr/bin/env python3

# Based on a script by Tim Peters, 03 October 2000.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the license for this code?
should it be added to license / about etc?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure. I got the original script from the Python repo, so I guess it's the same license.

@mmisol mmisol merged commit 1125d11 into DynamoDS:master Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants