Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syntax error when making atomizer from cloned repo #1

Closed
ryants opened this issue May 4, 2016 · 4 comments
Closed

syntax error when making atomizer from cloned repo #1

ryants opened this issue May 4, 2016 · 4 comments

Comments

@ryants
Copy link

ryants commented May 4, 2016

When I run "make" in the top directory I get the following error:

1993 ERROR: invalid syntax (async.py, line 16)
Traceback (most recent call last):
  File "/auto/nest/nest/u/ryants/tools/atomizer/pyinstaller2/PyInstaller/depend/owner.py", line 110, in getmod
    co = compile(stuff.replace("\r\n", "\n"), py[0], 'exec')
  File "async.py", line 16
    transport, pw = yield from asyncio.get_event_loop()\
                             ^
SyntaxError: invalid syntax
make: *** [all] Error 10

I am using Ubuntu 12.04 LTS if that helps troubleshoot at all

@jjtapia
Copy link
Member

jjtapia commented May 6, 2016

Hello,

The error is because of some changes they did in one of the atomizer's dependencies that makes it incompatible with Python 2.7, pexpect in particular.You can check the requirements.txt file for the particular version of pexpect atomizer needs (along with other dependencies)

If you already have pexpect installed you can do

$ pip uninstall pexpect
$ pip install pexpect=3.3

Thanks for the note by the way, I'll add this to the installation notes.

@ryants
Copy link
Author

ryants commented May 6, 2016

Thanks for the tip. If I switch to Python 3.x will that prevent me from having to downgrade pexpect? (I would test it myself, but I'm away from my work machine!)

@jjtapia
Copy link
Member

jjtapia commented May 6, 2016

Atomizer is not Python 3 compatible as of this moment. An alternative solution would be to upgrade the version of pip so that it can deal with the non compatible elements in the package (as reported here) however I haven't tested this solution myself.

@jjtapia
Copy link
Member

jjtapia commented Aug 9, 2016

This error was addressed by installing the dependencies in a Python virtualenv

@jjtapia jjtapia closed this as completed Aug 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants