Don't show test library prompt if interpreter is not selected

No description provided.

This will change in activateUnsafe in extensions.js. Activate the test frameworks later (after interpreter discovery)

(on linux)

I was able to validate the solution using the following settings.json:

{
    "python.testing.autoTestDiscoverOnSaveEnabled": true,
    "python.testing.pytestEnabled": true,
    //
    "python.linting.enabled": true,
    "python.linting.flake8Enabled": true,
    //
    "editor.formatOnSave": true,
    "python.formatting.provider": "black",
    //
    "python.pythonPath": "spamspamspam"
}

I checked to make sure the extension did not have an environment select and clicked on "discover" icon in the test explorer. There was no prompt. If I then selected a fresh venv (nothing installed) and clicked the icon, I got prompted.

But you needed to click the icon, that should not've happened. :( (I can also verify I needed to click the icon)
We'll have to investigate this.

Kartik Raj (@karrtikr)

Kartik Raj (@karrtikr) that would be a separate issue right?

Yes that's a different one, we can close this.

Kartik Raj (@karrtikr)

Kartik Raj (@karrtikr)

We'll have to investigate this.

Is this being tracked anywhere (or does it have to be tracked)?

Right, I don't believe it is. I'll open an issue.

Navigation Menu

Repository navigation

Don't show test library prompt if interpreter is not selected #9614

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Don't show test library prompt if interpreter is not selected #9614

Description

Activity

luabud commented on Jan 15, 2020

ericsnowcurrently commented on Jan 24, 2020

karrtikr commented on Jan 24, 2020

karthiknadig commented on Jan 24, 2020

karrtikr commented on Jan 30, 2020

luabud commented on Jan 31, 2020

karrtikr commented on Jan 31, 2020

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions