Closed heather999 closed 8 years ago
We did have a Twinkles issue on this already, https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/209, and the outcome of that was to run pylint --py3k
on the python scripts in the travisc-ci builds to ensure python 3 compliance. Do we need to do more? I guess I would ask @rbiswas4 or @danielsf about the DM plans and how they would affect us beyond what we've done so far.
I'm also thinking about software installations and when it is appropriate for us to make the move to python 3. Do we expect phosim will support py 3 on the same time scale as DM? @TomGlanzman should feel free to chime in too.
Assuming our code is python 3 compatible, I see no reason not to move to the python 3 version of the Stack as soon as it is available.
The lsst_sims stack is not yet python 3 compatible. We have planned our work for FY2017. Supporting python 3 is on there, but it is not a high priority. My guess would be that having lsst_sims ready for python 3 by the hack week is not realistic, but I could be wrong.
Thanks, @danielsf & @jchiang87 Closing this issue. It might be helpful to keep track of when the sims are py3-ready so we can transition at the right time.
Tom and I were chatting.. it sounds like DM is poised to move to python 3. Are we ready? It would be nice to take advantage of the Hack Week to pick an expert's brain. We can add a new hack to the growing list on Confluence - but I'd like to hear some confirmation this is useful, and an idea of who to target as an "expert". Thoughts @jchiang87, @tony-johnson, @drphilmarshall?