I mean once Python 2 is EOL requiring it for bootstrap might not be as
practical, and PyPy requiring itself to bootstrap would be doable but a bit
trickier.
On Tue, Jul 16, 2019, 3:35 AM William ML Leslie <
william.leslie@gmail.com> wrote:
>
>
> On Tue., 16 Jul. 2019, 2:34 pm Ryan Gonzalez,
... which is irrelevant in the context of RPython. Still, I wonder what’s the
long term plan is (if there’s already a plan): depend on PyPy2 indefinitely to
be able to translate PyPy3?
Sent from my iPad
> On 16. Jul 2019, at 19:51, Dan Stromberg wrote:
>
>
>> On Tue, Jul 16, 2019 at 1:35 AM
On Tue, Jul 16, 2019 at 1:35 AM William ML Leslie <
william.leslie@gmail.com> wrote:
>
>
> On Tue., 16 Jul. 2019, 2:34 pm Ryan Gonzalez, wrote:
>
>> I'm actually largely wondering if RPython is going to eventually move to
>> 3...
>>
>>>
>>>
> Significant effort, for what benefit exactly?
>
E
The plea for migration probably won’t be technically-based; plenty of shops
maintain special-case installations detached from the rest of the world. The
issue resides in general skills and available volunteers - the more specialized
the requirements, the less sustainable. Being 2-based requires
Nupic: https://github.com/numenta/nupic
There's a community edition that supports Python 3.x, but its license
may prove unsuitable to what we're doing.
On 7/15/19 4:57 PM, Matt Billenstein wrote:
What is the dependency?
m
On Mon, Jul 15, 2019 at 04:24:50PM -0700, Dan Stromberg wrote:
What
On Tue., 16 Jul. 2019, 2:34 pm Ryan Gonzalez, wrote:
> I'm actually largely wondering if RPython is going to eventually move to
> 3...
>
>>
>>
Significant effort, for what benefit exactly?
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.pytho
