pcp
[Top] [All Lists]

Re: python3 woes on f22

To: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Subject: Re: python3 woes on f22
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 16 Jul 2015 06:46:16 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <55A74A08.5010103@xxxxxxxxxx>
References: <5594A1B5.5090003@xxxxxxxxxx> <227885808.37023848.1436780775020.JavaMail.zimbra@xxxxxxxxxx> <y0my4ikulyq.fsf@xxxxxxxx> <955515466.37555879.1436847748465.JavaMail.zimbra@xxxxxxxxxx> <20150714115711.GG22361@xxxxxxxxxx> <305121480.38738777.1436917670865.JavaMail.zimbra@xxxxxxxxxx> <y0mvbdltum7.fsf@xxxxxxxx> <55A74A08.5010103@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: nx+A+HL3agzu9MSmKvkrYY2wrkmbIg==
Thread-topic: python3 woes on f22

----- Original Message -----
> >> [...]
> In the interests of resolving the original issue during development,
> I've merged this change from Nathan's tree. If the outcome of this
> discussion warrants additional changes, then they can be in follow up
> commits.

Thanks Mark - I can see no valid argument for further change here.

> One additional nit I have is that python scripts specifying pcp-python
> as the interpreter might benefit from a short comment saying the wrapper
> is there to use the default python interpreter for the platform, not
> because we've brewed our own special python and called it python-pcp!
> 

Yeah, I thought about that too - then realised its alot of python scripts
we'd need to mirror that comment through (and forever-more, for new ones
too).  So, I went with alot of detail in the man page instead, to keep it
all in one place - hopefully curious people will find that.

cheers.

--
Nathan

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