Merge https://github.com/jaraco/skeleton into master

Author: jaraco

.pre-commit-config.yaml

@@ -1,10 +1,10 @@
 repos:
 - repo: https://github.com/psf/black
-  rev: 19.10b0
+  rev: stable
   hooks:
   - id: black
 
 - repo: https://github.com/asottile/blacken-docs
-  rev: v1.4.0
+  rev: v1.8.0
   hooks:
   - id: blacken-docs

azure-pipelines.yml

@@ -89,6 +89,7 @@ stages:
         tox -e release
       env:
         TWINE_PASSWORD: $(PyPI-token)
+        GITHUB_TOKEN: $(Github-token)
       displayName: 'publish to PyPI'
 
   condition: contains(variables['Build.SourceBranch'], 'tags')

docs/refresh.svg

@@ -6,3 +6,17 @@ build-backend = "setuptools.build_meta"
 skip-string-normalization = true
 
 [tool.setuptools_scm]
+
+# jaraco/skeleton#22
+[tool.jaraco.pytest.plugins.black]
+addopts = "--black"
+
+# jaraco/skeleton#22
+[tool.jaraco.pytest.plugins.mypy]
+addopts = "--mypy"
+
+[tool.jaraco.pytest.plugins.flake8]
+addopts = "--flake8"
+
+[tool.jaraco.pytest.plugins.cov]
+addopts = "--cov"

pyproject.toml

@@ -0,0 +1,9 @@
+[pytest]
+norecursedirs=dist build .tox .eggs
+addopts=--doctest-modules
+doctest_optionflags=ALLOW_UNICODE ELLIPSIS
+# workaround for warning pytest-dev/pytest#6178
+junit_family=xunit2
+filterwarnings=
+    # https://github.com/pytest-dev/pytest/issues/6928
+    ignore:direct construction of .*Item has been deprecated:DeprecationWarning

pytest.ini

@@ -24,6 +24,14 @@ setup_requires = setuptools_scm[toml] >= 3.4.1
 [options.extras_require]
 testing =
 	# upstream
+	pytest >= 3.5, !=3.7.3
+	pytest-checkdocs >= 1.2.3
+	pytest-flake8
+	pytest-black >= 0.3.7; python_implementation != "PyPy"
+	pytest-cov
+	pytest-mypy; python_implementation != "PyPy"
+	# jaraco/skeleton#22
+	jaraco.test >= 3.2.0
 
 	# local
 	jaraco.itertools

setup.cfg

@@ -40,6 +40,10 @@ The `--allow-unrelated-histories` is necessary because the history from the skel
 
 Whenever a change is needed or desired for the general technique for packaging, it can be made in the skeleton project and then merged into each of the derived projects as needed, recommended before each release. As a result, features and best practices for packaging are centrally maintained and readily trickle into a whole suite of packages. This technique lowers the amount of tedious work necessary to create or maintain a project, and coupled with other techniques like continuous integration and deployment, lowers the cost of creating and maintaining refined Python projects to just a few, familiar Git operations.
 
+For example, here's a session of the [path project](https://pypi.org/project/path) pulling non-conflicting changes from the skeleton:
+
+<img src="https://raw.githubusercontent.com/jaraco/skeleton/gh-pages/docs/refresh.svg">
+
 Thereafter, the target project can make whatever customizations it deems relevant to the scaffolding. The project may even at some point decide that the divergence is too great to merit renewed merging with the original skeleton. This approach applies maximal guidance while creating minimal constraints.
 
 # Features

skeleton.md

@@ -7,8 +7,6 @@ tox_pip_extensions_ext_venv_update = true
 
 [testenv]
 deps =
-	# workaround for python/mypy#8627
-	mypy@git+https://github.com/python/mypy
 commands =
 	python -m unittest discover
 usedevelop = True
@@ -28,11 +26,14 @@ deps =
 	pep517>=0.5
 	twine[keyring]>=1.13
 	path
+	jaraco.develop>=7.1
 passenv =
 	TWINE_PASSWORD
+	GITHUB_TOKEN
 setenv =
 	TWINE_USERNAME = {env:TWINE_USERNAME:__token__}
 commands =
 	python -c "import path; path.Path('dist').rmtree_p()"
 	python -m pep517.build .
 	python -m twine upload dist/*
+	python -m jaraco.develop.create-github-release