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

Move to python 3 #28

Merged
merged 8 commits into from
Oct 23, 2017
Merged

Move to python 3 #28

merged 8 commits into from
Oct 23, 2017

Conversation

cecemel
Copy link
Contributor

@cecemel cecemel commented Oct 18, 2017

No description provided.

@coveralls
Copy link

coveralls commented Oct 18, 2017

Coverage Status

Coverage decreased (-1.0%) to 99.02% when pulling ec111b9 on move_to_python_3 into 7299df7 on DEV_0.4.0.

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.0%) to 99.02% when pulling 25e9e5a on move_to_python_3 into 7299df7 on DEV_0.4.0.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-1.0%) to 99.02% when pulling 25e9e5a on move_to_python_3 into 7299df7 on DEV_0.4.0.

@coveralls
Copy link

coveralls commented Oct 20, 2017

Coverage Status

Coverage decreased (-1.0%) to 99.02% when pulling c4c1e17 on move_to_python_3 into 7299df7 on DEV_0.4.0.

Copy link
Contributor

@Pieter-Beckers Pieter-Beckers left a comment

Choose a reason for hiding this comment

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

De changes hier en in de pairtree library vind ik goed, maar ik twijfel wel over de verdere onderhoudbaarheid van de pairtree library, maar zeker goed genoeg voor nu.

@Pieter-Beckers Pieter-Beckers merged commit d352908 into DEV_0.4.0 Oct 23, 2017
@Pieter-Beckers Pieter-Beckers deleted the move_to_python_3 branch October 23, 2017 07:30
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.

None yet

3 participants