So I'm migrating my code to a new project format after learning about how they should be formatted for release. I'm using UV to create the .git-ignore and all the other goodies it does. The package is called cmo. I'm trying to run tests on some of the code and resolve imports.

So as an example: I have cmo/src/data/doctrine/air_operations_tempo. And I have a file cmo/src/helpers/values/get_item_from_menu with the function get_item_from_menu.

air_operations_tempo imports it but is getting an error that neither com/src/etc. nor src/helpers/etc. work as a valid import path.

Also, trying to import air_operations_tempo into cmo/tests/data/doctrine/test_air_operations_tempo doesn't work either with cmo/src/etc. nor src/data/etc.

I am at a loss it works on the old code but not anymore. Any help would be GREATLY appreciated. I am at wits end. It's probably something simple knowing my luck.

A picture of the file structure

I am trying to get pytest to work. I am using VSCode, Anaconda and the Python extension on Windows 10 (all latest versions) with:

• pytest 5.2.4.

• Python 3.7

I am probably using the second most simplest use case. I have all my test files in a subdirectory called tests in the root directory of my application source code.

I can get test discovery and execution to work when I am at a command prompt with the activated anaconda environment and type: python -m . Pytest discovers all the tests and runs them with no problems whatsoever.

If I click on the Test discovery in VSCode, pytest finds all the test files but there are all kinds of ModuleNotFoundError errors. Example error output:

_____________________ ERROR collecting tests/test_acsr.py _____________________
ImportError while importing test module 'C:\path_to_source_code\tests\test_acsr.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests\test_acsr.py:6: in <module>
    from acsr import is_pure_ground_run
E   ModuleNotFoundError: No module named 'acsr'

The acsr.py file is in the root of my application (parent directory of tests) and contains the functions I wish to test.

I checked the VS Code, and pytest documentation to see if I was missing some configuration options but didn't find anything. It appears that under VS Code, pytest can't figure out the sys.path or something. I feel like I am going around in circles trying to get this working as none of the answers on stackoverflow or anywhere else seem to fit this simple use case.

If anyone can supply me with a fix or has a link to a comprehensive tutorial that helps with pytest setup in VS Code I would be greatly appreciated.

PS I had it working in VS Code months ago, and I don't remember having to do any special configuration beyond what was outlined in the docs. It just stopped working one day, perhaps after an update, not sure. When it was working I thought it was pretty awesome.

I've got a bunch of files in a directory that I'm pointing to with both the PYTHONPATH and LD_LIBRARY_PATH. I'm able to work with and import these libraries basically everywhere else but the testing tab: This works on the terminal with my virtualenv, also works with my current settings in my vscode terminal, I can even run a script in vscode using its own debugger without having to modify launch.json and it will detect the import.

But any unit tests I execute can't find the package, and vscode/pylance marks the import line in the file editor with "could not be resolved" error. I'm guessing these things aren't seeing the paths early enough for it to use them properly, but I've tried a few things and nothing seems to work. At the very least it doesn't seem to work when I set them via .env file in my workspace file.

Edit: Tried setting the values in my .bashrc to make it as global and early as possible and that doesn't work either. Its like its actively choosing to ignore it.

Edit2: I think maybe what I need to do is somehow explicitly set the variables for test discovery? I can see in the output "all environment variables set for pytest discovery" and it seems to only be drawing on a sepcific subset of env variables its pulling from the system and ignoring others. The pythonpath in particular is pointing exclusively to somewhere in the extensions own files.

SOLUTION: So apparently it absolutely refused to even look at my PYTHONPATH or LD_LIBRARY_PATH variables I needed unless I specifically put them in a .env file and nowhere else, and it had to be in the directory of one specific module of my repository instead of the root directory, god why does this shit have to be so painfully specific.

I'm trying to use torch in a python script but even though it's pip installed, pylance doesn't recognize it

https://imgur.com/EM5fEIo

Any advice on how to resolve this? Thanks.