Person linkage case study (for PyPI)
If you have access to GitHub, we recommend installing from https://github.com/ihmeuw/person_linkage_case_study. This package is provided only for the convenience of users who cannot access GitHub.
Getting started
Before you start, you'll need to have Python installed. If you intend to use Spark, you'll also need Spark 3.4 to be installed on your system.
First, make a directory to use for development. Inside this directory, create and enter a virtual environment for this project:
$ python -m venv .venv
$ source .venv/bin/activate
and install this package:
$ pip install person_linkage_case_study
Your new working directory for interacting with the case study will be inside this venv. Specifically:
$ cd .venv/lib/python3.*/site-packages/person_linkage_case_study
To test that things are set up correctly, try running:
$ snakemake --forceall
Installing extras
You can install dependencies for using Spark and Dask by installing with those extras:
$ pip install person_linkage_case_study[spark,dask]
Spark without Singularity
The case study typically runs Spark in a Singularity container. If you cannot use Singularity,
edit the file at person_linkage_case_study/profiles/default/config.yaml to say
use-singularity: false instead of use-singularity: true.
As mentioned above, this will rely on Spark 3.4 being installed on your system.
Specifically, it must be installed at /opt/spark.
What's next?
For further instructions, see the README.md bundled within the package (at the top level
of your working directory as described previously).
Aside from how to use Spark, and installing with pip install person_linkage_case_study
instead of pip install -e ., all the instructions in that README apply to a PyPI installation.
Metadata
Release files for person-linkage-case-study 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| person_linkage_case_study-0.1.0.tar.gz | 17.6 MB | Without provenance | Details for person_linkage_case_study-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| person_linkage_case_study-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for person_linkage_case_study-0.1.0-py3-none-any.whl |
Total release size: 35.4 MB
Release files / person_linkage_case_study-0.1.0.tar.gz
| Download URL | person_linkage_case_study-0.1.0.tar.gz |
|---|---|
| Size | 17.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97776464591770a072582c04179d6d3f85961dfa7d98429c7779e53522181fa7
|
|
BLAKE2b-256 checksum How to use checksums |
af34da7f515c896e6cdaf74a2630c92e038528aa02f8e957733494b0c151bc42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / person_linkage_case_study-0.1.0-py3-none-any.whl
| Download URL | person_linkage_case_study-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8db1d6c7dd06055c47b29ff21b00ca67b4ea29bd4d61f491191d908884cfc7d
|
|
BLAKE2b-256 checksum How to use checksums |
ba135ee9b86ba7d44610998978b4b8f734e0f8ad74584929bf3309d30c1e1bc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for person-linkage-case-study 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.