GuardedhandshakeState might throw an error on py2 if future is installed #1
Comments
tgalal
added a commit
that referenced
this issue
Apr 24, 2019
refs #1 GuardedhandshakeState might throw an error on py2 if future is installed On python2 if 'future' was globally installed, transitions lib will successfully do a "from builtins import object" eventhough it seems intended for py3 only. This imported object in py2 already has a 'next()' method, causing a conflict with 'next' that is defined as a state action/transition and raises a 'TypeError: newobject is not an iterator'
|
fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On python2 if 'future' was globally installed or accessible by dissononce, transitions lib will successfully do a
from builtins import objecteventhough it seems intended for py3 only. This imported object in py2 already has anext()method, causing a conflict with 'next' that is defined as a state action/transition and raises aTypeError: newobject is not an iteratorThe text was updated successfully, but these errors were encountered: