[Distutils] How to prevent some .egg-info files being "touched" during a build/install process

[Phillip J. Eby]

At 02:28 PM 4/5/2007 -0700, Venkat Bommakanti wrote:
>Thanks, Matt & Philip.
>
>I'll get them out of source control - since those
>files were deployed in the installed egg, I thought
>they were needed to be under source control.
>
>Just like one can specify temp build & dist dirs to
>be used in the build/install process, is it possible
>to have setuptools place these files in a user-defined
>dir... that'd make it easy to implement the
>"make clean" equivalent to ensure these files don't
>show up as being "privtate" files in one's tree.

See the egg_info command options, but please note that "setup.py develop" 
and "setup.py test" will not work correctly unless the .egg-info directory 
is in its default location.  So, if you can live with that limitation, yes, 
you can change where the egg-info lives.  If not, then the answer is no.