pcp
[Top] [All Lists]

Re: [pcp] Yet another Python snarfoo

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Yet another Python snarfoo
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sat, 5 Mar 2016 17:41:48 -0500 (EST)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <001601d17725$b4f20430$1ed60c90$@internode.on.net>
References: <56D627B6.6000900@xxxxxxxxxxxxxxxx> <001601d17725$b4f20430$1ed60c90$@internode.on.net>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AQLvqQLv/fNB2KVOfunHCyODAhCp750O34vQfNdbKPM=
Thread-topic: Yet another Python snarfoo
Hi Ken,

----- Original Message -----
> I've been beating my head against this brick wall for a few days, and would
> really like some pain relief ...
> 

:)  Thanks for fighting the good fight!

> [...]
>       #!/usr/bin/env pmpython
> 
> which demonstrably works.
> 
> Anyone see a problem with globally replacing the existing #!/usr/bin/pcp
> python with the above for Python scripts in PCP?
> 

Seems a good approach to me (we can drop pcp-python then?  or make it a symlink
I guess, for back-compat with existing scripts in the wild).

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>