[INSTRM-296] Change 'python' to 'python3' everywhere. Created: 22/Feb/18 Updated: 15/Jan/19 Resolved: 15/Jan/19 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | ICS-PY3 | ||||||||
| Description |
|
Sigh. Depending on the system and environment, python can mean python2 or python3. PEP 394 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. Shebangs, various eups, MHS, ics_config, system scripts. This is related to Deep sigh. |
| Comments |
| Comment by shimono [ 22/Feb/18 ] |
|
this includes |
| Comment by cloomis [ 22/Feb/18 ] |
|
Yes – this is a cover-all ticket we can use on all the products. Each product will only have a very few changes. |
| Comment by cloomis [ 15/Jan/19 ] |
|
a) this is mostly done, and b) who cares? |