Thanks for the extended write up. It reflects my understanding so far as well, and fine tuned a couple of points I've not been clear on.
First I think we have to make a distinction between the source tarball > (setup.py sdist) vs "binary" builds (ie setup.py bdist & setup.py install). My biggest question of the moment is whether we should make any distinction at all. Leo is a pure python program, not relying on any C extensions or anything. (Excepting PyQt, but Setuptools doesn't solve that for us anyway.) I don't understand what benefit might be gained from creating source and binary distributions. With source, we only need one, and (when properly configured) it serves all python versions and OS combinations. With binary we need a different configuration and delivery archive for each platform. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
