Hi Everyone,
the python3 support poll has run its on
https://twitter.com/ossronny/status/1043837215175057408
The results have a interesting shape.
37% now
09% with 3.4 mid 2019
38% with the python 2.7 eol
16% a year after py 2.7 eol
468 votes in the final result.
Its my belief tha
Hi everyone,
yesterday i tried yet again to reshape node structure to allow the
integration of function-definition.
every time i work with something around those structures it becomes
apparent, that its immensely fragile to work within it with backward
compat in mind,
its so deeply cross-related t
Hi Ronny,
On Mon, Oct 1, 2018 at 5:01 AM RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hi Everyone,
>
> the python3 support poll has run its on
> https://twitter.com/ossronny/status/1043837215175057408
>
> The results have a interesting shape.
>
> 37%now
> 09%with 3.4 mid
Hi Bruno,
Am Montag, den 01.10.2018, 08:13 -0300 schrieb Bruno Oliveira:
> Hi Ronny,
>
> On Mon, Oct 1, 2018 at 5:01 AM RonnyPfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
> > Hi Everyone,
> >
> >
> >
> > the python3 support poll has run its on
> >
> > https://twitter.com/ossronny/s
On Mon, Oct 1, 2018 at 8:22 AM Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
>
> In the plan i outlined, the first python 3 only release would be the one
> that drops 3.4 mid-2019 - at that point in time the maintenance branch
> would be prepared before release merge time.
>
I see,
Hi Ronny,
>From my POV breaking those internal APIs slowly and with warnings in place
is fine, just like it was done with the "marks" API.
I suspect that the internal Node creation API sees even less usage than
marks, so I think it is fine to break it slowly and with proper warnings in
place.
On
