Installation

Requirements

Package metadata declares Python 3.6 or later and operating-system independence. The package depends on pandas, requests, AWS and SSH/SFTP libraries, Selenium tooling, and other runtime packages. A normal pip installation resolves them automatically.

Test the Python version you deploy

The declared lower bound is Python 3.6, but some transitive dependencies may have raised their own Python requirements since this package release. Use a pinned environment and test installation on the exact interpreter used in production.

Install from PyPI

Use the interpreter that will run your application:

python -m pip install pacifico

For a clean project environment:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install pacifico

On Windows PowerShell, activate with:

.venv\Scripts\Activate.ps1

Install a specific release

Reproducible deployments should pin a version:

python -m pip install "pacifico==0.0.9.42"

Record the full environment with the dependency-management approach used by your project. Avoid relying on a fresh, unpinned dependency resolution for production rebuilds.

Upgrade

python -m pip install --upgrade pacifico

Review the request reference, run representative metadata/value/report requests in a non-production environment, and confirm DataFrame schemas before promoting an upgrade.

Notebook installation

In Jupyter, use the kernel-aware pip magic:

%pip install pacifico

Restart the kernel after installation if the import was attempted before the package was installed. The leading ! used in older notebook examples invokes a shell; %pip is generally better at targeting the active kernel.

Verify the import

import pacifico
from pacifico import Country, Fixing, Quality, VersionType

print(pacifico.request)
print(Fixing.EOD)

The package exports:

  • pacifico.request
  • Country
  • Fixing
  • Quality
  • VersionType

Other modules under pacifico.core and pacifico.util are implementation details, even when importable. Build application code around the root exports above.

Editable installation for contributors

The repository uses a src layout and includes a private shared-code submodule. Contributors should clone recursively:

git clone --recurse-submodules <REPOSITORY_URL>
cd pacifico-client
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e .

If the repository is already cloned:

git submodule update --init --recursive
python -m pip install -e .

See Development and builds for distribution and documentation commands.

Common installation failures

Symptom Likely cause Action
ModuleNotFoundError: pacifico pip targeted another interpreter Run python -m pip show pacifico with the same python used to start the program
Failure building a native dependency Missing platform build tools or an incompatible old dependency Upgrade pip, use a supported Python, and prefer a wheel-enabled environment
ModuleNotFoundError under pacifico_devel in an editable checkout Private submodule missing Initialize the repository submodules
Notebook still cannot import after installation Kernel has stale state or uses another interpreter Restart the kernel and inspect sys.executable