How to add the current project path to "python.analysis.extraPaths", currently using version 1.3.1 #324

maryjeck · 2024-04-27T16:04:27Z

before the version 1.3.1,it's auto include it

jfcherng · 2024-04-27T19:12:24Z

We do have some logics for python.analysis.extraPaths but I don't think LSP-pyright have ever included the current project path. What we do for python.analysis.extraPaths is to find Sublime Text API stubs and installed Python libraries for Sublime Text plugin hosts and that only happens when the user sets pyright.dev_environment. That's totally unrelated to your description.

jfcherng · 2024-04-27T19:20:16Z

Since your description is pretty specific, how do you find LSP-pyright adds the current project path to python.analysis.extraPaths? Or, maybe, what you are actually trying to achieve?

jfcherng · 2024-04-28T14:13:42Z

Didn't see Path (plaintext search) in pyright's recent changelog either 🤔

maryjeck · 2024-04-29T04:13:58Z

In the previous version, my custom module could be imported normally, but in this latest version, my project's custom module cannot be recognized.
So I want to ask if there is any special parameter indicating the current project path

jfcherng · 2024-04-29T04:17:41Z

In the previous version, my custom module could be imported normally, but in this latest version, my project's custom module cannot be recognized. So I want to ask if there is any special parameter indicating the current project path

Could you provide a minimal reproducer repository (or uploading a .zip file) for test?

maryjeck · 2024-04-29T04:35:06Z

In the previous version, my custom module could be imported normally, but in this latest version, my project's custom module cannot be recognized. So I want to ask if there is any special parameter indicating the current project path在以前的版本中，我的自定义模块可以正常导入，但在这个最新版本中，我无法识别我的项目的自定义模块。所以我想问一下是否有任何特殊参数指示当前项目路径

Could you provide a minimal reproducer repository (or uploading a .zip file) for test?你能提供一个最小的复制器存储库（或上传 .zip 文件）进行测试吗？

ok,I'll pack it up

maryjeck · 2024-04-29T04:40:52Z

test.zip
This is a test file

显示这个错误

maryjeck · 2024-04-29T04:41:15Z

It will be recognized in previous versions

jfcherng · 2024-04-29T04:50:08Z

I am not able to reproduce this with the latest released LSP-pyright. Could you share your LSP-pyright's settings?

Could your issue be reproduced in Sublime Text's safe mode without changing any LSP-pyright's settings?

maryjeck · 2024-04-29T06:43:31Z

// Settings in here override those in "LSP-pyright/LSP-pyright.sublime-settings"
{
    "settings": {
        "python.analysis.extraPaths": [
            "F:\\miniconda3\\Lib",
            "F:\\miniconda3\\Lib\\site-packages",
            "./"
        ],
        "python.analysis.autoSearchPaths": true,
        "python.analysis.stubPath": "./typings",
        "python.analysis.diagnosticMode": "workspace",
        "python.analysis.diagnosticSeverityOverrides": {
            "reportUnboundVariable": "none",
            "reportGeneralTypeIssues": "information",
            "reportOptionalMemberAccess": "none",
            "reportUnusedImport": "warning"
        },
        "python.analysis.typeshedPaths": [
            "."
        ],
        "python.analysis.typeCheckingMode": "off",
        "pyright.disableOrganizeImports": true,
        "python.pythonPath": "F:\\miniconda3\\python.exe",
        "python.venvPath": ".",
    }
}

maryjeck · 2024-04-29T06:46:04Z

here

jfcherng · 2024-04-29T12:05:56Z

Still can't reproduce, even with the exact plugin settings.

// Settings in here override those in "LSP-pyright/LSP-pyright.sublime-settings"
{
    "settings": {
        "python.analysis.extraPaths": [
            "C:\\Users\\jfcherng\\AppData\\Local\\Programs\\Python\\Python38\\Lib",
            "C:\\Users\\jfcherng\\AppData\\Local\\Programs\\Python\\Python38\\Lib\\site-packages",
            "./"
        ],
        "python.analysis.autoSearchPaths": true,
        "python.analysis.stubPath": "./typings",
        "python.analysis.diagnosticMode": "workspace",
        "python.analysis.diagnosticSeverityOverrides": {
            "reportUnboundVariable": "none",
            "reportGeneralTypeIssues": "information",
            "reportOptionalMemberAccess": "none",
            "reportUnusedImport": "warning"
        },
        "python.analysis.typeshedPaths": [
            "."
        ],
        "python.analysis.typeCheckingMode": "off",
        "pyright.disableOrganizeImports": true,
        "python.pythonPath": "C:\\Users\\jfcherng\\AppData\\Local\\Programs\\Python\\Python38\\python.exe",
        "python.venvPath": ".",
    }
}

jfcherng · 2024-04-29T12:06:24Z

Could your issue be reproduced in Sublime Text's safe mode without changing any LSP-pyright's settings?

This hasn't been answered yet.

jfcherng · 2024-04-29T12:28:24Z

Someone probably has the same issue: microsoft/pyright#7016 (comment)
But it's claimed fixed in pyright 1.1.360, which is LSP-pyright 1.3.1 🤔

maryjeck · 2024-04-29T13:23:01Z

Someone probably has the same issue: microsoft/pyright#7016 (comment) But it's claimed fixed in pyright 1.1.360, which is LSP-pyright 1.3.1 🤔

What I use is LSP-pyright 1.3.1

maryjeck · 2024-04-30T14:31:29Z

@jfcherng How to roll back to the previous version or a specific version

jfcherng · 2024-04-30T14:43:20Z

@jfcherng How to roll back to the previous version or a specific version

I guess basically you want Package Control to not manage it.

	"unmanaged_packages_ignore": [],

Or just overwrite language-server to an old version.

maryjeck · 2024-05-04T13:22:09Z

The status of version 1.3.2 is the same, and the reconfiguration is also the same, o(╥﹏╥)o

jfcherng · 2024-05-04T13:23:29Z

Have you found a working old version yet?

maryjeck · 2024-05-04T13:24:43Z

I don’t know how to roll back. After setting it up according to your method, it didn’t roll back to the previous version.

jfcherng · 2024-05-04T13:47:47Z

I don’t know how to roll back. After setting it up according to your method, it didn’t roll back to the previous version.

It prevents package control from managing (updating) it. It won't do rollback. It's you who have to do the rollback.

jfcherng · 2024-05-04T13:55:06Z

I don’t know how to roll back.

Download the version you want. E.g., https://github.com/sublimelsp/LSP-pyright/archive/refs/tags/1.3.2.zip
Decompress and put it like

Packages
└── LSP-pyright
    ├── commands.py
    ├── dependencies.json
    ├── language-server
    │   ├── package.json
    │   └── package-lock.json
    ├── ...

If you decompress it, it's LSP-pyright-1.3.2, you have to rename it as LSP-pyright and put it under Packages.

Restart ST.

And if you are familiar with git, you will know you can do this with git and quickly switch among versions.

maryjeck · 2024-05-04T14:14:24Z

This version works very well, and can be retired as long as the upstream version is not resolved.

maryjeck · 2024-05-04T14:28:22Z

Say something else

Except for one package, lsp-basedpyright is also limited to this version. Is it because lsp is not set up properly or is it an upstream problem?

jfcherng · 2024-05-04T14:41:31Z

Just to confirm. LSP-pyright 1.3.0 and LSP LSP-basedpyright 1.1.0 both work for you and their next version failed, right?

maryjeck · 2024-05-04T14:46:31Z

Just to confirm. LSP-pyright 1.3.0 and LSP LSP-basedpyright 1.1.0 both work for you and their next version failed, right?

yes。The latter two versions of these two plug-ins do not work normal, whether it is a clean system or a safe mode

maryjeck · 2024-05-05T02:56:38Z

LSP-basedpyright

By the way, I replaced package.json and package-lock.json in LSP-basedpyright 1.1.0 with the same files in 1.1.2, and the result is that it runs perfectly. It seems that it is not an upstream problem. Please help to see if there is a setting problem

jfcherng · 2024-05-06T15:06:34Z

Could you try this: https://github.com/sublimelsp/LSP-pyright/archive/refs/heads/fix/import-not-found.zip

I doubt it may be fixed by 273a22c. This is the only behavior change that I notice between v1.3.0 and v1.3.1: 1.3.0...1.3.1

maryjeck · 2024-05-07T03:03:46Z

Could you try this: https://github.com/sublimelsp/LSP-pyright/archive/refs/heads/fix/import-not-found.zip

I doubt it may be fixed by 273a22c. This is the only behavior change that I notice between v1.3.0 and v1.3.1: 1.3.0...1.3.1

sorry,Still not working

jfcherng · 2024-05-07T13:20:04Z

Unfortunately, I still can't spot other behavior different between 1.3.0...1.3.1.

jfcherng · 2024-05-07T13:34:08Z

Could you provide LSP-pyright's initialization logs (in LSP's log panel) for both v1.3.0 and v1.3.1 on your side?

maryjeck · 2024-05-09T01:37:48Z

log panel

How to view lsp logs?

Like this?

jfcherng · 2024-05-09T01:38:41Z

log panel

How to view lsp logs?

Like this?

yes, but a screenshot won't help. you can save them into files, zip them and upload here.

maryjeck · 2024-05-09T02:33:20Z

I will create a new clean version and send it to you.

jfcherng · 2024-05-09T02:46:08Z

I will create a new clean version and send it to you.

Appreciated.

maryjeck · 2024-05-17T03:43:34Z

lsp-pyright-logs.zip
Sorry, I've been away on a business trip recently and haven't had the time to test it. I'm uploading it for you now.

maryjeck · 2024-05-17T16:31:18Z

I have determined that in my case, it is a problem with the upstream language-server. I still use 1.3.0

jfcherng · 2024-05-17T17:08:01Z

I have determined that in my case, it is a problem with the upstream language-server. I still use 1.3.0

You mean this is a pyright issue rather than lsp-pyright's?

jfcherng · 2024-05-17T18:40:03Z

lsp-pyright-logs.zip Sorry, I've been away on a business trip recently and haven't had the time to test it. I'm uploading it for you now.

Thanks for providing these information. But I need logs both when working and when not working, so we can find the difference.

maryjeck · 2024-05-18T02:00:21Z

diff.zip
This is the log for 1.10 and 1.15.

jfcherng · 2024-05-21T13:06:55Z

OK (1.1.0?)

'diagnosticMode': 'workspace', 'extraPaths': ['F:\\miniconda3\\Lib', 'F:\\miniconda3\\Lib\\site-packages', '.\\', './', '', '.'],

FAILED (1.1.5?)

'diagnosticMode': 'openFilesOnly', 'extraPaths': [],

Expected to be failed but I doubt they are run under the exact same setup.

I think they have some fundamental differences so that I don't think they are run under the same setup. Hence diff.zip is probably useless.

I would expect the only environment difference when running for logs is the version number of LSP-basedpyright or LSP-pyright. Same ST workspace, plugin settings, project settings, same opened file etc... except that one uses LSP-basedpyright v1.1.0 and the other uses v1.1.5.

jfcherng added the help wanted Extra attention is needed label May 7, 2024

How to add the current project path to "python.analysis.extraPaths", currently using version 1.3.1 #324

How to add the current project path to "python.analysis.extraPaths", currently using version 1.3.1 #324

Comments

maryjeck commented Apr 27, 2024

jfcherng commented Apr 27, 2024 • edited Loading

jfcherng commented Apr 27, 2024 • edited Loading

jfcherng commented Apr 28, 2024 • edited Loading

maryjeck commented Apr 29, 2024 • edited Loading

jfcherng commented Apr 29, 2024

maryjeck commented Apr 29, 2024

maryjeck commented Apr 29, 2024

maryjeck commented Apr 29, 2024

jfcherng commented Apr 29, 2024 • edited Loading

maryjeck commented Apr 29, 2024 • edited by jfcherng Loading

maryjeck commented Apr 29, 2024

jfcherng commented Apr 29, 2024 • edited Loading

jfcherng commented Apr 29, 2024

jfcherng commented Apr 29, 2024 • edited Loading

maryjeck commented Apr 29, 2024 • edited Loading

maryjeck commented Apr 30, 2024

jfcherng commented Apr 30, 2024 • edited Loading

maryjeck commented May 4, 2024

jfcherng commented May 4, 2024

maryjeck commented May 4, 2024

jfcherng commented May 4, 2024 • edited Loading

jfcherng commented May 4, 2024 • edited Loading

maryjeck commented May 4, 2024

maryjeck commented May 4, 2024

jfcherng commented May 4, 2024 • edited Loading

maryjeck commented May 4, 2024

maryjeck commented May 5, 2024

jfcherng commented May 6, 2024 • edited Loading

maryjeck commented May 7, 2024

jfcherng commented May 7, 2024

jfcherng commented May 7, 2024 • edited Loading

maryjeck commented May 9, 2024

jfcherng commented May 9, 2024 • edited Loading

maryjeck commented May 9, 2024

jfcherng commented May 9, 2024

maryjeck commented May 17, 2024

maryjeck commented May 17, 2024

jfcherng commented May 17, 2024 • edited Loading

jfcherng commented May 17, 2024 • edited Loading

maryjeck commented May 18, 2024

jfcherng commented May 21, 2024 • edited Loading

OK (1.1.0?)

FAILED (1.1.5?)

jfcherng commented Apr 27, 2024 •

edited

Loading

jfcherng commented Apr 27, 2024 •

edited

Loading

jfcherng commented Apr 28, 2024 •

edited

Loading

maryjeck commented Apr 29, 2024 •

edited

Loading

jfcherng commented Apr 29, 2024 •

edited

Loading

maryjeck commented Apr 29, 2024 •

edited by jfcherng

Loading

jfcherng commented Apr 29, 2024 •

edited

Loading

jfcherng commented Apr 29, 2024 •

edited

Loading

maryjeck commented Apr 29, 2024 •

edited

Loading

jfcherng commented Apr 30, 2024 •

edited

Loading

jfcherng commented May 4, 2024 •

edited

Loading

jfcherng commented May 4, 2024 •

edited

Loading

jfcherng commented May 4, 2024 •

edited

Loading

jfcherng commented May 6, 2024 •

edited

Loading

jfcherng commented May 7, 2024 •

edited

Loading

jfcherng commented May 9, 2024 •

edited

Loading

jfcherng commented May 17, 2024 •

edited

Loading

jfcherng commented May 17, 2024 •

edited

Loading

jfcherng commented May 21, 2024 •

edited

Loading