Django Quickbooks
This is an ongoing project to integrate any Django project with Quickbooks Desktop and Quickbooks Online. Quickbooks integration support for Python 3.6+ and Django 2.0+
| Version: | 0.6.4 |
|---|---|
| Download: | https://pypi.org/project/django-quickbooks/ |
| Source: | https://github.com/weltlink/django-quickbooks/ |
| Keywords: | quickbooks,quickbooks-django,django,quickbooks-desktop,quickbooks-online,qb,qbwc,qwc,integration,django-quickbooks |
Features
Quickbooks Desktop
- Soap session handling for 8 basic quickbooks web connector operations:
- authenticate()
- clientVersion()
- closeConnection()
- connectionError()
- getLastError()
- getServerVersion()
- receiveResponseXML()
- sendRequestXML()
- interactiveDone() - not really implemented
- interactiveRejected() - not really implemented
- interactiveUrl() - not really implemented
- Several Realm management model (for handling multiple web connector integration)
- Realm Session management model (for handling concurrent web connector connections)
- QuickBooks Task management model (for handling object synchronization updates)
- Abstract Processor implementation for easier QBXML response handling
- Abstract Object implementation for easier QBXML bidirectional data conversion
- Abstract Service implementation for easier QBXML object manipulation
Quickbooks Online
...
Roadmap
- Quickbooks Desktop Integration (most of the job is done, but can be improved)
- Add all other remaining quickbooks objects (or most important ones)
- Add all other remaining services (or most important ones)
- Add all other remaining processors (or most important ones)
- Quickbooks Online Integration (or most important ones)
Requirements
- Python 3.6+
- Django 2.0+
- RabbitMQ (or reimplementation of QueueManager)
- Celery (for handling asynchronous tasks)
Notice
Soap server for Quickbooks Web Connector is built on top of Spyne and Lxml.
Setup & Documentation
Contributing
Check out our smaller-roadmap or larger-roadmap to see on what you can help us to improve. Or if you have any problem just drop us a line or open an issue and we’ll work out how to handle it.
Links
References
This library could not be possible without contributions from other open-source projects. Thanks for quickbooks-php for giving the concept of creating quickbooks toolkit. Thanks for Django_to_QuickBooks_API and pyqwc for giving core realization of soap server which made this library possible.
Metadata
Release files for django-quickbooks 0.6.4
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 | |
|---|---|---|---|---|
| django-quickbooks-0.6.4.tar.gz | 40.3 kB | Without provenance | Details |
Release files / django-quickbooks-0.6.4.tar.gz
| Download URL | django-quickbooks-0.6.4.tar.gz |
|---|---|
| Size | 40.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a4001ae0e33484c85ddc9c1f45891285465c953f85489a7d604bedb5c2b809e
|
|
BLAKE2b-256 checksum How to use checksums |
29b8da7baaf986aaee3067d6714d99b5b6b5a122b28bd1c5bbaaaad25544f143
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.6.8
|
Security for django-quickbooks 0.6.4
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.