This project has been archived by its maintainers, and is no longer receiving any updates.
zope.mkzeoinstance
This package provides a single script, mkzeoinstance, which creates a standalone ZEO server instance.
Changelog
6.0 (2024-09-16)
Add support for Python 3.12.
DRop support for Python 3.7.
5.1.1 (2023-05-05)
Make blob_dir parameter added in 5.1 optional. (#18)
5.1 (2023-04-28)
Add configuration option -b resp. --blobs for passing blob directory path. (#16)
5.0 (2023-02-09)
Drop support for Python 2.7, 3.4, 3.5, 3.6.
Add support for Python 3.7, 3.8, 3.9, 3.10, 3.11.
Drop support for running tests using python setup.py test.
4.1 (2017-05-26)
Fix generated runzeo and zeoctl scripts to run with ZEO 5.
4.0 (2017-02-28)
100% unit test coverage.
Drop support for Python 2.6.
Add support for Python 3.4, 3.5, and 3.6.
Move dependency from ZODB3 -> [zdaemon, ZODB, ZEO]. Even though this package doesn’t actually import anything from the last two, the generated instance won’t be usable unless the host python has them installed.
3.9.6 (2014-12-23)
Add support for testing on Travis, and with tox.
3.9.5 (2011-10-31)
Place the socket used by the zeoctl control process to conmmunicate with its runzeo daemaon in $INSTANCE_HOME/var, instead of $INSTANCE_HOME/etc (which would idealy not be writable by the process). See: https://bugs.launchpad.net/zope.mkzeoinstance/+bug/175981
3.9.4 (2010-04-22)
Rename the script / package mkzeoinstance to avoid clashing with the script bundled with ZODB.
Add an option to spell the host interface to be listened on, as well as the port the generated ZEO server configuration. Thanks to Igor Stroh for the patch. See: https://bugs.launchpad.net/zodb/+bug/143361
Fix generated templates to cope with the move of zdaemon code into its own project.
Fork from the version of the mkzeoinst script contained in ZODB 3.9.4.
Metadata
Release files for zope.mkzeoinstance 6.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 | |
|---|---|---|---|---|
| zope_mkzeoinstance-6.0.tar.gz | 12.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope.mkzeoinstance-6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.8 kB
Release files / zope_mkzeoinstance-6.0.tar.gz
| Download URL | zope_mkzeoinstance-6.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
337c3e882bcab7ccf3cc95a1699f94ce8823528c07b452d88be523bda6d05abd
|
|
BLAKE2b-256 checksum How to use checksums |
fcf693cf22fdb1e2b09d3fc823bc3fff680547430c353d874606b632b39fc0e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Release files / zope.mkzeoinstance-6.0-py3-none-any.whl
| Download URL | zope.mkzeoinstance-6.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
262deed2024b0a4aaa9cfb55568e5ab986e118ff3d4a8ff84107582bcd525958
|
|
BLAKE2b-256 checksum How to use checksums |
410b5bc1e4b6e8ff42280dd799ddf63a7c6b1ad5fe0be0ab6d07009c29c3d836
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Security for zope.mkzeoinstance 6.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.