E360 TDImport Service Client
E360 TDImport Service Client for Python
Introduction
add info
Features
add info
Usage
add info
Development
Requires Python 3.12+. Dependencies are managed with uv.
Internal wheels (including clients_core) resolve from e360-pypi (Artifactory). On VPN/corporate network:
export UV_INDEX_URL=https://rwes-artifactory01.internal.imsglobal.com/artifactory/api/pypi/e360-pypi/simple
Commands
uv sync --group dev
uv run ruff check tdimport_client tests
uv run ruff format tdimport_client tests
uv run pytest
SFTP integration tests (optional)
Unit tests mock paramiko. To exercise a real SFTP server locally:
docker compose -f docker-compose.integration.yml up -d
RUN_SFTP_INTEGRATION=1 uv run pytest tests/integration -v
docker compose -f docker-compose.integration.yml down
Production upload path remains /D:/td-bundles. Integration tests override UPLOAD_PATH to /upload (atmoz/sftp chroot home).
Publishing to public PYPI
- To enable publishing rename
DISABLED_Pypifile.jsontoPypifile.json. repository_urlis the address of the repository where to upload to.api_token_idis a guid for Jenkins secret storage holding an API Token.
Metadata
Release files for tdimport-client 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tdimport_client-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / tdimport_client-0.3.2-py3-none-any.whl
| Download URL | tdimport_client-0.3.2-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
befbb98506c773e487852438a719070412b113d8c60f29f0274efec03d0cd060
|
|
BLAKE2b-256 checksum How to use checksums |
5b5e68ca40ad7ff00dc1db0c02e478b3864870873bb32eb2f1402d44dec51682
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for tdimport-client 0.3.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.