New submission from Steve Dower: (Originally posted as a comment to issue26631 but confirmed separately.)
For 3.5.2 and 3.6.0a2, I updated the installer for the launcher so that it is always shared between Python versions (i.e. if you install 3.6 followed by 3.5, it won't touch the launcher because there's a "newer" one there). However, because this didn't make it into 3.6.0a1, there is actually a version conflict that breaks installation. I've marked this a deferred blocker for now and brought in the two RMs. I believe (and will test with the RCs) that this won't recur with the latest versions. It can also be easily worked around by choosing not to install the launcher. We haven't seen this before because there have been no supported "downgrade" scenarios (i.e. installing 3.5.0 over 3.5.1 aborts at the start, well before this error would be seen). ---------- assignee: steve.dower components: Windows messages: 268500 nosy: larry, ned.deily, paul.moore, steve.dower, tim.golden, zach.ware priority: deferred blocker severity: normal stage: test needed status: open title: Cannot install 3.5.2 with 3.6.0a1 installed type: behavior versions: Python 3.5, Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27314> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
