What's happened?!
There was a sneaky bug in v1.6.0 which caused Twine to be outside the import path in the Python runtime. It is fixed in v1.6.1 by updating $PYTHONPATH
to point to a correct location of the user-global site-packages/
directory.
Full Diff: v1.6.0...v1.6.1