⚠️ WORK IN PROGRESS ⚠️
This library is a Python wrapper for accessing Somconnexio's Zoho.
Resources
- CRMLeads
Installation
$ pip install zoho-somconnexio-python-client
Configuration Environment
You need define the Zoho CRM_CLIENT_ID, CRM_ORGANIZATION_ID, CRM_CLIENT_SECRET and ZOHO_CRM_STORE as environment variables. You need define:
ZOHO_CRM_CLIENT_ID=<YOUR CLIENT ID>
ZOHO_CRM_CLIENT_SECRET=<YOUR CLIENT SECRET>
ZOHO_CRM_ORGANIZATION_ID=<YOUR ORGANIZATION>
ZOHO_CRM_STORE=<YOUR PATH TO STORE TOKEN & LAYOUTS>
If this envvars are not defined, a exception will be raised with the name of the envvar not defined.
To execute functions, you need define:
ZOHO_APIKEY_ACTIVAT_FROM_ODOO=<FUNCTION_API_KEY>
Development
Setup environment
- Install
pyenv
curl https://pyenv.run | bash
- Build the Python version
pyenv install 3.11.9
- Create a virtualenv
pyenv virtualenv 3.11.9 zoho-somconnexio-python-client
- Activate virtualenv
pyenv activate zoho-somconnexio-python-client
- Install dependencies
pyenv exec pip install -r requirements-dev.txt
- Install pre-commit hooks
pyenv exec pre-commit install
Run tests
To run the test you can run:
$ tox
Also you can run only the tests running:
$ pytest .
and if you want the coverage info:
$ pytest --cov .
Formatting
We use pre-commit to execute Black as formatter.
Release process
Update CHANGELOG.md following this steps:
- Add any entries missing from merged merge requests.
- Duplicate the
[Unreleased]header. - Replace the second
Unreleasedwith a version number followed by the current date. Copy the exact format from previous releases.
Then, you can release and publish the package to PyPi:
- Update the
__version__var in__init__.pymatching the version you specified in the CHANGELOG. - Open a merge request with these changes for the team to approve
- Merge it, add a git tag on that merge commit and push it.
- Once the pipeline has successfully passed, go approve the
publishstep.
Metadata
Release files for zoho-somconnexio-python-client 0.1.6
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 |
|---|---|---|---|---|
| zoho_somconnexio_python_client-0.1.6.tar.gz | 12.7 kB | Without provenance | Details for zoho_somconnexio_python_client-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zoho_somconnexio_python_client-0.1.6-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for zoho_somconnexio_python_client-0.1.6-py2.py3-none-any.whl |
Total release size: 29.9 kB
Release files / zoho_somconnexio_python_client-0.1.6.tar.gz
| Download URL | zoho_somconnexio_python_client-0.1.6.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad18c98fe3bcda2f809157d8427c11dd05dea29a9544d0eab7d875781fd148cd
|
|
BLAKE2b-256 checksum How to use checksums |
77bf76476a9c8df2ddb5b545b2593b4d9a3e49410eb769794fc431dbcbb22ed3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / zoho_somconnexio_python_client-0.1.6-py2.py3-none-any.whl
| Download URL | zoho_somconnexio_python_client-0.1.6-py2.py3-none-any.whl |
|---|---|
| Size | 17.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
49d8decacf77767778fe5e0aff9638c36c76e47b1018f7a61040b61ecc239693
|
|
BLAKE2b-256 checksum How to use checksums |
de0f72a913b31cc552e4c4f79a2101013bef7cd6c49d44586310046ae7f4ff8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for zoho-somconnexio-python-client 0.1.6
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.