[Distutils] setuptools passing arguments/settings to dependencies' dependencies

[Kent]

> I thought you were using --find-links as of your last email?  So, I'm a little confused as to what scenario you're actually trying to fix.
>

Yes, I mentioned, I *used* to be using --find-links, but I determined
this is not what I really wanted (though it did work in version c9).

> The next thing I would do is verify that the config file is actually being read, by setting the DISTUTILS_DEBUG environment variable to "yes", and then running "easy_install -v ." and observing the output.
>

I know the answer is "absolutely, yes" for top level dependencies, as
web access is blocked due to the setup.cfg line.  Just not for the
dependencies' dependencies.  When I get a chance and I am in the
office, I would gladly post the results of the debug.

>
>> Like I mentioned, I do have a workaround in place that is working for
>> me.  I post it here in case it may help others:
>
> Please don't do that, and *nobody else should do it either*.  You are going to ERASE people's personal distutils configuration files with that code!  (You're not even checking to see if it exists first!)
>

Thank you for posting the disclaimer before use.  I am exactly aware
it is deleting that file and for my project that is completely
acceptable, so I did not do anything fancy like backing it up.  I'd
hope anyone using this would have an understanding of python enough to
see what is going on and modify it to meet their needs, but that is a
poor assumption so a disclaimer would have been better; thank you for
posting such.

> I would be *extremely* upset if I tried to install your package and it erased one of my .pydistutils.cfg files, with all their command aliases, wikiup configs, path customizations, etc.
>

(Again, for my project this is a non-issue, as our company installs
our software on our client's VMs - we are in complete control of the
environment, so the "pure evil", as you called it isn't at all - it
fixes an issue for us.)

> (Of course, when run under easy_install control, the sandbox should catch your setup script's antics and terminate it with an error without harming any files, but still...  it's pure evil and the sort of thing that should NEVER, ever be done in a setup.py, on pain of banishment from PyPI.)
>

I can only hope you are saying that tongue-in-cheek, because it is a
bit harsh (how did I possibly offend you?).  My workaround is
acceptable for me, (not for a cheese shop project, I agree), but may
help others in my circumstances.  setuptools is very useful software
even for projects that are never going to be publicly released.


Thanks again for your help thus far.