Python 3 compatibility, sort of, maybe #103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "py3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The first commit is entirely automated, using
futurize --stage1(a subset of2to3that avoids doing anything that would break 2). Looks like it accidentally nuked the CRs from a couple files, which has made this diff look much worse than it actually is.Successfully builds both pokered and pokeyellow using CPython 2.7 and CPython 3.5 and maybe even a PyPy in there somewhere. Makes me happy since bare
pythonis Python 3 on Arch.The test suite appears to be on fire, which makes it hard to tell if I broke anything. May keep poking at this, though.
Well, one way to fix the test suites is to keep deleting code and tests until everything is "passing". I guess we should setup travis-ci, since we are trying to not live in the dark ages and such.
Oho, believe me, I love deleting stuff that no one can justify keeping around. :D
Relative imports render poketools unusable as a git submodule.
That sounds backwards; relative imports exist for cases like submodules.
This is probably the issue @PikalaxALT ran into.
@PikalaxALT For reference, and for other people reading this page, I worked around this "can't relative import" error by invoking the tools as
python -m pokemontools.gbz80disasm(rather than for instancepython pokemontools/gbz80disasm.py).