<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Visual Studio Code on Dieter Vansteenwegen / Boxfish</title><link>https://boxfish.be/tags/visual-studio-code/</link><description>Recent content in Visual Studio Code on Dieter Vansteenwegen / Boxfish</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 06 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://boxfish.be/tags/visual-studio-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up Visual Studio Code for Python development (on Linux)</title><link>https://boxfish.be/posts/20210906-setting-up-visual-studio-code-for-python-development-on-linux/</link><pubDate>Mon, 06 Sep 2021 00:00:00 +0000</pubDate><guid>https://boxfish.be/posts/20210906-setting-up-visual-studio-code-for-python-development-on-linux/</guid><description>&lt;blockquote>
&lt;p>Update January 2024:&lt;/p>
&lt;p>I don&amp;rsquo;t use many of the separate tools for linting/refactoring/formatting anymore in favour of &lt;a href="https://github.com/astral-sh/ruff" target="_blank" rel="noopener">Ruff&lt;/a>.&lt;/p>
&lt;p>Configuration for Ruff has moved is done in my &lt;code>pyproject.toml&lt;/code> &lt;a href="https://github.com/dietervansteenwegen/python_template/blob/master/pyproject.toml" target="_blank" rel="noopener">template&lt;/a>&lt;/p>
&lt;p>I&amp;rsquo;m still using AutoDocString to ease docstring creation and MyPy for type checking.&lt;/p>
&lt;/blockquote>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p class="warning">The following is a brief guide to reinstalling/setting up Visual Studio Code (VSC) on a new Linux system. The main use is Python development. As such, it is very brief and mostly for my own documentation.&lt;/p></description></item><item><title>Using MicroPython (PyBoard V1.1) with Visual Studio Code</title><link>https://boxfish.be/posts/20200928-using-pyboard-v1-1-with-visual-studio-code/</link><pubDate>Mon, 28 Sep 2020 00:00:00 +0000</pubDate><guid>https://boxfish.be/posts/20200928-using-pyboard-v1-1-with-visual-studio-code/</guid><description>&lt;h2 id="warning">Warning&lt;/h2>
&lt;blockquote>
&lt;p>This still isn&amp;rsquo;t working as I think it should. Especially the linting and autocomplete still doesn&amp;rsquo;t work (leaving only the PyMakr module which works partly, in fact). For example: &lt;code>import pyb&lt;/code> still does not add autocompletion when typing something like &lt;code>s = pyb.&amp;lt;CTRL + SPACE&amp;gt;&lt;/code>. Most likely this is because I used a combinations of tools that shouldn&amp;rsquo;t be used together. Need to spend more time on this&amp;hellip;&lt;/p>
&lt;/blockquote>
&lt;h2 id="intro">Intro&lt;/h2>
&lt;p>I&amp;rsquo;ve recently started using a &lt;a href="https://store.micropython.org/product/PYBv1.1H" target="_blank" rel="noopener">PyBoard&lt;/a> for a project that I am working on. Writing code in an IDE, saving the files, then manually copying them to the board to test them gets tedious rather quickly. If you&amp;rsquo;re using Visual Studio Code, there are options to do almost everything from within the IDE itself. Getting things to work as they should took a bit of effort and head scratching. What I needed to do is documented below.&lt;br>
Links to the sources of my information is at the bottom.&lt;/p></description></item></channel></rss>