🔒 vs code driving me mad

[dim shadow]

Okay guys I have a problem with the behavior of VS code which is driving me nuts to be honest

So I have a directory structure where I have a bunch of folders where I'm actually writing the actual program and one single folder where I have the utilities kind of folder where I have all of the utilities

Now the problem is whenever I open vs code so that I can see all of the folders including the utilities 1 and then inside of subfolder I'm writing one of the program files and I'm importing one of the modules from one of the utils the problem I'm having is that the python program cannot find that module

Then I have to do this weird hack around where I do

sys.path.append("..")```

and then i also Need to open one of the subfolders as the main folder in VS code for district to work and only then can it import the utils properly so is there a work around around this or is there any other solution to this problem

[ripe cove]

@dim shadow

Python help channel opened

Remember to:

• Ask your Python question, not if you can ask or if there's an expert who can help.
• Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
• Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

Closes after a period of inactivity, or when you send !close.

[red wolf]

can u show ur project directory tree

[dim shadow]

here is how it looks

[red wolf]

and in which file u trying to import utils from and where are utils

[dim shadow]

i am tryng to import stack from linear structure

[red wolf]

think u missed one file path there

[dim shadow]

what??

[red wolf]

and can u show inside LinearStructures folder ?

[dim shadow]

sure

[red wolf]

missed blurring one file path

[dim shadow]

oh no i wanted to show that XD

to show where am i running the file from

[red wolf]

and whats command u using to run this

[dim shadow]

The only reason I'm hiding the path was because one of them has my name in it so instead of just blaring that portion i did some extra as well

[dim shadow]

??

I'm just using the run arrow from the Visual Studio code app

[red wolf]

py "2025-03-21 Lab 3/Ex1_ReverseWords.py"

what happens if u run it like this

[dim shadow]

So you want me to run the file from the terminal?

[red wolf]

yes

[dim shadow]

nope

its the same

[red wolf]

weird

[red wolf]

from ..LinearStructures import Stack

ig

or just make a venv at labs and that might fix (?)

[dim shadow]

still the same

[dim shadow]

nah that's too overkill for basic python code XD

[red wolf]

it really aint

[dim shadow]

O k so you want me to create a virtual environment over here and what else

[wet yew]

Gah.

[dim shadow]

And it should be in which directly the labs directory should have it with all of the 4 folders or should it be in one of the sub folders

[wet yew]

You don't need a venv for this. (They're very useful, but irrelevant here.)

[dim shadow]

Yeah I know it is very useless over here to be honest in my opinion as well

[red wolf]

i thought activating venv at labs would fix sys.path so that it could import it ?

[wet yew]

Just ensure that the folder containing LinearStructures is in your sys.path. Python gets that from the $PYTHONPATH environment variable, and VSCode should have some hook for setting that.

[dim shadow]

But if it fixes this issue that I am having which is driving me crazy I am happy to implement it

[dim shadow]

Well how can I check that and ensure that the folder is inside the path

[wet yew]

You can also do this with a venv by (a) making one (b) pointing VSCode at that venv and (c) installing the LinearStructures in the venv.

Feels elaborate.

[dim shadow]

Now that's a bit too crazy

[wet yew]

They're great for per-project environments. They just don't directly solve your current problem.

[dim shadow]

Any other solution which is less absurd

[dim shadow]

Yeah I know which environments I am using them in my other projects

They especially helpful when you're having a bunch of different Libraries and different python versions and stuff like that

anyhow over here how can I get the linear structure folder inside the path

[dim shadow]

Like you said in this message

[wet yew]

See this (link goes directly to the relevant section): https://code.visualstudio.com/docs/python/environments#_use-of-the-pythonpath-variable

[red wolf]

@wet yew does it not work like that ?

[dim shadow]

So I need to set python path variable

how do i enter terminal settings??

[wet yew]

"Activating" a venv puts the venv's bin at the front of your shell executation path so that python3 (or py etc) find the venv python. In VSCode, it may cause VSCode to invoke the venv python directly.

Regardless, the effect is that when you invoke the python3 from the venv is put's the venv's libraries in the sys.path automatically.

Then you just instal your extra libs in the venv.

For the OP, probably installing an "editable" version of LinearStructures. Which is basicly a symlink to that, in the site-poackages.

[wet yew]

I don't use VSCode, unsure.

[red wolf]

but wouldnt activating a venv in directory X put X in sys.path ?

[dim shadow]

If you don't mind telling me Which editor do you use

[wet yew]

No, it puts the venv libs in the sys.path.

[red wolf]

just checked C:\Users\Dagger\test\.venv it puts this in sys.path which ig is what confused me

[wet yew]

Note that when you invoke a script as:

py /path/to/the/script.py

(which is how VSCode runs things in the terminal window), Python puts /path/to/the at the front of the sys.path automatically. So If the OP's script were in the folder containing LinearStructures it might "just work". But that's fortuitous, not controlled.

[dim shadow]

I did that but it was not working?

[wet yew]

I use vim to edit code.

[dim shadow]

here

[wet yew]

Your script seems to be in a subdirectory. Is that the case.

[dim shadow]

yea

So I have a parent folder which has 4 subfolders and the programs are in 3 of those subfolders with the remaining one being linear structs where the imported modules are

[wet yew]

My Python area looks like this.

Oh, that's horribly unreadable. Discord scaling things down I guess.

[red wolf]

do u have 2 monitors or is just 1 large monitor and 1 large vim area (i assume with plugins)

[dim shadow]

wow

i am at awe

props to you for making sense from that color scheme

[wet yew]

That's a 16 inch macbook pro laptop display. Just one 3072x1920 screen. One full-screen iTerm window broken into 2 terminals side by side, a shell in the right and vim in the left. Vim split into 2 windows (files).

[red wolf]

for a moment i thought u just had installed some vim plugins and made 1 giant battlestation

[wet yew]

Nay. I ise iTerm to multiplex terminal windows. See the tabs on the left? A tab per python work area.

[dim shadow]

Is this the m three macbook pro

[wet yew]

No, an older intel one.

[dim shadow]

Because I have just recently seen the 16 inch Macbook Pro laptop with one of my friends and it wasn't that big to be honest

to manage all that one screen is mega

man is crazy and talented at the same time

[wet yew]

It's the same size. I run in native resolution. Macs default to a lower "logical" pixel count with subpixel dithering for nice rendering.

I just want lots of characters in my terminals.

[wet yew]

Looks like the magnifier widget in the discord view does show the full resolution.

[wet yew]

It's just 2 windows. Code on the left, a shell on the right. The shell is like VSCode's terminal window down the bottom. But big enough to be useful.

[dim shadow]

No you gotta open the image in a new tab

the magnifier just distorts the image to be honest

[wet yew]

Oh. It seemed to zoom in to me here. But it is full res for you? I often wonder.

Anyway. The terminal window on the right has the dev environment available.

CSS[~/hg/css(hg:default)]fleet2*> py3
+ exec /Users/cameron/tmp/venv--css--apple.x86_64.darwin/bin/python3
Python 3.13.1 (main, Dec  3 2024, 17:59:52) [Clang 16.0.0 (clang-1600.0.26.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['/Users/cameron/hg/css/lib/python', '/Users/cameron/p/lib/python', '/Users/cameron/lib/python', '/Users/cameron/rc/python', '/Users/cameron/var/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python313.zip', '/Users/cameron/var/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python3.13', '/Users/cameron/var/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python3.13/lib-dynload', '/Users/cameron/tmp/venv--css--apple.x86_64.darwin/lib/python3.13/site-packages']
>>>

So for me, typing py3 invokes the python3 from the venv I'm using. But also there's a $PYTHONPATH variable.

In the sys.path above these:

'/Users/cameron/hg/css/lib/python', '/Users/cameron/p/lib/python', '/Users/cameron/lib/python', '/Users/cameron/rc/python'

come from the $PYTHONPATH and the rest come from the venv python3 executable: the base homebrew python, then the venv site-packages at the end.

Does this make things any clearer?

@dim shadow ??

[ripe cove]

Python help channel closed for inactivity

This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.