What’s new in 7.6.1? Fix spelling:word role rendering verbatim (contributions by Mark Vander Stel) add test job using isolated build setup skip builder test that requires git history add check-python-versions to pkglint job fix broken links in release notes set doc language to english for sphinx 5.0 docs: update docs for domain
What’s new in 7.6.0? feature: add spelling:word role for inline corrections docs: update documentation to use new domain-based directive feature: add domain The old spelling directive is deprecated in favor of spelling:word-list.
What’s new in 7.5.1? #180 Suppress SystemExit errors in ImportableModuleFilter caused by importing modules that run code on import and exit when that code sees an error. Bug report and reproducer provided by Trevor Gross.
What’s new in 7.5.0? Support multiple wordlists as a string option from the command line via -D (contributions by Graham Smith) Include captions on figures in the text checked. Add a configuration option to limit the suggestions shown in the output.
What’s new in 7.4.0? Fixes
#159 Use the line of the misspelled word as source position in message (contributions by Peter Gerell) #153 log our version of location instead of log library’s, report error locations using relative paths, show the correct filename for included files handle empty word list correctly Tooling
ci: add python 3.11 test job tox: pass PYENCHANT_LIBRARY_PATH variable through to commands tox: only run unit tests with one version of python by default
What’s new in 1.12.0? mergify: Let mergify handle merging PRs client: update ssl handling for newer python 3 and imapclient requirements: update imapclient dependency to >=2.2.0 for python 3.10 packaging: add python 3.10 support to trove classifiers tox: use current python version only for default environments github: add python 3.10 to CI configuration stop building universal wheels
What’s new in 7.3.3? Minor code tweaks (contributions by Avram Lubkin) Skip contrib test when not in repo (contributions by Avram Lubkin) Switch to PEP 420 namespace (contributions by Avram Lubkin)
When I took on a staff engineer role on the OpenShift team at Red Hat last year, one of the first changes I wanted to make was to overhaul our design review process. Lately, we’ve been talking a lot about that process and whether we can update it to “go faster.” I’ve been explaining why the process works the way it does to different people, and thought that others outside of Red Hat might be interested in the same answers.