create prod-like dev env

Signed-off-by: Allie Crevier <[email protected]>

.circleci/config.yml

@@ -10,7 +10,7 @@ common-steps:
       name: Install requirements and run tests
       command: |
         set -e
-        virtualenv .venv
+        make venv
         source .venv/bin/activate
         pip install --require-hashes -r requirements/dev-requirements.txt
         export PYTHONPATH=$PYTHONPATH:.  # so alembic can get to Base metadata

.gitignore

@@ -85,6 +85,7 @@ celerybeat-schedule
 # Environments
 .env
 .venv
+.venv-debian
 env/
 venv/
 ENV/

Makefile

@@ -1,6 +1,12 @@
 .PHONY: all
 all: help
 
+.PHONY: venv-debian
+venv-debian: ## Provision a Python 3 virtualenv for **development**
+	python3 -m venv .venv-debian --system-site-packages
+	.venv-debian/bin/pip install --upgrade pip wheel
+	.venv-debian/bin/pip install --require-hashes -r "requirements/dev-requirements-debian.txt"
+
 .PHONY: venv
 venv: ## Provision a Python 3 virtualenv for **development**
 	python3 -m venv .venv
@@ -32,11 +38,11 @@ check-black: ## Check Python source code formatting with black
 
 .PHONY: isort
 isort: ## Run isort to organize Python imports
-	@isort --recursive ./
+	@isort --skip-glob .venv-debian --recursive ./
 
 .PHONY: check-isort
 check-isort: ## Check Python import organization with isort
-	@isort --check-only --diff --recursive ./
+	@isort --skip-glob .venv-debian --recursive --check-only --diff ./
 
 .PHONY: mypy
 mypy: ## Run static type checker
@@ -115,15 +121,19 @@ safety: ## Runs `safety check` to check python dependencies for vulnerabilities
 bandit: ## Run bandit with medium level excluding test-related folders
 	pip install --upgrade pip && \
 	pip install --upgrade bandit && \
-	bandit -ll --recursive . --exclude ./tests,./.venv
+	bandit -ll --recursive . --exclude ./tests,./.venv,./.venv-debian
 
 .PHONY: check
 check: clean check-black check-isort semgrep bandit lint mypy test-random test-integration test-functional ## Run the full CI test suite
 
 .PHONY: sync-requirements
 sync-requirements:  ## Update dev-requirements.txt to pin to the same versions of prod dependencies
-	rm -r requirements/dev-requirements.txt && cp requirements/requirements.txt requirements/dev-requirements.txt
+	if test -f "requirements/dev-requirements.txt"; then rm -r requirements/dev-requirements.txt; fi
+	if test -f "requirements/dev-requirements-debian.txt"; then rm -r requirements/dev-requirements-debian.txt; fi
+	cp requirements/requirements.txt requirements/dev-requirements.txt
+	cp requirements/requirements.txt requirements/dev-requirements-debian.txt
 	pip-compile --allow-unsafe --generate-hashes --output-file requirements/dev-requirements.txt requirements/requirements.in requirements/dev-requirements.in
+	pip-compile --allow-unsafe --generate-hashes --output-file requirements/dev-requirements-debian.txt requirements/requirements.in requirements/dev-requirements-debian.in
 
 .PHONY: requirements
 requirements:  ## Update *requirements.txt files if pinned versions do not comply with the dependency specifications in *requirements.in
@@ -141,11 +151,9 @@ update-dev-only-dependencies:  ## Update dev-requirements.txt to pin to the late
 	@while read line; do \
 		pip-compile --allow-unsafe --generate-hashes --upgrade-package $file --output-file requirements/dev-requirements.txt requirements/requirements.in requirements/dev-requirements.in; \
 	done < 'requirements/dev-requirements.in'
-
-.PHONY: update-pip-requirements
-update-pip-requirements: ## Updates all Python requirements files via pip-compile for Linux.
-	pip-compile --verbose --rebuild --generate-hashes --annotate --allow-unsafe --output-file "requirements/dev-requirements.txt" "requirements/requirements.in" "requirements/dev-requirements.in"
-	pip-compile --verbose --rebuild --generate-hashes --annotate --output-file "requirements/requirements.txt" "requirements/requirements.in"
+	@while read line; do \
+		pip-compile --allow-unsafe --generate-hashes --upgrade-package $file --output-file requirements/dev-requirements-debian.txt requirements/requirements.in requirements/dev-requirements-debian.in; \
+	done < 'requirements/dev-requirements-debian.in'
 
 # Explaination of the below shell command should it ever break.
 # 1. Set the field separator to ": ##" and any make targets that might appear between : and ##

requirements/dev-requirements-debian.in

@@ -0,0 +1,34 @@
+atomicwrites==1.2.1
+attrs==19.3.0
+black==19.10b0
+Click==7.0
+coverage==4.5.1
+flake8==3.6.0
+flaky==3.6.1
+isort==4.3.21
+MarkupSafe>=1.1
+mccabe==0.6.1
+more-itertools==4.3.0
+mypy==0.761
+mypy-extensions==0.4.3
+pillow>=8.3.1
+pip>=21.1
+pip-tools==5.5.0
+pluggy==0.13.0
+py>=1.10.0
+PyAutoGUI==0.9.48
+pycodestyle==2.4.0
+pyobjc-core==6.2;platform_system=="Darwin"
+pyobjc==6.2;platform_system=="Darwin"
+pyflakes==2.0.0
+pytest==5.2.1
+pytest-cov==2.8.1
+pytest-mock==1.10.0
+pytest-qt==3.3.0
+pytest-random-order==1.0.4
+pytest-vcr==1.0.2
+pytest-xdist==1.30.0
+pyyaml==5.4.1
+semgrep==0.42.0
+typed-ast==1.4.1
+vcrpy==4.0.2