Skip to main content

Harmony Tool for Retrospective Data Harmonisation

Project description

Harmony

Package template taken from https://pypi.org/project/example-pypi-package/

This package

  • uses GitHub Actions for both testing and publishing
  • is tested when pushing master or main branch, and is published when create a release
  • includes test files in the source distribution
  • uses setup.cfg for version single-sourcing (setuptools 46.4.0+)

Automated tests

Test code is in tests/ folder using unittest.

The testing tool tox will be used in the automation with GitHub Actions CI/CD.

Use tox locally

Install tox and run it:

pip install tox
tox

In our configuration, tox runs a check of source distribution using check-manifest (which requires your repo to be git-initialized (git init) and added (git add .) at least), setuptools's check, and unit tests using pytest. You don't need to install check-manifest and pytest though, tox will install them in a separate environment.

The automated tests are run against several Python versions, but on your machine, you might be using only one version of Python, if that is Python 3.9, then run:

tox -e py39

Thanks to GitHub Actions' automated process, you don't need to generate distribution files locally. But if you insist, click to read the "Generate distribution files" section.

Generate distribution files

Install tools

Install or upgrade setuptools and wheel:

python -m pip install --user --upgrade setuptools wheel

(If python3 is the command on your machine, change python to python3 in the above command, or add a line alias python=python3 to ~/.bashrc or ~/.bash_aliases file if you use bash on Linux)

Generate dist

From example_pypi_package directory, run the following command, in order to generate production version for source distribution (sdist) in dist folder:

python setup.py sdist bdist_wheel

Install locally

Optionally, you can install dist version of your package locally before uploading to PyPI or TestPyPI:

pip install dist/example_pypi_package-0.1.0.tar.gz

(You may need to uninstall existing package first:

pip uninstall example_pypi_package

There may be several installed packages with the same name, so run pip uninstall multiple times until it says no more package to remove.)

Upload to PyPI

Register on PyPI and get token

Register an account on PyPI, go to Account settings § API tokens, "Add API token". The PyPI token only appears once, copy it somewhere. If you missed it, delete the old and add a new token.

(Register a TestPyPI account if you are uploading to TestPyPI)

Set secret in GitHub repo

On the page of your newly created or existing GitHub repo, click Settings -> Secrets -> New repository secret, the Name should be PYPI_API_TOKEN and the Value should be your PyPI token (which starts with pypi-).

Push or release

The example package has automated tests and upload (publishing) already set up with GitHub Actions:

  • Every time you git push or a pull request is submitted on your master or main branch, the package is automatically tested against the desired Python versions with GitHub Actions.
  • Every time a new release (either the initial version or an updated version) is created, the latest version of the package is automatically uploaded to PyPI with GitHub Actions.

View it on pypi.org

After your package is published on PyPI, go to https://pypi.org/project/example-pypi-package/ (_ becomes -). Copy the command on the page, execute it to download and install your package from PyPI. (or test.pypi.org if you use that)

If you want to modify the description / README of your package on pypi.org, you have to publish a new version.

If you publish your package to PyPI manually, read below:

Install Twine

Install or upgrade Twine:

python -m pip install --user --upgrade twine

Create a .pypirc file in your $HOME (~) directory, its content should be:

[pypi]
username = __token__
password = <PyPI token>

(Use [testpypi] instead of [pypi] if you are uploading to TestPyPI)

Replace <PyPI token> with your real PyPI token (which starts with pypi-).

(if you don't manually create $HOME/.pypirc, you will be prompted for a username (which should be __token__) and password (which should be your PyPI token) when you run Twine)

Upload

Run Twine to upload all of the archives under dist folder:

python -m twine upload --repository pypi dist/*

(use testpypi instead of pypi if you are uploading to TestPyPI)

Update

When you finished developing a newer version of your package, do the following things.

Modify the version number __version__ in src\examplepy__init__.py.

Delete all old versions in dist.

Run the following command again to regenerate dist:

python setup.py sdist bdist_wheel

Run the following command again to upload dist:

python -m twine upload --repository pypi dist/*

(use testpypi instead of pypi if needed) `

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

harmonydata-0.1.0.tar.gz (49.2 kB view details)

Uploaded Source

Built Distribution

harmonydata-0.1.0-py3-none-any.whl (33.1 kB view details)

Uploaded Python 3

File details

Details for the file harmonydata-0.1.0.tar.gz.

File metadata

  • Download URL: harmonydata-0.1.0.tar.gz
  • Upload date:
  • Size: 49.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.11.3

File hashes

Hashes for harmonydata-0.1.0.tar.gz
Algorithm Hash digest
SHA256 19d9a6099b5c328f5b721a7b2a94f97abf151ea34cc702bd67f5ce7e01f54ada
MD5 9ccb48480d12b17ef9c28dae7c184e01
BLAKE2b-256 8c1142ce41a1dbc29e878dadc2bdb97cb4ea4cdacc149330808491b585268b48

See more details on using hashes here.

File details

Details for the file harmonydata-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: harmonydata-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 33.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.11.3

File hashes

Hashes for harmonydata-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 84be261aebac05ba65f310a47435bc6796c16555b7f61b15098c7b263c72d5b0
MD5 a738ab3c45e6d24a7245af215f8622ce
BLAKE2b-256 bb82cbcdf8731fffb7205068d752986075bb6acd04a7b433261b37a819801a53

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page