David Cournapeau <da...@ar.media.kyoto-u.ac.jp> writes: > Tres Seaver wrote: > > There are three classes of files here: > > > > - "source" files, which should be under version control, and > > included (by default) in the sdist. > > > > - "derived" files, which should *not* be under version control, > > but which might (in certain circumstances) be included in the > > sdist. E.g., the C file generated from a Pyrex / Cython source > > file, to enable builds on systems without Pyrex / Cython > > installed. > > > > - "stray" files, not under version control. These shuold *never* > > be in an sdist. > > Why those assumptions on what people can do. That's exactly what's > wrong with distutils for me, all those untold assumptions, which are > 'obviously' correct. As I said previously, including built > documentation is something I use MANIFEST.in for, and should be > supported, or at least possible.
That is, IIUC, covered by the “derived” class in Tres's list. -- \ “Are you pondering what I'm pondering?” “I think so, Brain, but | `\ wouldn't his movies be more suitable for children if he was | _o__) named Jean-Claude van Darn?” —_Pinky and The Brain_ | Ben Finney _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
