-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UserWarning: incompatible copy of pydevd already imported #20355
Comments
I have this (or very similar) on a flask project as well, also using python 3.9
|
I have a similar problem. Since version v2022.20.0, the debugpy module is not found at launch time. When I install it, I get errors with pydevd. VsCode version: 1.74.0 debugpy error :
after debugpy intallation (same for all 1.6 versions) :
|
Same problem here with 1.74.0 |
Confirming, VSCode 1.74.0, Python 3.10.8 |
Some with VSCode 1.74.0 and Python 3.10.4 |
Same, vscode 1.74.0, python 3.9.13, python extension v2022.20.0 |
Same, with VSCode 1.74.9 ant Python 3.10.6 |
I assume no one has their own copy of debugpy or pydevd installed in their project somehow that would trigger this message? And do note the version of the Python extension is also important. And the relevant details automatically calculated when using the |
FYI we can reproduce this locally. This is reported at debugpy already at microsoft/debugpy#1148 . We are reaching out to the debugpy team about it, but if we can't get it resolved quickly we will roll back our copy of debugpy to https://pypi.org/project/debugpy/1.6.3/ and do a point release. |
I do have debugpy 1.6.3 in my environment. I'll await your resolution or point release before taking any action (e.g., to upgrade debugpy). |
I just merged #20369 . I need to trigger a build, make sure an installed VSIX works appropriately, and then we will release |
|
I got here chasing the same (type of) error messaging. Just bumped up to 2022.20.1 and can confirm the messaging has gone away. I am seeing a message "PyInt_FromLong not found." that wasn't present before 2022.20.1, however this may be from something else in my environment... just wanted to mention it here in case it sticks out to someone else: EDIT: |
LGTM. Message is gone here. Thanks @brettcannon for your support. |
Sorry for the noob question, but when I run Help > Check for Updates...
running vscode on windows, I don't see the new release. How to best get it?
…On Tue, Dec 13, 2022 at 3:35 AM Jej ***@***.***> wrote:
LGTM. Message is gone here.
Thanks @brettcannon <https://github.com/brettcannon> for your support.
—
Reply to this email directly, view it on GitHub
<#20355 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVVATIUUIQR74OB45KYE3WNAYM3ANCNFSM6AAAAAASZR3XCA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
...but I guess I picked it up when I restarted as the errors are gone. I
was looking for a new vscode release. Looks like it was the Python
extension that changed. Sorry for the noise.
…On Tue, Dec 13, 2022 at 6:32 AM Lou King ***@***.***> wrote:
Sorry for the noob question, but when I run Help > Check for Updates...
running vscode on windows, I don't see the new release. How to best get it?
On Tue, Dec 13, 2022 at 3:35 AM Jej ***@***.***> wrote:
> LGTM. Message is gone here.
>
> Thanks @brettcannon <https://github.com/brettcannon> for your support.
>
> —
> Reply to this email directly, view it on GitHub
> <#20355 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGVVATIUUIQR74OB45KYE3WNAYM3ANCNFSM6AAAAAASZR3XCA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
The unfortunate thing of about having to roll back to debugpy 1.6.3 is we lost all the bugfixes in 1.6.4. |
Since the last update (v2022.20.0) I get the following warning when I launch the debugger (on a newly created django project):
If I downgrade to previous version (v2022.18.2), the warning disappears.
Version: 1.74.0
Release: 22342
Commit: cb188d662af4ff5d43505b572b49905a1f0153ad
Date: 2022-12-08T20:05:53.183Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 6.0.0-0.deb11.2-amd64
Sandboxed: No
The text was updated successfully, but these errors were encountered: