View Issue Details

IDProjectCategoryView StatusLast Update
0005710SUMoBugpublic2019-10-24 20:48
Reporterumuench Assigned ToKyle_Katarn  
PrioritylowSeverityminorReproducibilityalways
Status feedbackResolutionopen 
Product Version5.9.9 
Target VersionLong term 
Summary0005710: Python Version
DescriptionDiffent Environments
2.7
3.5
3.6
3.7
3.8
...
--->e.g.: Update from 3.7.4 to 3.7.5 (correct) but from 3.7.4 to 3.8.0 (not correct)
Steps To Reproducehttps://www.python.org/downloads/release/python-2717/
https://www.python.org/downloads/release/python-380/

...
Tagsversion

Activities

umuench

2019-10-20 18:50

reporter  

20-10-_2019_18-16-26.png (367,521 bytes)

wolf

2019-10-21 14:44

reporter   ~0003737

Why should an update of version 3.7.4 to 3.8 not be correct?

And how does SUMo handle your 2.7 Python environment?

I'm aware that these different product lines (Python 2 and Python 3) shouldn't be mixed. A change is a migration not an update. But I'm not aware of such issues within the Python 3 product line.

It is already known that current SUMo implementation is limited in handling publishers update policies with concurrant product lines with some idead pronounced to address some (more) policies in the future. Such changes will require fundamental redesign and major version change of SUMo. And isn't end of development resp. support of Python 2 already announced for 1st January 2020, declaring version 2.7.17 as penultimate version?

Issue History

Date Modified Username Field Change
2019-10-20 18:50 umuench New Issue
2019-10-20 18:50 umuench Tag Attached: version
2019-10-20 18:50 umuench File Added: 20-10-_2019_18-16-26.png
2019-10-21 14:44 wolf Note Added: 0003737
2019-10-24 20:48 Kyle_Katarn Assigned To => Kyle_Katarn
2019-10-24 20:48 Kyle_Katarn Status new => feedback
2019-10-24 20:48 Kyle_Katarn Target Version => Long term