category__and
[tpg_get_posts category__and="flowers, purple flowers"]
By category__in
[tpg_get_posts category__in="flowers, purple flowers"]
By category__not_in
[tpg_get_posts numberposts=1 category__not_in="flowers, purple flowers"]
*** these notes are a work-in-progress and will be updated as needed ***
This post documents how I set up projects in Python and how to configure VS Code for debugging.
Project Structure
There are 2 basic forms of project structure that seem to work for me.
Simple Projects
project-name
doc/
data/
inc/
__init__.py
shared-code1.py
shared-code2.py
tests/
__init__.py
test_test1.py
test_test2.py
program.py
program2.pyComplex Projects
project-name
doc/
data/
tests/
testfiles/
temp&permanent-test-files
__init__.py
test_test1.py
test_test2.py
project-name
inc/
__init__.py
shared-code1.py
shared-code2.py
__init__.py
__main__.py
program.pyTesting
The __init__.py in the testing folder should contain the following code. This adds the project folder to the python path so the imports work as expected.
import os
import sys
PROJECT_PATH = os.getcwd()
PROJECT_FOLDER = os.path.basename(PROJECT_PATH)
SOURCE_PATH = os.path.join(
PROJECT_PATH,PROJECT_FOLDER
)
sys.path.append(SOURCE_PATH)VS Code Configuration
The challenge with both of these structures is importing the programs and shared programs in the tests modules. If you are in the main directory, then running the tests with discovery (ie python -m unittest) will generally work. However, if you are in the test directory and trying to debug a test with VS Code, the imports fail with module not found.
The follow launch will set the PYTHONPATH to the workspace folder so all imports can be found.
"launch": {
"version": "0.2.0",
"configurations": [
{
"name": "Python: Current File",
"type": "python",
"request": "launch",
"program": "${file}",
"env": {"PYTHONPATH": "${workspaceFolder}"},
"console": "integratedTerminal",
"justMyCode": true
}
]
}By tag and sticky post
[tpg_get_posts tag="flowers" ignore_sticky_posts="false" ]