Windows 10: Python Unexpected Token Syntax Error in Visual Studio Code

Incntr0l · Mar 6, 2019

G'day everyone,

I have been using Python through the IDLE shell for a few months now before moving to VSCode for easier use and adding it to a Git repo without having to use Git Bash. Yesterday I was doing some practice with Read/Write file and everything was going smoothly, I could read the file I had made and everything. This morning though, I ran into a bit of trouble and I cannot seem to fix it.

Each time I try and run the script just for reading a test file, it comes back with a "Syntax error near unexpected token" for open curved bracket '(' and the "*.read()" (* being the file name). Below is a small snip of the code I have done.

I run that and it comes back with the Syntax error:

It is the same for the response to the print line (shown below), saying that there is an unexpected token but there is none that I can see.

I do not know what to do to fix this, I had a look around the web and couldn't find anything. If anyone knows how to fix this, please let me know.

:)

Brink · Mar 6, 2019

Python in Visual Studio Code - January 2019 Release

We are pleased to announce that the January 2019 release of the Python Extension for Visual Studio Code is now available. You can download the Python extension from the Marketplace, or install it directly from the extension gallery in Visual Studio Code. You can learn more about Python support in Visual Studio Code in the documentation.

In this release we have closed a total of 62 issues, including:

IPython console support in the Python Interactive window

Support for running an entire file in the Python Interactive window

Problems for failed tests when using pytest (thanks Chris NeJame)

Much faster outline when using the Python Language Server

Keep on reading to learn more!
Click to expand...

Read more: Python in Visual Studio Code Python at Microsoft

Brink · Mar 6, 2019

Python Extension for Visual Studio Code - March 2018 Release

We are pleased to announce that the March 2018 release of the Python Extension for Visual Studio Code is now available from the marketplace and the gallery. You can the download the Python extension from the marketplace, or install it directly from the extension gallery in Visual Studio Code. You can learn more about Python support in Visual Studio Code in the VS Code documentation.In this release have closed a total of 61 issues which make the Preview debugger easier to try out, and includes various fixes and enhancements.

Improvements to Preview Debugger

In the February release of the extension we made a Preview of version of our debugger available demonstrating faster debugging performance but limited feature support. In this release we have added further enhancements to the preview.

Debug configurations have been added for more app types: Django, PySpark, Pyramid, Watson, and Scrapy. The preview debugger is also now bundled with the extension so you no longer need to manually install ptvsd to try it out, simply add one of the Experimental Debugger configurations and start debugging:

We’ve also added support for Django template debugging, you can set breakpoints in a Django app and view variables in the templates:

We’ve also added the following capabilities:

Support for debugging unit tests

Jinja template debugging support for apps other than Flask

Various Fixes and Enhancements

We have also fixed several small enhancements and fixed issues requested by users that should improve your experience working with Python in Visual Studio Code. The full list of improvements is listed in our changelog, some notable issues are:

Pipenv improvements: added the ability to read Pipfile name from the environment variable (#999), development-time packages are installed into dev-packages (#1110)

Add support for the "it" locale #1152

Improved extension load time #931

Unit test discovery banner is suppressed when test discovery failure is caused by syntax errors in test code #704

Conda installer is not used in non-conda environments #969

Prevent extension from displaying the wrong interpreter #981

Fixed high CPU Usage in wmic process on Windows #1036

Stop autocomplete from appearing in comments #1123

Be sure to download the Python extension for VS Code now to try out the above improvements. If you run into any issues be sure to file an issue on the Python VS Code GitHub page.
Click to expand...

Source: Python in Visual Studio Code – March 2018 Release Python Engineering at Microsoft

Brink · Mar 6, 2019

Python in Visual Studio Code - May 2018 Release

We are pleased to announce that the May 2018 release of the Python Extension for Visual Studio Code is now available from the marketplace and the gallery. You can download the Python extension from the marketplace, or install it directly from the extension gallery in Visual Studio Code. You can learn more about Python support in Visual Studio Code in the VS Code documentation.

In this release we have closed a total of 103 issues including support for the new and popular formatter Black, improvements to the experimental debugger and formatting as you type.

Support for Black Formatter

Black is a new code formatting tool for Python that was first released in March and has quickly gained popularity. Black has a single opinion about how Python code should be formatted, allowing you to easily achieve consistency across your codebase. The Python extension now supports using it as a formatter.

To enable the Black formatter, go into File > User Preferences > Settings, and put the following setting in your User Settings (for settings for all workspaces) or Workspace settings (for the current workspace/folder).

"python.formatting.provider": "black"

Then run the VS Code command “Format Document”. You will get a prompt to install the Black formatter:

Selecting Yes will install Black into the currently selected interpreter in VS Code. Once black has finished installing, you will need to run the Format Document command again to format your document.

In the below code example, we can see that black adds a blank line before functions, spaces around equals signs, and uses double quotation marks instead of single quotation marks:

If you want formatting to happen automatically when hitting save, you can add the following setting:

"editor.formatOnSave": true

If you want to format Python 2.7 code, Black will need to run in a Python 3 environment. In that case, you can install black using python3 –m pip install –upgrade black into a Python 3 interpreter/environment of your choice, and then set the python.formatting.blackPath setting to point to the black command that was installed (on UNIX-based OSs you can typically find this with the command which black).

Various Fixes and Enhancements

We have also added small enhancements and fixed issues requested by users that should improve your experience working with Python in Visual Studio Code. The full list of improvements is listed in our changelog, some notable improvements are:

Improvements to testing: added a ‘Discover Unit Tests’ command (#1474) for discovering unit tests, removed error in the output window when running tests (#1529)

Improvements to the Experimental Debugger: auto-enable jinja template debugging on *.jinja and *.j2 files (#1484), ensure debugged program is terminated when Stop debugging button is clicked. (#1345), support for attach/detach (#1255)

Fixed syntax errors caused when using the editor.formatOnType setting is enabled (#1799)

Ensure python environment activation works as expected within a multi-root workspace. (#1476)

Fixed flask debugging configurations so that they work with the latest versions of flask (#1634)

Ensure the display name of an interpreter does not get prefixed twice with the words Python. (#1651)

`Go to Definition` now works for functions which have numbers that use `_` as a separator (as part of our Jedi 0.12.0 upgrade). (#180)

Fixed rename refactor issue that removes the last line of the source file when the line is being refactored and source does not end with an EOL. (#695)

Be sure to download the Python extension for VS Code now to try out the above improvements. If you run into any issues be sure to file an issue on the Python VS Code GitHub page.
Click to expand...

Source: Python in Visual Studio Code - May 2018 Release Python at Microsoft

Windows 10: Python Unexpected Token Syntax Error in Visual Studio Code

Python Unexpected Token Syntax Error in Visual Studio Code

Python Unexpected Token Syntax Error in Visual Studio Code

Python Unexpected Token Syntax Error in Visual Studio Code

Python Unexpected Token Syntax Error in Visual Studio Code - Similar Threads - Python Unexpected Token

Visual Studio Code C++ Syntax Highlighting Include Path

Visual Studio Code C++ Syntax Highlighting Include Path

Visual Studio Code C++ Syntax Highlighting Include Path

Visual Studio code says my Python code is ALL RIGHT, but...

Visual Studio code says my Python code is ALL RIGHT, but...

Visual Studio Python

Python in Visual Studio Code - January 2019 Release

Python in Visual Studio Code - May 2018 Release

Python Extension for Visual Studio Code - March 2018 Release

Users found this page by searching for:

unexpected token python visual studio

unexpected token player_1python(parser-16)

unexpected token en pyton