Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Python 3.x support #191

Closed
royalstream opened this issue Jan 21, 2016 · 8 comments
Closed

Python 3.x support #191

royalstream opened this issue Jan 21, 2016 · 8 comments
Assignees
Milestone

Comments

@royalstream
Copy link

Disclaimer: I scanned all the docs and the changelog for an answer but I couldn't find anything explicit.

Apparently Python 3.4 was supported up to version 0.9.0 (there's even a compat.py from 2014) but after that it seems like it was silently dropped. There's no mention about it in the changelog (did I miss it?). The new doc pages simply say Python 2.7 and I found new code (late 2015) using the old print.

Is this temporary? are compatibility-related contributions welcome or was it dropped for good?

@scttl
Copy link
Contributor

scttl commented Jan 21, 2016

Hi,

Yes restoring python 3.x support is definitely something on our radar, but hasn't yet made its way to the top of our TODO pile. We'd absolutely welcome compatibility related contributions, but would probably want to start with expanding our testing infrastructure to ensure things correctly build, all unit tests pass, and examples run across different python versions. We were using tox for this in the past, so that would probably be a good starting point.

@scttl scttl self-assigned this Jan 21, 2016
@scttl scttl added the question label Jan 21, 2016
@scttl scttl added this to the v1.3.0 milestone Jan 21, 2016
@royalstream royalstream changed the title Python 3.x support (question) Python 3.x support Jan 21, 2016
@royalstream
Copy link
Author

Got it! Thanks.

@untom
Copy link

untom commented Apr 12, 2016

It looks like v1.3.0 has come and gone without Python3 support making it into that release. Is there any time frame for when we can expect a Py3 compatible version of neon?

@scttl scttl removed this from the v1.3.0 milestone Apr 12, 2016
@scttl
Copy link
Contributor

scttl commented Apr 12, 2016

Hi,

Sorry we shuffled priorities around and I never got around to removing this from the v1.3.0 milestone on github (so this shouldn't have been closed). Since this task is currently on our internal backlog, I can't really provide an updated timeframe until the work is scoped and scheduled.

@scttl scttl reopened this Apr 12, 2016
@genghis88
Copy link

I was trying to use neon for a project. I ported my network from keras to neon and tried testing, and realized it wasn't working and that python3 is not supported. Supporting python3 is good for neon and for users like me. Can you give us an approximate time frame at least?

@raymondjplante
Copy link

After encountering Nervana at Boston Deep Learning Summit, I was interested in comparing to Keras + Theano, but lack of Python3 support is a non-starter. Hope you get a chance to move this up in the queue!

@ursk
Copy link
Contributor

ursk commented May 13, 2016

We are actively working on python 3 support right now, and it is going to come back soon. Thanks for your patience!

@jennifermyers jennifermyers added this to the v1.5.0 milestone Jun 23, 2016
@jennifermyers
Copy link
Contributor

Python3 support will be part of the imminent neon 1.5.0 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants