Open ptsl opened 1 year ago
wierd..... never seen that one before. Might be fixed by https://github.com/Almenon/AREPL-vscode/issues/439
In the meanwhile... does AREPL produce a log or something that I could send in to help understand the issue?
I've also noticed that in:
from arepl_dump import dump
the identifier arepl_dump
is not resolved, that is, it is underlined with a red wobbly line. Could it be connected to the problem somehow? (It definitely means that VSCode cannot see some stuff it should see.)
No log. If you want, you could try different versions of python and see what happens.
I've also noticed
No, not connected. The VSCode python extension doesn't like arepl_dump
because it's unaware that it's available in the context of AREPL. You can ignore the error.
This might be fixed if you update AREPL to v3 :)
If it's not fixed can you send me the code that reproduces the issue please?
Hi, thank you for the update and for your work on AREPL!
I’m not working with Python much at the moment, but when I get back to Python programming, I'll definitely let you know if I encounter the issue again.
Thanks again for all your hard work!
Bug: A strange traceback is produced with syntactically correct Python code.
How to reproduce: Sometimes I type in a syntactically valid Python code (which ends with
print(vars(myobj))
and the following traceback is produced. To get rid of the traceback, I just type any key (which makes the code syntactically incorrect), delete it with Backspace and whoa - the traceback disappears.Traceback:
Other Information (please complete the following information):