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.

Sign up for GitHub

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

Jump to bottom

csort range py3 compatible #32

Merged
merged 3 commits into from
Nov 3, 2016
Merged

csort range py3 compatible #32

merged 3 commits into from
Nov 3, 2016

Commits on Nov 2, 2016

  1. Changed xrange to range for blue-yonder#8

    @earthgecko
    earthgecko committed Nov 2, 2016
    Configuration menu
    Copy the full SHA
    42f0a8a View commit details
    Browse the repository at this point in the history

  2. Modified csort due to range changing from list to type for blue-yonder#8

    @earthgecko
    earthgecko committed Nov 2, 2016
    Configuration menu
    Copy the full SHA
    5d03264 View commit details
    Browse the repository at this point in the history

Commits on Nov 3, 2016

  1. Use assertItemsEqual py2 and assertCountEqual py3 

    Due to a change in unittest in as identified by @jneuff in
blue-yonder#8 (comment)

Semantically they appear to be the same and this fixes the related failing
tests on Python 3.5 as described in the gist in
blue-yonder#8 (comment)

Adds a basic method to determine python version for now, only committing so that
the new deeper unitest.assertEqual issue that now presents itself can be
addressed.
    @earthgecko
    earthgecko committed Nov 3, 2016
    Configuration menu
    Copy the full SHA
    7c2be54 View commit details
    Browse the repository at this point in the history