Plus some minor changes:
- added unittests to test reset() functionality
- fixed a minor bug in __init__.py where py2 module was import first when running on py3
- prevent pyc files from being written during unittests, to protect later tests from finding pyc files written by earlier tests
NOTE: reset() and uninstall() don't fully work in py2, and their tests currently fail on py2,
until issue#2 is resolved (https://github.com/elfsternberg/polyloader/issues/2)
Unit tests included to ensure that Polyloader doesn't interfere with
standard Python import behavior, while still allowing for arbitrary
compilers to be associated with new file suffixes on the fly.
WOOT!
I wrote unit tests!
The syntax of the compilers has been change; I chose to trust Python's
source file loaders, so now we get a default stream in whatever format
the current version of Python is most comfortable with.
Made a note in my TODO about a Context Manager for making Polyloaders
"live" and then removing them automatically when a procedure goes out
of scope.
I have this weird sensation that this might actually work...
This is broken out from a week-long development cycle for the
[Hy](http://docs.hylang.org/en/latest/) programming language,
which I can't recommend enough.
shx2
Elf M. Sternberg