Runtime data necessary for CASA operation.
- Create a release branch with a version name (ie v1.6.2)
- Ensure the version number in pyproject.toml on the branch is set correctly
- Create a tag of the release branch (ie v1.6.2-1)
- Github Action runs automatically to publish a pip package to pypi
$: pip install casaconfig
See the casaconfig API documentation on casadocs (links above).
Also see the External Data section of casadocs for additional details
- every push to the casaconfig repository will push a new wheel to test pypi
- the version in pyproject.toml must be updated before each push so that the wheel has a unique name (e.g. "1.2.3dev2", where "dev?" could be incremented during development; see the specification for more information about valid version signifiers)
- When testing with a casatools build, "pip install" the development casaconfig wheel before running any tests - it may be installed before casatools is installed or after since the casatools build does not depend on casasconfig (uninstall any already installed casaconfig if necessary).
- For release, follow the above instructions.
Wheels can be built locally following the same process used by the CI actions. To install the build-system dependencies as defined in pyproject.toml and then generate a source distribution and wheel:
python3 -m pip install build setuptools --user
python3 -m build
This will create:
casaconfig.egg-info
├── PKG-INFO
├── SOURCES.txt
├── dependency_links.txt
├── requires.txt
└── top_level.txt
dist
├── casaconfig-[VERSION]-py3-none-any.whl
└── casaconfig-[VERSION].tar.gz