This package provides a i18n aware content base class for Zope3 using the mongodb instead of ZODB.
CHANGES
3.2.1 (2025-10-09)
bugfix; adjust conditional check for request and negotiator. Check explicit for None
3.2.0 (2025-06-15)
Compatibility with Python3
3.1.0 (2018-04-24)
feature: added I18nMongoObject
cleanup: I18nMongoItemBase moved from m01.i18n.item to m01.i18n.base.
3.0.0 (2017-01-11)
feature: added level 2 test using mongodb stub server and use the fake mongodb setup for default test runner
support pymongo >= 3.0.0 and use 3.0.0 as package version and reflect pymongo >= 3.0.0 compatibility
0.5.0 (2013-06-28)
initial release
1 maintainer
Metadata
1 maintainer
Release files for m01.i18n 3.2.1
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 |
|---|---|---|---|---|
| m01.i18n-3.2.1.tar.gz | 164.2 kB | Without provenance | Details for m01.i18n-3.2.1.tar.gz |
Release files / m01.i18n-3.2.1.tar.gz
| Download URL | m01.i18n-3.2.1.tar.gz |
|---|---|
| Size | 164.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90e354210fbd9afa8174a7002fe51bcc914bca101f30ed72eaca394dfa59877f
|
|
BLAKE2b-256 checksum How to use checksums |
570d24b90b6e516602f97bae543f0b7d3c1a82d83ef6d83b75f13b5624164508
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.27.1 setuptools/44.1.1 requests-toolbelt/1.0.0 tqdm/4.64.1 CPython/2.7.18
|
Security for m01.i18n 3.2.1
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.
