This release is a pre-release and may not be stable for production use.
casaconfig
Runtime data necessary for CASA operation.
Release Instructions
- 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
Installation
$: pip install casaconfig
Usage
See the casaconfig API documentation on casadocs (links above).
Also see the External Data section of casadocs for additional details
Developers Instructions
- 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
Setting up CASA branches for casaconfig development
The casaconfig build process publishes test wheels to test.pypi.org
In order to test these with Casa packages, two changes are needed in the casa6 repository branch.
- Add a line to casa6/build.conf with the appropriate wheel version. For example:
casaconfig==1.0.3.dev2
- Add the following line with the apppropriate branch name to casa6/casatools/setup.py
META_DATA["install_requires"] = "casaconfig@git+https://github.com/casangi/casaconfig@CAS-14512"
This adds the casaconfig branch as a casatools install time dependency. It will not use the wheel, but rather build the branch in place. This is required in order to avoid adding test.pypi.org as a pip extra-index-url, which might cause other development packages to be installed inadvertently. Note that casaconfig dependency is typically defined in setup.cfg, but the syntax above does not work with setup.cfg.
Preparing the casa6 branch for merge
- Merge the casaconfig branch to main and create a wheel
- Update casa6/build.conf to use that wheel
- Comment out the extra "install_requires" line from setup.py
6 maintainers
Metadata
6 maintainers
Release files for casaconfig 1.5.2.dev1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| casaconfig-1.5.2.dev1.tar.gz | 58.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| casaconfig-1.5.2.dev1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 136.3 kB
Release files / casaconfig-1.5.2.dev1.tar.gz
| Download URL | casaconfig-1.5.2.dev1.tar.gz |
|---|---|
| Size | 58.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a13e8444e17818999911b3f86288a0abf2bba85750b6c85fe2fbab42616e1aad
|
|
BLAKE2b-256 checksum How to use checksums |
b8b77aca171c7cec84dbcbe989c761be8daa668a8a2aba2bf7a197a800aecaad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / casaconfig-1.5.2.dev1-py3-none-any.whl
| Download URL | casaconfig-1.5.2.dev1-py3-none-any.whl |
|---|---|
| Size | 77.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef86ba6cabca7f85978b5438c6226853a701eccb6755f2ce60eca8a45c10229a
|
|
BLAKE2b-256 checksum How to use checksums |
64f7106db8f884b574d0fed28146a38fbd395077b6666ec72242769894c1fa52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
