Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-375

Change default python version in newinstall and lsstsw to Python3 for v14

    Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM
    • Labels:
      None

      Description

      I propose that we change the default version of python 3 that is installed via newinstall or bin/deploy to be Python3. I would like this to be done for the v14 release so that we can make a statement that this is where we are heading. The release notes should absolutely state how to use python2 for a build. We regularly use python3 now and Jenkins has been testing it for ages and sims builds fine.

      This is not talking about removing python2. I am just saying that in the absence of any options given to these commands we should use python3.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            On a related note, for version 14.0 I would like us to include a timeline for dropping Python2 support from Science Pipelines so that the community can understand what we are doing and so that developers understand the schedule.

            Show
            tjenness Tim Jenness added a comment - On a related note, for version 14.0 I would like us to include a timeline for dropping Python2 support from Science Pipelines so that the community can understand what we are doing and so that developers understand the schedule.
            Hide
            pschella Pim Schellart [X] (Inactive) added a comment -

            +1, and it would be nice if we could have a binary install by default too (but that may be a separate RFC).

            Show
            pschella Pim Schellart [X] (Inactive) added a comment - +1, and it would be nice if we could have a binary install by default too (but that may be a separate RFC).
            Hide
            athornton Adam Thornton added a comment -

            This will make the JupyterLab component of the Science Platform slightly simpler; the weeklies have been defaulting to Python 3 for some time, so I think it's a good idea.

            Show
            athornton Adam Thornton added a comment - This will make the JupyterLab component of the Science Platform slightly simpler; the weeklies have been defaulting to Python 3 for some time, so I think it's a good idea.
            Hide
            hchiang2 Hsin-Fang Chiang added a comment -

            Does this mean the shared stacks on lsst-dev:/software and /ssd will become Python 3 on the same timescale? Or will that depend on something else?

            Show
            hchiang2 Hsin-Fang Chiang added a comment - Does this mean the shared stacks on lsst-dev:/software and /ssd will become Python 3 on the same timescale? Or will that depend on something else?
            Hide
            tjenness Tim Jenness added a comment -

            Switching the shared stack to Python3 is on the list for this year but not related to this RFC.

            Show
            tjenness Tim Jenness added a comment - Switching the shared stack to Python3 is on the list for this year but not related to this RFC.
            Hide
            tjenness Tim Jenness added a comment -

            We were going to switch the stack to Python3 when we switched to devtoolset-6 but RFC-332 is blocked on the demo failing.

            Show
            tjenness Tim Jenness added a comment - We were going to switch the stack to Python3 when we switched to devtoolset-6 but RFC-332 is blocked on the demo failing.
            Hide
            Parejkoj John Parejko added a comment -

            +1: a great idea.

            Show
            Parejkoj John Parejko added a comment - +1: a great idea.
            Hide
            swinbank John Swinbank added a comment - - edited

            For what it's worth, I don't see why switching shared stacks to Python 3 should be coupled to using devtoolset-6 (except that it could save a little effort if we were to change everything at once).

            Show
            swinbank John Swinbank added a comment - - edited For what it's worth, I don't see why switching shared stacks to Python 3 should be coupled to using devtoolset-6 (except that it could save a little effort if we were to change everything at once).
            Hide
            tjenness Tim Jenness added a comment -

            John Swinbank I agree. It's a bit less work but they are independent decisions.

            Show
            tjenness Tim Jenness added a comment - John Swinbank I agree. It's a bit less work but they are independent decisions.
            Hide
            rowen Russell Owen added a comment - - edited

            +1 seems like a great time to make this change

            Show
            rowen Russell Owen added a comment - - edited +1 seems like a great time to make this change
            Hide
            tjenness Tim Jenness added a comment -

            No complaints. Adopting. I've opened pull requests for the minor changes.

            Show
            tjenness Tim Jenness added a comment - No complaints. Adopting. I've opened pull requests for the minor changes.

              People

              • Assignee:
                tjenness Tim Jenness
                Reporter:
                tjenness Tim Jenness
                Watchers:
                Adam Thornton, Frossie Economou, Hsin-Fang Chiang, John Parejko, John Swinbank, Jonathan Sick, Joshua Hoblitt, Pim Schellart [X] (Inactive), Russell Owen, Steve Pietrowicz, Tim Jenness
              • Votes:
                1 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Planned End:

                  Summary Panel