AnyBlok Multi Engines
Improve AnyBlok AnyBlok to connect with multi engine for the same database
AnyBlok Multi Engines is released under the terms of the Mozilla Public License.
See the latest documentation
Front Matter
Information about the AnyBlok Multi Engines project.
Project Homepage
AnyBlok is hosted on github - the main project page is at https://github.com/AnyBlok/AnyBlok_Multi_Engines. Source code is tracked here using GIT.
Releases and project status are available on Pypi at http://pypi.python.org/pypi/anyblok_multi_engines.
The most recent published version of this documentation should be at http://doc.anyblok-multi-engines.anyblok.org.
Project Status
AnyBlok multi engines is currently in beta status and is expected to be fairly stable. Users should take care to report bugs and missing features on an as-needed basis. It should be expected that the development version may be required for proper implementation of recently repaired issues in between releases;
Installation
Install released versions of AnyBlok from the Python package index with pip or a similar tool:
pip install anyblok_multi_engines
Installation via source distribution is via the setup.py script:
python setup.py install
Unit Test
Run the test with nose:
pip install nose nosetests anyblok_multi_engines/tests
Dependencies
AnyBlok works with Python 3.3 and later. The install process will ensure that AnyBlok, in addition to other dependencies. The latest version of them is strongly recommended.
Contributors
Anybox team:
Jean-Sébastien Suzanne
Bugs
Bugs and feature enhancements to AnyBlok should be reported on the Issue tracker.
CHANGELOG
1.1.0 (2017-12-23)
[REF] add session event from AnyBlok 0.12.0
1.0.1 (2017-10-08)
[FIX] doc
[FIX] use a better way to install blok wich inherit Query or Session
1.0.0 (2016-07-13)
[IMP] PLugin Registry and get_url for master(s) / slave(s) engines
[ADD] doc
[IMP] unittest
Metadata
Release files for anyblok_multi_engines 1.1.0
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 |
|---|---|---|---|---|
| anyblok_multi_engines-1.1.0.tar.gz | 15.3 kB | Without provenance | Details for anyblok_multi_engines-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anyblok_multi_engines-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for anyblok_multi_engines-1.1.0-py3-none-any.whl |
Total release size: 34.2 kB
Release files / anyblok_multi_engines-1.1.0.tar.gz
| Download URL | anyblok_multi_engines-1.1.0.tar.gz |
|---|---|
| Size | 15.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
134496ad6fc446587e91dacb33b2af3fced504fe8d42ed9238eab523bb6f324a
|
|
BLAKE2b-256 checksum How to use checksums |
1cc6f6cf3a2244d71fd5409af5d48f8495662464ec210f11f6577c1690982027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / anyblok_multi_engines-1.1.0-py3-none-any.whl
| Download URL | anyblok_multi_engines-1.1.0-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9164c5696e981adc4412a719349706cfc7c544acd57626b59ec5f59555e43c9f
|
|
BLAKE2b-256 checksum How to use checksums |
dbe058dcef6e5cbe6558963ea7d3a8608dc78670d0268e7def62b6c347ea1396
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for anyblok_multi_engines 1.1.0
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.