js.i18n
Introduction
This library packages i18n-js for fanstatic. It is aware of different modes (normal, minified).
This requires integration between your web framework and fanstatic, and making sure that the original resources (shipped in the resources directory in js.i18n) are published to some URL.
The package is maintained on js.i18n at bitbucket.org.
How to use?
You can import i18n-js from js.i18n and need it where you want these resources to be included on a page:
>>> from js.i18n import i18n >>> i18n.need()
CHANGES
0.0.0
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for js.i18n 0.0.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 |
|---|---|---|---|---|
| js.i18n-0.0.0.tar.gz | 8.7 kB | Without provenance | Details for js.i18n-0.0.0.tar.gz |
Release files / js.i18n-0.0.0.tar.gz
| Download URL | js.i18n-0.0.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddcd4b35b7f75933175a0b93c15c3a8802f24692d195782cc8fbd013b6b42d5b
|
|
BLAKE2b-256 checksum How to use checksums |
d75dd43d06c8b5e91ce7fcde7344bffd2cbfb7d340565864273dd6b62e7e485b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for js.i18n 0.0.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.
