-
Notifications
You must be signed in to change notification settings - Fork 673
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
Editing code leads to unexpected token '<newline>' errors in error list #4835
Comments
It would be helpful if you could answer a few questions:
|
I have the same issue, each time that I create a new line appears the error. If I close the file and reopen the error dissapear. The version is: |
I have this problem as well There is a workaround as stated here: https://developercommunity.visualstudio.com/content/problem/374322/phantom-python-errors-in-vs-community-1588.html I replaced all occurrences of "TODO"with "TO DO". |
Now when a workaround has been identified, could this finally be fixed please? |
I couldn't reproduce the issue with |
Still an issue in 15.9.12 on Win7 64-bit with Python 2.7.14. How many months more before we get some kind of fix? VS2013 is a better editing environment at the moment....! |
How can this issue be closed with so many people reporting it? |
For me too working with replacing TODO with "TO DO". |
There seems to be a lot of punting this issue around and trying to close it without actually fixing it. Is this going to be fixed ever? |
I'm on VS Code and had a similar issue. Just spent half an hour commenting out lines to locate what I expected to be a missing parentheses. At the end, only four lines and imports where left. I could not for the life of me figure out why I was getting If there is shared code between the Python VS Code Extension and PTVS it might be related? Version: 1.37.1 |
This is exactly the kind of problem which makes working in an IDE very annoying on a daily basis - if it doesn't get fixed, people will start to look at alternatives as continually being reminded of having to add workarounds to your comments just to avoid the IDE telling you about non-existent syntax errors is a "grinding" bug in the UI - the kind which saps your enthusiasm for the whole product. |
I am facing the problem, while I want to do loads of caching data then the error getting....json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) |
Still very much facing this in the latest VS Code and after deleting and re-downloading the latest language server. On random but frequent (hourly or so) occassions during the day I get all kinds of phantom errors where a file just trips up as soon as I edit a single character after opening. languageServer Python Extension VS Code |
Thanks to everyone for these reports. @TiemenSch, could you please report your issue against the language server here: https://github.com/microsoft/python-language-server. PTVS is using an old language server (~2 years since the fork) so this is not the place to report issues with the new language server in VS Code. I'd move the issue over but want to keep the original issue open against PTVS. For those experiencing the original issue in Visual Studio, we are working on moving VS to use the new language server early in 2020, which should provide a considerably better experience. We are not fixing bugs in the old language server which is why there has been no movement on this. As a small team we have to decide where to focus our limited resources and we'd rather keep that focus on getting PTVS moved over to the LSP (language server protocol) and the new language server. We thank you for your patience. |
My apologies! I came here after multiple referencing issues and thought this was the one. Completely overlooked the switch in tooling. Thanks for the clear explanation and I'll head over straight away! |
PYVS editor is not usable in Visual Studio 2017 (15.8.9 and several previous versions). If I try to add a new code to existing code, it always throws syntax error (unexpected token).
The text was updated successfully, but these errors were encountered: