python-alkivi-odoo-client
Odoo python client used at Alkivi. Based on odoorpc on which we add additional fonction.
Package
Example
from alkivi.odoo import client as odoo
# Using default configuration
client = odoo.Client()
# Using specific endpoint
client = odoo.Client(endpoint='prod')
# TODO
Credentials
Credentials are fetched from, in priority order: - ./odoo.conf (script directory) - $HOME/.odoo.conf - /etc/odoo.conf
Example
[default]
; general configuration: default endpoint
endpoint=dev
[dev]
; configuration specific to 'dev' endpoint
protocol=jsonrpc+ssl
port=443
url=odoo.domain
version=8.0
db=odooDatabase
user=pdooUser
password=AweSomePasswOrd
[prod]
; other configuration
Tests
Testing is set up using pytest and coverage is handled with the pytest-cov plugin.
Run your tests with py.test in the root directory.
Coverage is ran by default and is set in the pytest.ini file. To see an html output of coverage open htmlcov/index.html after running the tests.
TODO
Travis CI
There is a .travis.yml file that is set up to run your tests for python 2.7 and python 3.2, should you choose to use it.
TODO
Metadata
Release files for alkivi-odoo-client 1.0.3
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 |
|---|---|---|---|---|
| alkivi_odoo_client-1.0.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / alkivi_odoo_client-1.0.3-py2.py3-none-any.whl
| Download URL | alkivi_odoo_client-1.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e52c5bb0e3f66bf09fbb9b56e789140a3b8357aea68faa8002d9060ab3c4146d
|
|
BLAKE2b-256 checksum How to use checksums |
21b285c69cb29c52d7de0688d73f91dc6cdba043162c2efd74c158734b394686
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for alkivi-odoo-client 1.0.3
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.