https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-296 Instrument control development <p>Sigh.</p> <p>Depending on the system and environment, python can mean python2 or python3. <a href="https://www.python.org/dev/peps/pep-0394/" class="external-link" rel="nofollow">PEP 394</a> recommends using python3 wherever you need to be explicit. Yes, in many environments (conda python=3; some new OSes) we can simply use python and always get python3. But that is not robust. Or we could maintain backward compatibility "forever", which we really do not want to do.</p> <p>Shebangs, various eups, MHS, ics_config, system scripts. This is related to <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-279" title="Change python3 for installation of eups/actors" class="issue-link" data-issue-key="INSTRM-279"><del>INSTRM-279</del></a>, which is for the ansible side of things.</p> <p>Deep sigh.</p> INSTRM-296

Change 'python' to 'python3' everywhere.

Task Normal Won't Fix Won't Fix Unassigned cloomis Wed, 21 Feb 2018 17:56:54 +0000 Mon, 14 Jan 2019 17:59:18 +0000 Mon, 14 Jan 2019 17:59:18 +0000 0 1 <p>this includes <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-280" title="bootstrap/eupsinstall fails to install on python3" class="issue-link" data-issue-key="INSTRM-280"><del>INSTRM-280</del></a>?</p> <p>Yes – this is a cover-all ticket we can use on all the products. Each product will only have a very few changes.</p> <p>a) this is mostly done, and b) who cares?</p> Relates INSTRM-280 Development Epic Link INSTRM-281 Rank 0|ii03xr: