On Mon 23 Sep 2019 at 11:32:46 (-0400), Greg Wooledge wrote:
> On Sun, Sep 22, 2019 at 05:21:27PM +0200, Thomas Schmitt wrote:
> > PATH is a convention of shells like bash or dash, not of Python.
> > In your examples it lets the shell parser find /usr/bin/python from
> > "python".
>
> It's also us
On Mon 23 Sep 2019 at 06:10:22 (-0500), Richard Owlett wrote:
> On 09/23/2019 03:36 AM, Curt wrote:
> > [snip]
> >
> > Honestly, I took the name 'script'.py for a metasyntactic variable.
>
> Yes that was my intention. My question was concerning all scripts.
> Mentioning the specific script would
On Mon, Sep 23, 2019 at 01:12:14PM -0400, Greg Wooledge wrote:
> On Mon, Sep 23, 2019 at 06:56:47PM +0200, Thomas Schmitt wrote:
> > Problem is that Richard Owlett expected it to work in the starter program
> > of the interpreter (here: /usr/bin/python) when it opens the script file
> > for reading
On Mon, Sep 23, 2019 at 06:56:47PM +0200, Thomas Schmitt wrote:
> Greg Wooledge wrote:
> > I'd be rather surprised if there's *no* function in Python that uses
> > the PATH variable.
>
> Problem is that Richard Owlett expected it to work in the starter program
> of the interpreter (here: /usr/bin/
Hi,
Greg Wooledge wrote:
> I'd be rather surprised if there's *no* function in Python that uses
> the PATH variable.
Problem is that Richard Owlett expected it to work in the starter program
of the interpreter (here: /usr/bin/python) when it opens the script file
for reading. I assume Python deve
On Sun, Sep 22, 2019 at 05:21:27PM +0200, Thomas Schmitt wrote:
> PATH is a convention of shells like bash or dash, not of Python.
> In your examples it lets the shell parser find /usr/bin/python from
> "python".
It's also used by some of the libc exec wrappers. Specifically,
the ones with "p" in
On 09/23/2019 03:36 AM, Curt wrote:
[snip]
Honestly, I took the name 'script'.py for a metasyntactic variable.
Yes that was my intention. My question was concerning all scripts.
Mentioning the specific script would be "noise".
I
can't see offhand why it couldn't easily be changed if it was
On 09/22/2019 05:00 PM, David Wright wrote:
On Sun 22 Sep 2019 at 16:31:22 (-), Curt wrote:
On 2019-09-22, Thomas Schmitt wrote:
So to avoid the cd command with absolute path, you would have to give
the script address as absolute path:
python /path/to/script/script.py
I make my loc
On 09/22/2019 07:59 PM, David wrote:
On Mon, 23 Sep 2019 at 00:10, Richard Owlett wrote:
May I be pointed to a complete explanation of the use of the PATH$
environmental variable.
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
Section 8.3, subheading PATH
Thank yo
On 2019-09-22, David Wright wrote:
> On Sun 22 Sep 2019 at 16:31:22 (-), Curt wrote:
>> On 2019-09-22, Thomas Schmitt wrote:
>> >
>> > So to avoid the cd command with absolute path, you would have to give
>> > the script address as absolute path:
>> >
>> > python /path/to/script/script.py
>
On Mon, 23 Sep 2019 at 00:10, Richard Owlett wrote:
> May I be pointed to a complete explanation of the use of the PATH$
> environmental variable.
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
Section 8.3, subheading PATH
On Sun 22 Sep 2019 at 16:31:22 (-), Curt wrote:
> On 2019-09-22, Thomas Schmitt wrote:
> >
> > So to avoid the cd command with absolute path, you would have to give
> > the script address as absolute path:
> >
> > python /path/to/script/script.py
> >
>
> I make my local scripts executable a
On Sun 22 Sep 2019 at 16:31:22 -, Curt wrote:
> On 2019-09-22, Thomas Schmitt wrote:
> >
> > So to avoid the cd command with absolute path, you would have to give
> > the script address as absolute path:
> >
> > python /path/to/script/script.py
> >
>
> I make my local scripts executable an
On 2019-09-22, Thomas Schmitt wrote:
>
> So to avoid the cd command with absolute path, you would have to give
> the script address as absolute path:
>
> python /path/to/script/script.py
>
I make my local scripts executable and stick them in '/usr/local/bin'.
> Have a nice day :)
>
> Thomas
>
On Sun 22 Sep 2019 at 09:10:17 (-0500), Richard Owlett wrote:
> I recently downloaded a python script which uses some custom helper
> scripts. The scriptS are provided as zip file. The instructions were
> ti download to chosen directory and un-zip the file.
>
> The launching instructions were to d
Hi,
Richard Owlett wrote:
> The launching instructions were to do
>cd /path/to/script
> then
>python script.py
> I thought I could "simplify" my life by doing
>export PATH=$PATH:/path/to/script
> and then launch by doing just doing
>python script.py
>
> That FAILED to find script.p
Hi.
On Sun, Sep 22, 2019 at 09:10:17AM -0500, Richard Owlett wrote:
> May I be pointed to a complete explanation of the use of the PATH$
> environmental variable.
bash(1), COMMAND EXECUTION section.
Reco
I recently downloaded a python script which uses some custom helper
scripts. The scriptS are provided as zip file. The instructions were ti
download to chosen directory and un-zip the file.
The launching instructions were to do
cd /path/to/script
then
python script.py
That *WORKS* as adv
18 matches
Mail list logo
