A fresh start

[jonathanfine]

I've decided that the best way to fix issues

• Test framework does not test previous version #61 Test framework does not test previous version
• Signature of Minecraft constructor has changed - previously took a connection #59 Signature of Minecraft constructor has changed - previously took a connection
• Purpose of 1.0 release #58 Purpose of 1.0 release
• Compatibility of code base with previous version not obvious #57 Compatibility of code base with previous version not obvious

is to make a fresh start.

I've done this at https://github.com/jonathanfine/py-mcpi

I believe that https://github.com/jonathanfine/py-mcpi/tree/add-python3 is fit for release, but I've not tested it. (This work is closely based on the early commits to this project, and particular thanks are due to @doismellburning and @ghickman , whose steps I have followed.)

It would be good to have some testing, and I'm working on that in https://github.com/jonathanfine/py-mcpi/tree/add-tests.

My way of working will be to add tests that pass on the original codebase, and then merge them into the add-python3 branch. This ensures that the tests are run on both the original and new code, resolving #61. I followed this path to discover the unicode-bytes-socket problem that @ghickman found before me.

The changes I'm making to the code are small, so this will help a great deal with #57.

[bennuttall]

Hi all

Where are we up to with this?