Can't get addressability to Django

[eddhyne]

All my references to django imports have sqiggly lines. Error msg is "Import "django.utilis.timezone" could not be resolved.
My pip.list command shows Django 4.2.1 installed in my virtual environment.
I have no Django intellisense
Attached is a screenshot.

[brettcannon]

I've transferred this to Pylance, but one key detail you cropped out of your screenshot is what environment you have selected (to verify it matches the one you have active in your terminal)?

[eddhyne]

Thanks for getting back to me. How do I verify the one I should be using? The one I am using is the virtual environment I installed packages in. When I add code, where should I be? ***@***.*** Ed Dhyne Direct: 954-608-6603 ***@***.******@***.***> www.linkedin.com From: Brett Cannon ***@***.***> Sent: Wednesday, May 24, 2023 2:26 PM To: microsoft/pylance-release ***@***.***> Cc: Ed Dhyne ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/pylance-release] Can't get addressability to Django (Discussion #4415) I've transferred this to Pylance, but one key detail you cropped out of your screenshot is what environment you have selected (to verify it matches the one you have active in your terminal)? — Reply to this email directly, view it on GitHub<#4415 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWFRBTF4BQEADX5BA6X2G2LXHZHEVANCNFSM6AAAAAAYNYNVXA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[rchiodo]

We'd need to know the environment selected in VS Code. It's on the bottom right of the window:

That's usually the reason why Pylance can't find your imports. It's not using the same environment that you're running with.

But it could be other reasons too.

[eddhyne]

Yes that is the virtual environment I install Django in. ***@***.*** Ed Dhyne Direct: 954-608-6603 ***@***.******@***.***> www.linkedin.com From: Rich Chiodo ***@***.***> Sent: Wednesday, May 24, 2023 2:59 PM To: microsoft/pylance-release ***@***.***> Cc: Ed Dhyne ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/pylance-release] Can't get addressability to Django (Discussion #4415) We'd need to know the environment selected in VS Code. It's on the bottom right of the window: [image]<https://user-images.githubusercontent.com/19672699/240714531-6dd47aa3-a2b7-424f-b0ca-81d14b6c53f3.png> That's usually the reason why Pylance can't find your imports. It's not using the same environment that you're running with. But it could be other reasons too. — Reply to this email directly, view it on GitHub<#4415 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWFRBTGLUULRT5LXGCP647DXHZK5TANCNFSM6AAAAAAYNYNVXA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[rchiodo]

Okay the next thing we need is a log of Pylance's analysis. Directions for capturing that log can be found here:
https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue

[eddhyne]

Here is the log and requirements.txt Ed Dhyne Direct: 954-608-6603 ***@***.******@***.***> www.linkedin.com From: Rich Chiodo ***@***.***> Sent: Wednesday, May 24, 2023 3:03 PM To: microsoft/pylance-release ***@***.***> Cc: Ed Dhyne ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/pylance-release] Can't get addressability to Django (Discussion #4415) Okay the next thing we need is a log of Pylance's analysis. Directions for capturing that log can be found here: https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue — Reply to this email directly, view it on GitHub<#4415 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWFRBTHLWO3PQNY2S24OMULXHZLN5ANCNFSM6AAAAAAYNYNVXA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[rchiodo]

The log for the 'Python Language Server' should show a line saying it's using that environment. Something like so:

2023-05-24 15:13:37.211 [info] [Info  - 3:13:37 PM] (33116) Setting pythonPath for service "Edshello_django": "Z:\Edshello_django\.venv\scripts\python.exe"

If it doesn't say that, then you didn't pick the right environment.

If it does say that, then you may be hitting a problem where UNC paths don't work. This VS code issue here:
microsoft/vscode#182070

There's an allow list now for UNC paths.
https://code.visualstudio.com/docs/setup/windows#_working-with-unc-paths

[eddhyne]

When I hit Ctrl+Shift+p I get a dropdown showing
Python 3.11.3('venv':)..venv\Scripts\python.exe Recommended What is it recommended for?
. When I enter code, I get squiggly line on all Djano imports and no Django intelisense
Is this .venv only for installing packages in? This has Django 4.2.1 the llatest 1 I installed.
. Python 3.11.3 64-bit D:\Python311\python.exe Global
When I select this, I get no squiggly lines and I do get Django intelisense
I this what I should select to do all my coding, runserver testing, debugging etc?
This also has This has Django 4.2.1

[rchiodo]

You can pick whichever one you want to run/install packages into. We generally recommend using a venv for doing this though.

I'm not sure what Z: is mapped to, maybe it's not a UNC path, but that might be why that venv doesn't work. VS code recently made it harder to use UNC paths because they're considered a security risk.

You could :

• Use the global python
• Create another venv somewhere on a local disk

[eddhyne]

I will use the global python
My z: drive is a mapped drive to a SYNOLOGY NAS. Could that be causing the problem?
I will move the project to a regular Windows drive and delete and recreate the venv to see if it makes a difference. Thanks.

[eddhyne]

How can I tell when Visual Studio Code was updated? I think it was yesterday on my PC. It fixed my problem. Its working OK on my NAS Z: drive. See my attachment.

[eddhyne]

I added all the info below to git but I don’t see my lates update there. How can I tell when Visual Studio Code update 1.78.2 was installed on my PC. It seams to have fixed my problem. I am working in the project in my NAS Z: drive and everything seam to be working when I am in my .VENV or Global. I will check it out further. ***@***.*** Ed Dhyne Direct: 954-608-6603 ***@***.******@***.***> www.linkedin.com From: Rich Chiodo ***@***.***> Sent: Thursday, May 25, 2023 11:59 AM To: microsoft/pylance-release ***@***.***> Cc: Ed Dhyne ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/pylance-release] Can't get addressability to Django (Discussion #4415) You can pick whichever one you want to run/install packages into. We generally recommend using a venv for doing this though. I'm not sure what Z: is mapped to, maybe it's not a UNC path, but that might be why that venv doesn't work. VS code recently made it harder to use UNC paths because they're considered a security risk. You could : * Use the global python * Create another venv somewhere on a local disk — Reply to this email directly, view it on GitHub<#4415 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWFRBTFZB3T646TS7CC6K73XH56VRANCNFSM6AAAAAAYNYNVXA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[eddhyne]

A few years ago I create www.imaginativesystems.com<http://www.imaginativesystems.com> in ASP.NET C#. I would like to replace it with a Python Django version. So far the tutorials I have tried only get me started. They don’t go into horizontal menus and vertical links like on my ISI site. Can you recommend any tutorials, courses, books or manuals that will help me. I would appreciate anything you can offer now that I can develop django projects in Visual Studio Code. Thanks for everything. Ed Dhyne Direct: 954-608-6603 ***@***.******@***.***> www.linkedin.com From: Rich Chiodo ***@***.***> Sent: Thursday, May 25, 2023 11:59 AM To: microsoft/pylance-release ***@***.***> Cc: Ed Dhyne ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/pylance-release] Can't get addressability to Django (Discussion #4415) You can pick whichever one you want to run/install packages into. We generally recommend using a venv for doing this though. I'm not sure what Z: is mapped to, maybe it's not a UNC path, but that might be why that venv doesn't work. VS code recently made it harder to use UNC paths because they're considered a security risk. You could : * Use the global python * Create another venv somewhere on a local disk — Reply to this email directly, view it on GitHub<#4415 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWFRBTFZB3T646TS7CC6K73XH56VRANCNFSM6AAAAAAYNYNVXA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[eddhyne]

After release update 1.78.2 was installed the other day, my problems have cleared up.