My position is that generated files do not belong in a VCS and instead should be generated at build time if possible and at tarball build time if not. In the otData case the specs aren't free and some Linux distros don't allow network during building so otData.py needs to be in the tarballs. My plan was for otData.py to be removed from the VCS and the MetaTools/build_otData.py script (updated to the attached one) run by setup.py sdist to create it before building the source tarball.
I expect that you want to be able to just use fonttools from a git checkout? I suppose we could come up with compromise there, could you explain your position and use-case in more detail?
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.