Control: notforwarded -1 Control: forwarded -1 https://release.debian.org/transitions/html/python3.6-supported.html
On 29/06/17 08:35, Matthias Klose wrote: > On 28.06.2017 23:46, Scott Kitterman wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian....@packages.debian.org >> Usertags: transition >> >> We would like to add python3.6 as a supported python3 version along with >> python3.5. This is not exactly like a normal transition. Only transient >> unbuildability of higher level packages is to be expected. >> >> As usual, we are planning a three step transition from python3.5 to >> python3.6. >> >> Adding python3.6 as supported is first. >> >> Once that is complete, we'll file another request to make python3.6 the >> default python3. This step does not need to immediately follow the first. >> >> After that, we'll drop python3.5 as a supported version (other than needing a >> tracker, that step doesn't need any support from the release team and won't >> entangle anything as buildability of packages is not implicated). >> >> Ben file: >> >> title = "python3-defaults"; >> is_affected = .depends ~ "python3-all-dev"; >> is_good = .depends ~ "python3 (<< 3.7)"; >> is_bad = .depends ~ "python3 (<< 3.6)"; > > this doesn't catch the embedded python interpreters. > > is_good = .depends ~ /python3 \(<< 3\.7\)/ | .depends ~ /(lib)?python3\.6/; > is_bad = .depends ~ /python3 \(<< 3\.6\)/ | (.depends ~ /(lib)?python3\.5/ & ! > .depends ~ /(lib)?python3\.6/) | .breaks ~ /python \(>= 3\.6\)/; > > should do the job. My bad, I reused the python3.5 tracker, which had been updated from python3.5-supported to python3.5-default. I have updated the python3.6 tracker now, and renamed it to avoid this sort of confusion next time. Cheers, Emilio
