Github messages for voidlinux
 help / color / mirror / Atom feed
From: RicArch97 <RicArch97@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Python extension fails to start in vs code
Date: Thu, 11 Nov 2021 16:20:22 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34033@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

New issue by RicArch97 on void-packages repository

https://github.com/void-linux/void-packages/issues/34033

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  Void 5.13.19_1 x86_64 AuthenticAMD uptodate rrrmFFFF
* package:  vscode-1.62.1_1

### Expected behavior
The Python extension should start and work as expected.

### Actual behavior
Extension fails with the following error: `[ms-python.python]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-python.python`

This also happened on version `1.62.0` I've also tried multiple versions of the extension, with the same result.

I've downloaded the binary (proprietary) version of vs code from the Microsoft website to try and reproduce it in there, but I was able to start the Python extension there without any problems, which is the reason for me to post this issue here.

### Steps to reproduce the behavior
Install the official Python extension by Microsoft from the extensions, and check the runtime status after restarting vs code.



             reply	other threads:[~2021-11-11 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 15:20 RicArch97 [this message]
2021-11-13 20:34 ` [ISSUE] [CLOSED] " Johnnynator
2021-11-13 20:35 ` Johnnynator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34033@inbox.vuxu.org \
    --to=ricarch97@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).