Skip to content

Latest commit

 

History

History
175 lines (129 loc) · 5 KB

README.dev.md

File metadata and controls

175 lines (129 loc) · 5 KB
Raw

Documentation for developers

Install

# get a copy of the cff-converter-python software
git clone https://github.com/citation-file-format/cff-converter-python.git
# change directory into cff-converter-python
cd cff-converter-python
# make a virtual environment named env
python3 -m venv env
# activate the virtual environment
source env/bin/activate
# upgrade pip, wheel, setuptools
python3 -m pip install --upgrade pip wheel setuptools
# install cffconvert and the 'dev' set of additional dependencies
python3 -m pip install --editable .[dev]

Running tests

Running the tests requires an activated virtual environment with the development tools installed.

# (from the project root)

# run all tests
python3 -m pytest test/

# tests for consistent file naming
bash test/test_consistent_file_naming.sh dir=test/
bash test/test_consistent_file_naming.sh dir=livetest/

# tests for consistent versioning
python3 -m pytest test/test_consistent_versioning.py

Running linters locally

For linting we use prospector and to sort imports we will use isort. Running the linters requires an activated virtual environment with the development tools installed.

# linter
prospector

# recursively check import style for the cffconvert module only
isort --check-only cffconvert

# recursively check import style for the cffconvert module only and show
# any proposed changes as a diff
isort --check-only --diff cffconvert

# recursively fix import style for the cffconvert module only
isort cffconvert

Developers should consider enabling automatic linting with prospector and isort on commit by enabling the git hook from .githooks/pre-commit, like so:

git config --local core.hooksPath .githooks

For maintainers

Making a release

  1. make sure the release notes are up to date

  2. preparation

    # remove old cffconvert from your system if you have it
python3 -m pip uninstall cffconvert

# this next command should now return empty
which cffconvert

# install the package to user space, using no caching (can bring to light dependency problems)
python3 -m pip install --user --no-cache-dir .
# check if cffconvert works, e.g.
cffconvert --version

# run the tests, make sure they pass
python3 -m pip pytest test

# git push everything, merge into main as appropriate

  3. publishing on test instance of PyPI

    # verify that everything has been pushed and merged by testing as follows
cd $(mktemp -d --tmpdir cffconvert-release.XXXXXX)
git clone https://github.com/citation-file-format/cff-converter-python.git .
python3 -m venv env
source env/bin/activate
python3 -m pip install --upgrade pip wheel setuptools
python3 -m pip install --no-cache-dir .

# register with PyPI test instance https://test.pypi.org

# remove these directories if you have them
rm -rf dist
rm -rf cffconvert-egg.info
# make a source distribution:
python setup.py sdist
# make a wheel
python setup.py bdist_wheel 
# install the 'upload to pypi/testpypi tool' aka twine
pip install .[publishing]
# upload the contents of the source distribution we just made (requires credentials for test.pypi.org)
twine upload --repository-url https://test.pypi.org/legacy/ dist/*

  4. Checking the package

    Open another shell but keep the other one. We'll return to the first shell momentarily.

    Verify that there is a new version of the package on Test PyPI https://test.pypi.org/project/cffconvert/

    python3 -m pip -v install --user --no-cache-dir \
--index-url https://test.pypi.org/simple/ \
--extra-index-url https://pypi.org/simple cffconvert

# check that the package works as it should when installed from pypitest

  5. FINAL STEP: upload to PyPI

    Go back to the first shell, then (requires credentials for pypi.org)

    twine upload dist/*

  6. Make the release on GitHub

  7. Go to Zenodo, log in to inspect the draft. Then click Publish to finalize it.

Building the docker image

# (requires 2.0.0 to be downloadable from PyPI)
docker build --tag cffconvert:2.0.0 .
docker build --tag cffconvert:latest .

See if the Docker image works as expected:

docker run --rm -v $PWD:/app cffconvert --validate
docker run --rm -v $PWD:/app cffconvert --version
docker run --rm -v $PWD:/app cffconvert
# etc

Publishing on DockerHub

See https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub for more information on publishing.

# log out of any dockerhub credentials
docker logout

# log back in with username 'citationcff' credentials
docker login

# re-tag existing images
docker tag cffconvert:2.0.0 citationcff/cffconvert:2.0.0
docker tag cffconvert:latest citationcff/cffconvert:latest

# publish
docker push citationcff/cffconvert:2.0.0
docker push citationcff/cffconvert:latest