Python 3.x support

[breznak]

reference for @oxtopus PR: #2377 where he already did lot of work!

• translation with python 2to3 tool
• use python -3 to hint incompatible parts for 2to3

[breznak]

ups, I've missed #2378 already

[rcrowder]

@breznak No, this issue is good. And ties in with numenta/nupic.core-legacy#567 where this work is due to occur first.

[rhyolight]

There are folks working on a fork of this repository that will be python 3 compatible at https://discourse.numenta.org/t/python-3-migration/3228/

[rhyolight]

@ObadaJabassini see my comment about the fork above.

[impredicative]

Any update for an estimated release date for Python 3? Python 2 support and compatibility soon won't be necessary. This migration is holding up adoption of nupic. It is just mind boggling why this migration has to be a community effort and not a core Numenta effort.

[oxtopus]

Heard. Numenta fired everyone working on it and deprioritized anything not directly related to "research". If you want Python 3 support, I suggest looking for alternatives or doing it yourself.

…

On Tuesday, June 12, 2018, Ouroboros Chrysopoeia ***@***.***> wrote: Any update for an estimated release date for Python 3? Python 2 support and compatibility soon won't be necessary. This migration is holding up adoption of nupic. It is just mind boggling why this migration has to be a community effort and not a core Numenta effort. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2506 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAT7gEwv9pBABbWGyTOCkdi8rXNyKXeMks5t8DKUgaJpZM4Fy2IU> .

[ghost]

Lol @ people waiting for Python 3, can't spend 10 seconds using virtualenv to create python 2.7 environment

[impredicative]

@kyle-sorensen It is not about creating a virtualenv; that's easy. It's about integrating with other code that's already in Python 3. Also, one useful thing that I cannot do in Python 2 is write "type annotations" (except as informal comments).

More importantly, Python 2 is about to expire in 1.5 years. Python 3 has been out since 2008. The delay in migration is jeopardizing adoption of the project. Wasn't a goal of Jeff H. to let a thousand flowers bloom? Well they're withering right now. If the goal is to work in a silo, I think even Vicarious can do that.

Cc: @subutai @cbaranski

[rhyolight]

@impredicative The mission of Numenta is twofold:

1. To understand how intelligence works in the mammalian brain.
2. To implement those principles in non-biological systems

I understand your frustration that NuPIC is out of date, but our priorities put research ahead of software updates for the community at this time. At some point in the future, we will likely cycle back into a software applications implementation mode, at which point it might make sense for us to dedicate engineering resources to migrating to python 3.

---

Wasn't a goal of Jeff H. to let a thousand flowers bloom? Well they're withering right now. If the goal is to work in a silo, I think even Vicarious can do that.

This is not about one implementation of HTM. This is about HTM theory. As I have said many times, I don't think NuPIC is going to be the HTM implementation the takes the world by storm. I want people to understand the concepts behind HTM so they can build their own systems based upon the principles of intelligence we have uncovered.

[impredicative]

It would seem that the current status is to provision NuPIC using PyTorch, as in the project https://github.com/numenta/nupic.torch