hurry.qunit
How to use?
You can import hurry.qunit from hurry.qunit and .need it where you want these resources to be included on a page:
from hurry.qunit import qunit .. in your page or widget rendering code, somewhere .. qunit.need()
This requires integration between your web framework and hurry.resource, and making sure that the original resources (shipped in the qunit-build directory in hurry.qunit) are published to some URL.
The package has already been integrated for Grok and the Zope Toolkit. If you depend on the hurry.zoperesource package in your setup.py, the above example should work out of the box. Make sure to depend on the hurry.zoperesource package in your setup.py.
CHANGES
0.5 (2010-08-20)
First public release of qunit. qunit doesn’t seem to have releases so we just make up a number. It’s the GIT version as of 2010-08-20.
Download
1 maintainer
Metadata
1 maintainer
Release files for hurry.qunit 0.5
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 | |
|---|---|---|---|---|
| hurry.qunit-0.5.tar.gz | 16.3 kB | Without provenance | Details |
Release files / hurry.qunit-0.5.tar.gz
| Download URL | hurry.qunit-0.5.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30e29c9e0277fc0a17278989b56bdb70e4e6c6be49d0734ab5cf4b77cdeba87d
|
|
BLAKE2b-256 checksum How to use checksums |
41a0e86a0132744af488c1e73dc02b00f38f551e06c1d844fc80185861693947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hurry.qunit 0.5
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.
