Deprecation Warnings

[thecolorblue]

I am running into some deprecation warnings when running this code in a notebook.

WARNING:tensorflow:<tensorflow.python.ops.rnn_cell.BasicLSTMCell object at 0x7f8745d1eef0>: Using a concatenated state is slower and will soon be deprecated.  Use state_is_tuple=True.

/home/condauser/anaconda3/lib/python3.5/site-packages/ipykernel/__main__.py:7: DeprecationWarning: converting an array with ndim > 0 to an index will result in an error in the future

I think these are causing the script to stop, as I am getting an InvalidArgument error later on.

I am on tensorflow 0.9.0rc0.

[RobRomijnders]

Correct.

The first warning is a known issue at the Tensorflow back-end
The second warning is because you write in Python 3

I think you can Google the Python 2 to Python 3 conversions and fix the
second warning yourself.
The first warning cannot cause in InvalidArgument

On 26 July 2016 at 12:28, Brad Davis notifications@github.com wrote:

I am running into some deprecation warnings when running this code in a
notebook.

WARNING:tensorflow:<tensorflow.python.ops.rnn_cell.BasicLSTMCell object at 0x7f8745d1eef0>: Using a concatenated state is slower and will soon be deprecated. Use state_is_tuple=True.

/home/condauser/anaconda3/lib/python3.5/site-packages/ipykernel/main.py:7: DeprecationWarning: converting an array with ndim > 0 to an index will result in an error in the future

I think these are causing the script to stop, as I am getting an
InvalidArgument error later on.

I am on tensorflow 0.9.0rc0.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the thread
https://github.com/notifications/unsubscribe-auth/APbLxRD5LpXeZrNE705B_dR9FdujP_aYks5qZeFVgaJpZM4JVARa
.

[thecolorblue]

Oh, didn't think of python 3. I was thinking it was an issue with my tensorflow version.

What is the best practices in python for major version support. Is it worth it to support python 2 and 3, maybe in separate branches?

[RobRomijnders]

Most of Python 2 is backwards compatible with Python 2. I think we can fix this error for good.

The error seems to be raised at line 7, so that concerns the import statements. Did you discard the
from __future__ statements? You already have Python 3, so you don;t need to import from future releases.

[thecolorblue]

Got it to run all the way through, but it looks like it affects jupyter in some way. I get some auto-save issues and usually have to re-start the docker container to run it again. I'll try to debug some more but it looks like it is working in python 3.

[RobRomijnders]

I made some major improvements. Does it work for you now?