Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Scott Kitterman writes: > We haven't started the transition yet. When it starts, binNMU should > be enough for most of the packages. When will you start the transition? -- Brian May

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

On November 28, 2015 7:21:57 PM EST, Brian May wrote: >Ben Finney writes: > >> API/ABI transitions (such as switching default Python 3 to be PYthon >> 3.5) are managed by the release team, with a workflow described at >> https://wiki.debian.org/Teams/ReleaseTeam/Transitions>. > >There is https:

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Ben Finney writes: > API/ABI transitions (such as switching default Python 3 to be PYthon > 3.5) are managed by the release team, with a workflow described at > https://wiki.debian.org/Teams/ReleaseTeam/Transitions>. There is https://release.debian.org/transitions/html/python3.5.html Still tryi

Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Brian May writes: > However I don't know much about this Python 3.5 transition, or what > the current waiting point is. API/ABI transitions (such as switching default Python 3 to be PYthon 3.5) are managed by the release team, with a workflow described at https://wiki.debian.org/Teams/ReleaseTea