Expedition-Python
Description
Expedition is a Windows-based software application for sailing navigation and racing. It has been used in multiple Volvo Ocean Race, America's Cup and Grand Prix events and is the most advanced and usable software available. It can be purchased from Expedition Marine.
This Expedition-Python library is a module for reading and writing data from Expedition. It provides a simple and intuitive API for reading and writing variables and system variables in Expedition. You can also do basic route and waypoint manipulation.
Installation
To install the Expedition module, you can use pip:
pip install Expedition-Python
Development Installation
For development, use uv to create a virtual environment and install the package in editable mode with dev tools:
git clone https://github.com/TTCMarine/Expedition-Python.git
cd Expedition-Python
uv sync
Alternatively, you can use pip: pip install -e .
Platform Support
- Windows: Full support with the Expedition DLL
- macOS/Linux: Mock implementation available for development and testing (see note below)
Note for macOS/Linux users: On non-Windows platforms, the package installs a mock implementation that allows you to develop and test code without the actual Expedition DLL. All methods are available but return dummy values. This is useful for developing code that will run on Windows.
Usage
There is a static method called from_default_location that can be used to create an instance of the ExpeditionDLL
class.
This method will attempt to locate the Expedition DLL file and create an instance of the ExpeditionDLL. This relies on
the installation directory being in a registry key, so it may not work for all installations.
Note on 64 vs 32-bit: If you are using a 32-bit version of Expedition, then you need to use a 32-bit version of Python.
Here's a simple example of how to use the Expedition module:
from Expedition import ExpeditionDLL, Var, SysVar
# Create an instance of the ExpeditionDLL class
expedition = ExpeditionDLL.from_default_location()
# Set and get a variable value
expedition.set_exp_var_value(Var.Bsp, 10.4)
value = expedition.get_exp_var_value(Var.Bsp)
print(value) # Outputs: 10.4
Contributing
Contributions are welcome! If you would like to contribute to the Expedition module:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests to ensure everything works
- Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Please ensure your code follows the project's style guidelines and includes tests for new features.
Development
Requirements
- Python 3.10 or higher (3.12 recommended for local development; see
.python-version) - uv for development (optional but recommended)
- For Windows: Expedition software installed
Expedition API headers (local only)
Expedition’s C headers (ExpDLL.h, user_channels.h, sys_channels.h) are proprietary and are not committed or shipped with this package. On Windows, after installing or updating Expedition, sync them for local development and AI-assisted binding work:
uv run python scripts/sync_expedition_headers.py
uv run python scripts/generate_enums_from_headers.py --write
uv run python scripts/check_enums_against_headers.py
Headers are copied to reference/expedition/ (gitignored). Enums in Expedition/enums.py are generated from those headers (see CHANGELOG.md for 2.0 breaking renames). See reference/README.md and AGENTS.md.
The wrapper supports both legacy ExpDLL and Expedition API 1.2 (ExpeditionX): batch var helpers fall back to single-var calls when needed; auxiliary APIs such as boat colour, marks, and AIS CPA require a legacy DLL.
Running Tests
After uv sync, run tests with:
uv run pytest tests/ -v
You can also use unittest: python -m unittest discover tests
Note: Tests require the Expedition DLL to be installed on Windows. On non-Windows platforms or when the DLL is not found, tests will be automatically skipped. This is expected behavior and allows the test suite to run on CI/CD systems without Expedition installed.
Building the Package
The package uses modern Python packaging with pyproject.toml. To build:
uv build
This will create distribution files in the dist/ directory.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for Expedition-Python 2.1.2
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 |
|---|---|---|---|---|
| expedition_python-2.1.2.tar.gz | 17.1 kB | With provenance | Details for expedition_python-2.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| expedition_python-2.1.2-py3-none-any.whl | Python 3 | none | any | Details for expedition_python-2.1.2-py3-none-any.whl |
Total release size: 30.5 kB
Release files / expedition_python-2.1.2.tar.gz
| Download URL | expedition_python-2.1.2.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c0a8bd9367ec8dbf6b68bdb588b6233b7765f41e5d717507fdb6f06c1e38dec
|
|
BLAKE2b-256 checksum How to use checksums |
1963e410fc9475048ddb47021e11683803777f3de467e295247f1c4fadfefa45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 23, 2026.
Transparency logRelease files / expedition_python-2.1.2-py3-none-any.whl
| Download URL | expedition_python-2.1.2-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e9aa9361f0e14631a592b1f7bf28e3d27bbc228b4e86dc847fe58c0f6ff53c0
|
|
BLAKE2b-256 checksum How to use checksums |
e3fb742a1edebbb71822e8cf0a775e6c6263d711e563de8df98ff8d68dc2784b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 23, 2026.
Transparency logSecurity for Expedition-Python 2.1.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for expedition_python-2.1.2.tar.gz
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 Jun 23, 2026.
Transparency logA 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.