Recent versions of Python will break the current exporters because of the use of non-ASCII characters in the comment section. See:
http://www.python.org/dev/peps/pep-0263/ where it states:
Python will default to ASCII as standard encoding if no other
encoding hints are given.
To define a source code encoding, a magic comment must
be placed into the source files either as first or second
line in the file, such as:
# coding=<encoding name>
or (using formats recognized by popular editors)
#!/usr/bin/python
# -*- coding: <encoding name> -*-
or
#!/usr/bin/python
# vim: set fileencoding=<encoding name> :
The 1.5 exporter script fails on line 133 and the 1.6 script fails on line 138, both of which are a recognition of help received:
# « pseudonym404 » : NMVert.uvco issue and solutions
As a work around you can delete the line in question after saying "all hail « pseudonym404 » for the contribution to this export script" a real fix might be to include some encoding (Or move the recognition from the script to a readme file
)