On Fri, Dec 02, 2005 at 08:10:41PM -0500, Mike Meyer wrote:
> Inyeol Lee <[EMAIL PROTECTED]> writes:
> > On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
> >> > The problem is that myscript.py and some modules that myscript.py
> >> > imports are not in the current directory, but in anoth
Inyeol Lee <[EMAIL PROTECTED]> writes:
> On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
>> > The problem is that myscript.py and some modules that myscript.py
>> > imports are not in the current directory, but in another place in the
>> > filesystem, say, /path/to/stuff. If this was a
On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> > I have a Makefile target that uses a python script, like:
> >
> > %.abc: %.def
> > python myscript.py
> >
> > The problem is that myscript.py and some modules that myscript.py
>
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I have a Makefile target that uses a python script, like:
>
> %.abc: %.def
> python myscript.py
>
> The problem is that myscript.py and some modules that myscript.py
> imports are not in the current directory, but in another place in the
> f
[EMAIL PROTECTED]
> I have a Makefile target that uses a python script, like:
> %.abc: %.def
> python myscript.py
> If this was a tcsh script, I would just do:
>setenv PYTHONPATH /path/to/stuff
>python myscript.py
> but this cannot be done from a Makefile.
Use:
%.abc:
I have a Makefile target that uses a python script, like:
%.abc: %.def
python myscript.py
The problem is that myscript.py and some modules that myscript.py
imports are not in the current directory, but in another place in the
filesystem, say, /path/to/stuff. If this was a tcsh script, I w
