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

getting ready for python 3 - part 2 #656

Closed
wants to merge 5 commits into from
Closed

Commits on Jul 3, 2019

  1. Copy the full SHA
    719db8d View commit details
    Browse the repository at this point in the history
  2. Replace xrange with range

    python 2 to 3: https://portingguide.readthedocs.io/en/latest/iterators.html#new-behavior-of-range
    
    Where there's a chance of performance issues with switching from the python 2 xrange to python 2 range, I've imported `from six.moves import range` to preserve the iterator behavior.
    However in places where there's not a performance issue, I've left out the six import so that there's less code churn after switching to python 3.
    adhintz committed Jul 3, 2019
    Copy the full SHA
    1bbcc9b View commit details
    Browse the repository at this point in the history
  3. Copy the full SHA
    d652122 View commit details
    Browse the repository at this point in the history
  4. Copy the full SHA
    a6b4245 View commit details
    Browse the repository at this point in the history

Commits on Aug 16, 2019

  1. Copy the full SHA
    8c54237 View commit details
    Browse the repository at this point in the history