AREPL not working at all
See original GitHub issuei keep getting the following error even for a simple print statement.
SyntaxError: invalid syntax
File "/home/****/.vscode/extensions/almenon.arepl-1.0.8/node_modules/arepl-backend/python/pythonEvaluator.py", line 164
raise StopIteration("There is no more input") from None
^
SyntaxError: invalid syntax
Python version is 3.6.6
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
AREPL extension error in VSCode with Python 3.7
When I start editing the code, instead of showing me the real time output, I get: 'py' is not recognized as an internal...
Read more >AREPL for python - Visual Studio Marketplace
Extension for Visual Studio Code - real-time python scratchpad.
Read more >arepl/Lobby - Gitter
I am using the python beautifulsoup 4.9.3 module installed in the environment using "from bs4 import BeautifulSoup". which works fine if I run...
Read more >Arepl NPM
Real-time evaluation: no need to run - AREPL evaluates your code automatically. You can control this (or even turn it off) in the...
Read more >arepl-backend - npm Package Health Analysis - Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages. License: MIT. Security Policy: No.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@talyaniv That error only happens with python 2. You have 3, sure, but arepl will only use the version you have configured in your path. Check python.pythonpath - what is that pointing too? And what is the value of arepl.pythonpath?
Yes, you were right. Can confirm that it’s fixed after setting my interpreter to use python 3. Awesome!