Investigate using in-box copies of packages in tools extensions by default

[karthiknadig]

Handling In-Box vs Installed libraries in Tools Extensions

Proposed Setting

"pylint.importType": {
    "default": "bundled",
    "description": "Defines where `pylint` is imported from. This setting will be ignored if `pylint.path` is set.",
    "enum": [
        "bundled",
        "environment"
    ],
    "enumDescriptions": [
        "Always use the bundled version of `pylint`.",
        "Always used `pylint` from environment, fall back to bundled version when not available.",
    ],
    "scope": "<see scope proposal>",
    "type": "string"
},

Scope of the setting

Recommend scope is "window". User should be able to configure this just like python.languageServer.

Client-side changes

While creating the server launch command, client will add --import-type bundled to the server.py script.

Server-side changes

In the server, parse the arguments, handle as follows:

• bundled: then insert bundled path at 0.
• environment: then append bundled path to the end.

[rzhao271]

I see some requirements above.
What are some verification steps for this issue? In particular, are the client/server-side changes verifiable, or only the new setting?

[karthiknadig]

@rzhao271 Sorry. This was just a spike to see the various option. Nothing to verify here.