Skip to content

Release 0.5.0 #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 35 commits into from
May 11, 2022
Merged

Release 0.5.0 #53

merged 35 commits into from
May 11, 2022

Conversation

ajnelson-nist
Copy link
Member

No description provided.

kchason and others added 30 commits March 21, 2022 14:33
References:
* #38
* [UCO OC-217] (CP-107) Revise ontology IRI to be slash-based and drop
  IRI base
* [ONT-64] (CP-17) Define scheme for CASE and UCO importable versioned
  IRIs

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A recent update in rdflib no longer infers the xsd prefix with the usage
of the unprepared string query accidentally used before this commit.
The `.prepareQuery` results should have been used here.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Fix unused variable reference
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Centralize namespace constants in namespace.py
Disclaimer:
Participation by NIST in the creation of the documentation of mentioned
software is not intended to imply a recommendation or endorsement by the
National Institute of Standards and Technology, nor is it intended to
imply that any specific software is necessarily the best available for
the purpose.

References:
* [AC-215] Evaluate pre-commit usage on casework repositories
* [AC-216] Apply Black to all casework Python code bases
* #37

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Disclaimer:
Participation by NIST in the creation of the documentation of mentioned
software is not intended to imply a recommendation or endorsement by the
National Institute of Standards and Technology, nor is it intended to
imply that any specific software is necessarily the best available for
the purpose.

References:
* [AC-215] Evaluate pre-commit usage on casework repositories
* [AC-216] Apply Black to all casework Python code bases
* #37

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Disclaimer:
Participation by NIST in the creation of the documentation of mentioned
software is not intended to imply a recommendation or endorsement by the
National Institute of Standards and Technology, nor is it intended to
imply that any specific software is necessarily the best available for
the purpose.

References:
* [AC-215] Evaluate pre-commit usage on casework repositories
* #37

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* usnistgov/opensource-repo#17

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This flag was a useful development aid, and its presence in the Make
command lines impacts generated UUID5s.  However, at the end of the
patch series adding this output, all of the debug statements will be
disabled.

A follow-on patch (at the end of the series) will regenerate
Make-managed files.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
`case_utils.local_uuid` provides a deterministic UUIDv5 generator based
on the execution environment.  Unfortunately, its prior implementation
was not behaving correctly when changing environments - a different
operating system, or working in a different rooted directory, would
cause UUID churn.

The issue turned out to be paths embedding in two manners:
1. The prior implementation assumed work happening somewhere under a
   user-home directory.  This is not always true.
2. The prior implementation did not catch that for a program
   `pip`-installed into a virtual environment in editable mode (or,
   possibly more generally than that), `sys.argv[0]` is the absolute
   path to the installed command in the virtual environment root.
   Hence, changing operating systems from macOS to Linux would change
   `/Users/me` to `/home/me` within the UUID seeding data.

This patch revises the practice from functionally operating in a
Boolean manner ("Was this special string passed?") to passing an
anchoring directory, preferably the repository's Git-root directory.

Usage of the prior variable `DEMO_UUID_REQUESTING_NONRANDOM` is now
deprecated, raising a warning.

A test is also added to confirm new warnings are raised.

A follow-on patch will regenerate Make-managed files.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
An unexpected behavior arose, and the 3.10 somehow parsed as 3.1.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Change test Python versions to earliest and latest
Without this patch, `THIRD_PARTY_LICENSES.md` was not being included in
the distribution files built by `setup.py`.

References:
* https://packaging.python.org/en/latest/guides/using-manifest-in/

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
ajnelson-nist and others added 5 commits May 11, 2022 10:45
@kchason kchason merged commit 33d9565 into main May 11, 2022
@kchason kchason deleted the release-0.5.0 branch May 11, 2022 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants