Python3 compatibility #27
Conversation
|
@kfuruya your additions to the pull requests have been awesome, but I see you didn't merge them. Was something stopping you? This look s great to me. |
|
The commits need to be squashed into one! Then it's great to go in. |
|
I thought I did that, hang on. On Tue Nov 04 2014 at 1:52:13 PM Kim Furuya [email protected]
|
dmasad
force-pushed
the
python3_compatibility
branch
from
a68ae49 to
d90756c
Compare
|
Okay should be done now. On Tue Nov 04 2014 at 1:53:20 PM David Masad [email protected] wrote:
|
Oops fixed Adding in WolfSheepPredation Adding parameters and fixing style issues
dmasad
force-pushed
the
python3_compatibility
branch
from
d90756c to
9ad9cc7
Compare
* Use Pathlib Code by Phil Robare (versilimidude2) * Use pre-commit * Dropped unused imports * used pre-commit to run pyupgrade, trim whitespace * Remove pathlib changes These belong in a separate PR. * remove redundant black, move comment as per rht's suggestions --------- Co-authored-by: Catherine Devlin <[email protected]>
* Use Pathlib Code by Phil Robare (versilimidude2) * Use pre-commit * Dropped unused imports * used pre-commit to run pyupgrade, trim whitespace * Remove pathlib changes These belong in a separate PR. * remove redundant black, move comment as per rht's suggestions --------- Co-authored-by: Catherine Devlin <[email protected]>
* Use Pathlib Code by Phil Robare (versilimidude2) * Use pre-commit * Dropped unused imports * used pre-commit to run pyupgrade, trim whitespace * Remove pathlib changes These belong in a separate PR. * remove redundant black, move comment as per rht's suggestions --------- Co-authored-by: Catherine Devlin <[email protected]>
3 participants
Turns out that all it took was changing print to print() to make this Python 3 compatible. As written now, it's still backwards-compatible with Python 2 as well. This will resolve issue #23.