Re: Python 3.6 in stretch

On Mon, 09 Jan 2017 23:02:42 +, Simon McVittie wrote: > (I'm increasingly of the opinion that semver is an over-simplification > that fails on contact with the real world - in particular, if foo 1.2.3 > is in a stable branch of a larger environment like Debian, you fix 17 > minor bugs and

Re: Python 3.6 in stretch

On Jan 09, 2017, at 02:28 PM, Michael Lustfield wrote: >Python uses the microversion position for this. More importantly... is this >really a point that matters? Not really. In Debian terms you might think about the first digit as an epoch, the second digit as a major version and the third

Re: Python 3.6 in stretch

On Mon, 09 Jan 2017 at 14:28:07 -0800, Michael Lustfield wrote: > If 3.5 to 3.6 was a typical "minor version," our expectation > would be that the update comes with security updates and bug fixes > (not feature changes). That isn't semver. Semver minor version increments add features in a

Re: Python 3.6 in stretch

On Mon, Jan 9, 2017 at 1:54 PM, Ben Finney wrote: > Adam Borowski writes: > >> On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: >> > Andrey Rahmatullin writes: >> > >> > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo

Re: Python 3.6 in stretch

Adam Borowski writes: > On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: > > Andrey Rahmatullin writes: > > > > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > > > Thanks for the info, didn't know that the transition freeze

Re: Python 3.6 in stretch

Adam Borowski writes: > On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: >> Galbo is referring correctly to the minor version, as specified in >> and Semantic Versioning >> . >> So, “3.5.3” →

Re: Python 3.6 in stretch

On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: > Andrey Rahmatullin writes: > > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > > Thanks for the info, didn't know that the transition freeze was actually > > > the version freeze for minor

Re: Python 3.6 in stretch

Andrey Rahmatullin writes: > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > Thanks for the info, didn't know that the transition freeze was actually > > the version freeze for minor versions of Python. > A minor version upgrade would be 3.5.3 -> 3.5.4. 3.5

Re: Python 3.6 in stretch

On 08.01.2017 17:27, Lars Wirzenius wrote: > On Sun, Jan 08, 2017 at 04:58:01PM +0100, Galbo Branbert wrote: >> I couldn't find any official statement if Python 3.6 will be the default >> interpreter in stretch (as it was the current stable when the soft freeze >> happened it should be, right?) >

Re: Python 3.6 in stretch

On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > Thanks for the info, didn't know that the transition freeze was actually > the version freeze for minor versions of Python. A minor version upgrade would be 3.5.3 -> 3.5.4. 3.5 -> 3.6 is a lot of changes. -- WBR, wRAR

Re: Python 3.6 in stretch

Thanks for the info, didn't know that the transition freeze was actually the version freeze for minor versions of Python. (and that 3.6 is not in Stretch, oops) For the next version of Debian it would be nice to know the version that will be included in the 'Bits from the Stable Release Managers'

Re: Python 3.6 in stretch

On Sun, Jan 08, 2017 at 06:27:57PM +0200, Lars Wirzenius wrote: > Python 3.6 isn't even in experimental yet This bit was wrong. 3.6 is in experimental. That doesn't change my point about a transition being too late now, however. -- I want to build worthwhile things that might last. --joeyh

Re: Python 3.6 in stretch

On Sun, Jan 08, 2017 at 04:58:01PM +0100, Galbo Branbert wrote: > I couldn't find any official statement if Python 3.6 will be the default > interpreter in stretch (as it was the current stable when the soft freeze > happened it should be, right?) Python 3.6 was released 23 December. The stretch

Re: Python 3.6 in stretch

On Sun, Jan 08, 2017 at 04:58:01PM +0100, Galbo Branbert wrote: > I couldn't find any official statement if Python 3.6 will be the default > interpreter in stretch (as it was the current stable when the soft freeze > happened it should be, right?) python3.6 is not even in sid so no. -- WBR, wRAR

Python 3.6 in stretch

I couldn't find any official statement if Python 3.6 will be the default interpreter in stretch (as it was the current stable when the soft freeze happened it should be, right?) Some reasons for it: (https://docs.python.org/3/whatsnew/3.6.html) -)SHA-3, formatted string literals, file system path