Introduction
This library packages select2 for fanstatic.
This requires integration between your web framework and fanstatic, and making sure that the original resources (shipped in the resources directory in js.select2) are published to some URL.
How to use?
You can import select2 from js.select2 and need it where you want these resources to be included on a page:
>>> from js.select2 import select2 >>> select2.need()
To use the full build use:
>>> from js.select2 import select2_full >>> select2_full.need()
CHANGES
4.0.4-1 (2017-10-16)
Fix a typo in a path in the resources definition.
4.0.4 (2017-10-08)
Upgraded to 4.0.4
Put i18n files inside a dictionary.
Added the ‘full’ javascript resources.
Include the minified CSS.
4.0.1 (2016-01-13)
Merged 4.0.1
README.md to README.rst
4.0.1 (2016-01-13)
Merged 4.0.1
README.md to README.rst
4.0.1+md.1 (2015-12-18)
Upgraded to 4.0.1
4.0.0+md.1 (2015-06-22)
Upgraded to 4.0.0
3.4.1 (2013-06-10)
Minor fix select2_locale_zh-TW.js.
3.4 (2013-06-06)
Updated to 3.4.
Added i18n to __init__.py.
3.3 (2013-01-21)
Added missing files.
3.2 (2013-01-21)
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for js.select2 4.0.4.post1
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.select2-4.0.4.post1.tar.gz | 124.6 kB | Without provenance | Details for js.select2-4.0.4.post1.tar.gz |
Release files / js.select2-4.0.4.post1.tar.gz
| Download URL | js.select2-4.0.4.post1.tar.gz |
|---|---|
| Size | 124.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2feb54e92c1b933490c140111babe2f95c157babcd4fa8baa26d791014cc16d
|
|
BLAKE2b-256 checksum How to use checksums |
d4c7b5a5c3e09a334b1dda1580b48f752cbc278f9513585ebd7adfd01789ad96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for js.select2 4.0.4.post1
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.
