On 28 February 2013 20:53, Daniel Holth wrote:
>> Sorry, I wasn't clear. I know about that, but I don't know how to set
>> up a site directory *before* starting the Python process. Thinking
>> about it, I guess I could do the addsitedir thing and then execfile
>> setup.py. Put all of that into a -
> Sorry, I wasn't clear. I know about that, but I don't know how to set
> up a site directory *before* starting the Python process. Thinking
> about it, I guess I could do the addsitedir thing and then execfile
> setup.py. Put all of that into a -c script. That's probably OK, just a
> bit messy. Pa
On 28 February 2013 20:30, Daniel Holth wrote:
> On Thu, Feb 28, 2013 at 3:26 PM, Paul Moore wrote:
>> For some scripts I am writing, I want to be able to run a package's
>> setup.py using subprocess.check_call(). However, the python
>> installation I'm using may not have setuptools/distribute in
On Thu, Feb 28, 2013 at 3:26 PM, Paul Moore wrote:
> For some scripts I am writing, I want to be able to run a package's
> setup.py using subprocess.check_call(). However, the python
> installation I'm using may not have setuptools/distribute installed,
> and yet I want to correctly process setup.
For some scripts I am writing, I want to be able to run a package's
setup.py using subprocess.check_call(). However, the python
installation I'm using may not have setuptools/distribute installed,
and yet I want to correctly process setup.py files which rely on
setuptools. Is there any way of setti
