You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you mean should we drop python 2 support and go to python 3 only, I don't think that's a good idea. It would mean every script would have to be transitioned to python 3 all at once, whereas supporting both will allow a more gradual port.
Activity
xylar commentedon Apr 17, 2019
If you mean should we drop python 2 support and go to python 3 only, I don't think that's a good idea. It would mean every script would have to be transitioned to python 3 all at once, whereas supporting both will allow a more gradual port.
xylar commentedon Apr 17, 2019
By the way, at least some COMPASS scripts do support python 3 as of:
#177
Also, there's a JIRA epic that I'm in charge of for converting the rest of COMPASS to support python 3.
xylar commentedon Apr 17, 2019
I believe this issue is largely redundant with #132 so I'm going to close it.
Merge PR #229 'xylar/ocean/update_compass_api_geom_feat_and_mesh_tool…
Merge PR MPAS-Dev#229 'xylar/ocean/update_compass_api_geom_feat_and_m…
v8.3.1-2.13: Update MPAS HRRR CI test for tempo v3 lookup tables (MPA…