| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and project gardening
- DRY with dependencies
- Enable coveralls.io and add a coverage tox environment
- A few tiny changes to increase coverage, but we're not at 100%
- Enable testing sphinx docs for all versions
- Publish CHANGES.rst on RTD
- Modern tox.ini and .travis.yml
- Travis was still testing 3.3 and not testing 3.6.
- Remove 'level' qualifiers from XML parsing and ZCML test cases.
They add about 2s to run the tests, but they're important; see #13.
That extra time gets lost in the amount of time it takes to spin
tox anyway.
|
| |
|
| |
|
|
|
|
| |
PyPy yet, since zope.security has still no PyPy support.
|
| |
|
|
|
|
|
|
|
| |
only load the specified translation domain. Allows to move catalogs to
`/usr/share/locale` and avoid loading hundreds of unrelated domains.
|
|
|
|
| |
added a test for our configure.zcml.
|
| |
|
| |
|
|
|
|
| |
We need to defer the merging into the ZCML handler execution phase, as the utilities don't exist yet during the ZCML parsing phase. Thx to Andreas Zeidler for finding and fixing the issue in PlacelessTranslationService in the first place.
|
| |
|
|
|
|
|
| |
with all extras on all levels. The ZCML tests (which also test the [compile]
extra) are on level 2 so they aren't picked up by bin/test.
|
|
|
|
| |
[zcml] extra being installed.
|
| |
|
|
|
|
|
|
| |
negotiate the language when th
e available languages are set globally via `zope_i18n_allowed_languages`. Refactored env variables into a config.py file.
|
|
|
|
| |
an environment variable called `zope_i18n_allowed_languages` now, which is a list of comma or space separated language codes. If the environment variable is set, the ZCML registration will only process those folders which are in the allowed languages list.
|
|
|
|
| |
need to depend on the `zope.i18n [compile]` extra and set an environment variable called `zope.i18n.compile_mo_files` to any True value to enable this option. Bumped the package version to 3.5dev, as we added features and this is not a maintenance release anymore.
|
|
|
|
| |
allows multiple packages to register translations in the same domain. If the same message exists in multiple catalogs the one registered first will take precedence. As an example this allows the messages from the zope domain to be spread across distinct files in various packages.
|
|
|