@@ -7,6 +7,108 @@ and this project strives to adhere to
77[ Semantic Versioning] ( http://semver.org/spec/v2.0.0.html ) .
88
99
10+ ### [ 2.3.1] - 2022-11-29
11+
12+ #### Changed
13+
14+ * The printout of the inferred ` intersphinx_mapping ` item for inventories
15+ retrieved by URL (` --url ` ) in the 'suggest' CLI mode is now relocated to
16+ fall immediately below the inventory-search output. It also now is displayed
17+ even if no objects in the ` objects.inv ` satisfy the score threshold.
18+ ([ #262 ] ( https://github.com/bskinn/sphobjinv/issues/262 ) )
19+
20+ * The 'suggest' CLI mode output now includes dividers for improved
21+ readability.
22+
23+ #### Tests
24+
25+ * The plaintext ` tests/resource/objects_attrs.txt ` was converted to POSIX EOLs
26+ and declared as binary to git, in order to provide a consistent state for
27+ sdist packaging, regardless of platform (POSIX vs Windows).
28+
29+ * As a result, it was necessary to modify the ` scratch_path ` fixture to
30+ "` unix2dos ` " this file on Windows systems, in order to provide a
31+ consistent test state.
32+
33+ * Similarly, the ` decomp_cmp_test ` fixture was modified to "` unix2dos ` " the
34+ ` objects_attrs.txt ` resource before comparisons, again in order to provide
35+ a consistent reference artifact. Implementing required direct manipulation
36+ of the bytes contents of the file, instead of the ` filecmp.cmp ` method
37+ that had been used previously.
38+
39+ * The README doctests and shell tests have been removed from the default
40+ pytest suite. They must be explicitly opted-in with the ` --readme ` and
41+ ` --doctest-glob="README.rst" ` flags to pytest.
42+
43+ * A new job, ` readme ` , has been added to the ` aux_tests ` stage of the Azure
44+ Pipelines CI to run these tests for PRs and release branches.
45+
46+ * The constraint for ` pytest-check ` was bumped to ` >=1.1.2 ` and all uses of
47+ the ` check ` fixture were revised from ` with check.check(...): ` to
48+ ` with check(...): ` . ([ #265 ] ( https://github.com/bskinn/sphobjinv/issues/265 ) )
49+
50+ * Azure Pipelines now has Python 3.11 available for all of Ubuntu, Windows and
51+ MacOS, so it was added to the core text matrix for all platforms.
52+
53+ * A new CI job was created on Azure Pipelines that creates an sdist from the
54+ current project, extracts it into a sandboxed environment, installs the dev
55+ dependencies, and runs the pytest suite (` azure-sdisttest.yml ` ).
56+
57+ * All uses of ` pytest-check ` were updated to use the
58+ [ v1.1.2 syntax] ( https://github.com/okken/pytest-check/blob/main/changelog.md#110---2022-nov-21 )
59+ (` check ` fixture, or ` from pytest_check import check ` ).
60+
61+ #### Internal
62+
63+ * The ` sys.exit() ` in the case of no objects falling above the 'suggest'
64+ search threshold was refactored into the main ` do_suggest() ` body, to
65+ minimize the surprise of an ` exit() ` call coming in a subfunction.
66+ ([ #263 ] ( https://github.com/bskinn/sphobjinv/issues/263 ) )
67+
68+ #### Packaging
69+
70+ * ` MANIFEST.in ` was revised in order to provide a testable (` pytest --nonloc ` )
71+ sdist, in order to streamline packaging of ` sphobjinv ` for conda-forge.
72+ (Thanks very much to [ @anjos ] ( https://github.com/anjos ) for getting the
73+ recipes for ` sphobjinv ` and its dependencies in place! See
74+ [ #264 ] ( https://github.com/bskinn/sphobjinv/issues/264 ) .)
75+
76+ #### Administrative
77+
78+ * ` sphobjinv ` is now available via conda-forge! A note was added to the docs
79+ to indicate this.
80+
81+ * The version bump on ` pytest-check ` no longer permits the use of Python 3.6
82+ in CI. As Python 3.6 is nearly a year beyond EOL, this seems a reasonable
83+ time to officially drop support for it. ` python_requires ` will still be at
84+ ` >=3.6 ` for now; it * should* still work for 3.6...but, no guarantees.
85+
86+ * The hook versions for ` pre-commit-hooks ` , ` black ` , and ` pyproject-fmt ` were
87+ updated to v4.3, v22.10, and v0.3.5, respectively.
88+
89+ * ` CONTENT_LICENSE.txt ` was created, to specifically house the full
90+ content/documentation license information.
91+
92+ * ` LICENSE.txt ` was revised to only hold the MIT License for the code,
93+ primarily so that Github's automatic systems will recognize the project as
94+ MIT licensed.
95+
96+ * Caching of pip downloads was added to all of the Azure Pipelines jobs.
97+
98+ * The version constraint for ` pytest-check ` was raised to ` >=1.1.2 ` .
99+
100+ * A temporary upper bound was placed on the ` flake8 ` version (now ` >=5,<6 ` ,
101+ instead of ` >=5 ` ) to avoid pip resolver failures likely due to conflicts
102+ with constraints declared by plugins.
103+
104+ * The older versions of ` jsonschema ` tested in the ` tox ` matrix were
105+ streamlined down to 3.0 (` ==3.0 ` ), 3.x (` <4 ` ), 4.0 (` <4.1 ` ) and 4.8
106+ (` <4.9 ` ).
107+
108+ * The pin of ` sphinx-issues==0.4.0 ` in the ` tox ` matrix was removed, to match
109+ the unpinned package in the ` requirements-xxx.txt ` files.
110+
111+
10112### [ 2.3] - 2022-11-08
11113
12114#### Added
@@ -24,6 +126,11 @@ and this project strives to adhere to
24126 with the URLs it checks when trying to retrieve a remote inventory.
25127 ([ #99 ] ( https://github.com/bskinn/sphobjinv/issues/99 ) , plus more)
26128
129+ * CLI 'suggest' results output now displays more information about
130+ the total number of objects in the inventory, the search score threshold,
131+ and the number of results falling at/above that threshold.
132+ ([ #232 ] ( https://github.com/bskinn/sphobjinv/issues/232 ) )
133+
27134 * A new CLI option, ` -p ` /` --paginate ` , enables paging of the results from the
28135 ` suggest ` feature. ([ #70 ] ( https://github.com/bskinn/sphobjinv/issues/70 ) )
29136
@@ -61,7 +168,8 @@ and this project strives to adhere to
61168 ` objects_sphinx.inv ` , and the previous v1.6.6 was renamed to
62169 ` objects_sphinx_1_6_6.inv ` .
63170
64- * The 'valid objects' test cases were updated to reflect the possibility for a colon within ` {role} ` :
171+ * The 'valid objects' test cases were updated to reflect the possibility for a
172+ colon within ` {role} ` :
65173
66174 * The colon-within-` {role} ` test case was moved from 'invalid' to 'valid'.
67175
@@ -105,12 +213,6 @@ and this project strives to adhere to
105213
106214### [ 2.2.2] - 2022-03-22
107215
108- #### Changed
109-
110- * CLI 'suggest' results output now displays more information about
111- the total number of objects in the inventory, the search score threshold,
112- and the number of results falling at/above that threshold.
113-
114216#### Fixed
115217
116218 * UnicodeDecodeErrors are ignored within the vendored ` fuzzywuzzy ` package
0 commit comments