| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates: python3 work |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Mon, 23 Feb 2015 09:54:16 -0500 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <763423700.13212590.1424688941302.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Mon, 23 Feb 2015 05:55:41 -0500 (EST)") |
| References: | <368618270.13212567.1424688934926.JavaMail.zimbra@xxxxxxxxxx> <763423700.13212590.1424688941302.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
> [...] > Nathan Scott (2): > python3: on-going work to support both python 2 and 3 > [...] Thank you. What are your thoughts about the longevity of this approach (conditionally rewriting the #! line of python scripts)? If only the build (or package-construction) scripts do rehashbanging, developers/qa may not see how to easily test that any given script source is and stays workable in both python languages. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: python3 work, Nathan Scott |
|---|---|
| Next by Date: | Re: Pointing pcp to alternative location for papi, Frank Ch. Eigler |
| Previous by Thread: | pcp updates: python3 work, Nathan Scott |
| Next by Thread: | Re: pcp updates: python3 work, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |