<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Pylance on vxlabs</title>
		<link>https://vxlabs.com/tags/pylance/</link>
		<description>Recent content in Pylance on vxlabs</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 09 Dec 2023 16:53:00 +0200</lastBuildDate>
		
			<atom:link href="https://vxlabs.com/tags/pylance/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Minimal VSCode settings and extensions configuration for Python with ruff</title>
				<link>https://vxlabs.com/2023/12/09/minimal-vscode-settings-and-extensions-configuration-for-python-with-ruff/</link>
				<pubDate>Sat, 09 Dec 2023 16:53:00 +0200</pubDate>
				<guid>https://vxlabs.com/2023/12/09/minimal-vscode-settings-and-extensions-configuration-for-python-with-ruff/</guid>
				<description>&lt;p&gt;This morning while working on my &lt;a href=&#34;https://adventofcode.com/2023&#34;&gt;AoC&lt;/a&gt; submission, I wondered what the simplest procedure was for sharing a minimal setup for editing Python in Visual Studio Code using &lt;a href=&#34;https://github.com/astral-sh/ruff&#34;&gt;ruff&lt;/a&gt; for formatting, linting and import sorting, and doing all of that automatically on save.&lt;/p&gt;&#xA;&lt;p&gt;It turns out that you can just store the following &lt;code&gt;extensions.json&lt;/code&gt; and &lt;code&gt;settings.json&lt;/code&gt; in the &lt;code&gt;.vscode&lt;/code&gt; sub-directory of your source directory, and all of the above will be done. As a bonus, you can use the &lt;code&gt;ruff.toml&lt;/code&gt; example below to customise your ruff setup.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Set severity override of Visual Studio Code Pylance type mismatches for better visual distinction</title>
				<link>https://vxlabs.com/2020/07/23/vscode-pylance-type-mismatch-warning/</link>
				<pubDate>Thu, 23 Jul 2020 22:57:00 +0200</pubDate>
				<guid>https://vxlabs.com/2020/07/23/vscode-pylance-type-mismatch-warning/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/&#34;&gt;Pylance&lt;/a&gt; is Microsoft&amp;rsquo;s new and improved Python language server.&lt;/p&gt;&#xA;&lt;p&gt;I have been using this in my Visual Studio Code remote editing sessions&#xA;(editing Python codes on the machine learning Linux machine next to me, from my&#xA;laptop), and I&amp;rsquo;m enjoying its new type-checking capabilities.&lt;/p&gt;&#xA;&lt;p&gt;Today I discovered a little configuration change that improved my Pylance&#xA;experience, so I thought I&amp;rsquo;d share in case it helps anyone else.&lt;/p&gt;&#xA;&lt;h2 id=&#34;aside-ox-hugo-exports-with-org-download-screenshots&#34;&gt;Aside: ox-hugo exports with org-download screenshots&lt;/h2&gt;&#xA;&lt;p&gt;It was also an excuse to test how &lt;a href=&#34;https://ox-hugo.scripter.co/&#34;&gt;ox-hugo&lt;/a&gt; exports would work for a note&#xA;straight from my daily journal if screenshots were involved.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
