Re: Obsolescence Python 3.5 support plan

2020-06-10 Thread Frank Crawford
On Wed, 2020-06-10 at 07:31 +0200, Eric L. Zolf wrote: > Hi Derek, > > On 09/06/2020 16:24, Derek Atkins wrote: > > EricZolf writes: ... > Nothing is impossible, the question is rather how much effort you put > into it. > > You can find zillions of explanations on the web about what happened >

Re: Obsolescence Python 3.5 support plan

2020-06-09 Thread Eric L. Zolf
Hi Derek, On 09/06/2020 16:24, Derek Atkins wrote: > EricZolf writes: > >> Actually, while writing this e-mail, I checked the code and noticed that >> it's enforcing pickle version 1 so the issue isn't the pickle protocol, >> the issue is solely the bytes vs. str vs. unicode change between

Re: Obsolescence Python 3.5 support plan

2020-06-09 Thread Derek Atkins
EricZolf writes: > Actually, while writing this e-mail, I checked the code and noticed that > it's enforcing pickle version 1 so the issue isn't the pickle protocol, > the issue is solely the bytes vs. str vs. unicode change between python > 2 and 3. There is not much we could have done about it

Re: Obsolescence Python 3.5 support plan

2020-06-07 Thread EricZolf
Hi, On 06/06/2020 14:07, Frank Crawford wrote: > On Thu, 2020-06-04 at 09:44 -0400, Derek Atkins wrote: >> So long as there isn't a client-server wire-format incompatiblity >> with >> older 2.x versions, I don't care! (I want to ensure we never make >> that >> same mistake again of a wire

Re: Obsolescence Python 3.5 support plan

2020-06-06 Thread Frank Crawford
On Thu, 2020-06-04 at 09:44 -0400, Derek Atkins wrote: > EricZolf < > ewl+rdiffbac...@lavar.de > > writes: > > [snip] > > Any comments on those plans? > > So long as there isn't a client-server wire-format incompatiblity > with > older 2.x versions, I don't care! (I want to ensure we never make

Re: Obsolescence Python 3.5 support plan

2020-06-04 Thread Derek Atkins
EricZolf writes: [snip] > Any comments on those plans? So long as there isn't a client-server wire-format incompatiblity with older 2.x versions, I don't care! (I want to ensure we never make that same mistake again of a wire incompatibility due to a change in underlying tooling). > KR, Eric

Obsolescence Python 3.5 support plan

2020-06-04 Thread EricZolf
Hi, from a past survey, we know that some of you still use Python 3.5, but we'd like sooner or later to get rid of it and wanted to ask you if there is a _big_ issue with it. Here the reasons for the foreseen move: - Python 3.5 is out-of-support by 13th of September according to [1] - The