Skip to main content

django-static-jquery3

Django application contains jquery and jquery-plugins' static files.

  • Mostly we use jquery plugins, for django ships with jquery already.
  • We put many jquery plugins in this package, so that we will not use jquery's version from now on.
  • Remove django from requirements.txt. We still keep django's file structure, but we will NOT need anything about django.

jQuery License

jQuery Plugins Licenses

  • Plugins may NOT a part of jquery.
  • Plugins obey their own licenses.

Install

pip install django-static-jquery3

Installed Plugins

  • jquery/plugins/jquery.cookie.js
  • jquery/plugins/jquery.parseQuery.js
  • jquery/plugins/jquery.utils.js
  • jquery/plugins/jquery.jstree/jstree.js

Usage

pro/settings.py

INSTALLED_APPS = [
    ...
    "django_static_jquery3",
    ...
]

app/template/app/index.html

{% load static %}

<script src="{% static "jquery/jquery.js" %}"></script>
<script src="{% static "jquery/plugins/jquery.cookie.js" %}"></script>
<script src="{% static "jquery/plugins/jquery.parseQuery.js" %}"></script>
<script src="{% static "jquery/plugins/jquery.utils.js" %}"></script>
<script src="{% static "jquery/plugins/jquery.cookie.js" %}"></script>

About releases

  • The first number is our release number.
  • The other three numbers are the same with jquery's release version.

Releases

v6.3.7.2

  • Doc update.

v6.3.7.1

  • Add jquery.parseQuery plugin.

v5.3.7.1

  • Upgrade jquery to v3.7.1.

v5.1.0

  • Add jquery.jstree plugin.

v5.0.0

  • Rename jquery3 folder to jquery.
  • Mostly we use jquery plugins, for django ships with jquery already.
  • We put many jquery plugins in this package, so that we will not use jquery's version from now on.
  • Remove django from requirements. We still keep django's file structure, but we will need anything about django.

v3.4.1.1

  • Add jquery plugin: jquery.cookie.
  • Fix document.

v3.4.1.0

  • Upgrade jquery to 3.4.1.

v3.3.1.1

  • Upgrade jquery to 3.3.1.

v3.2.1

  • First release with jquery 3.2.1.

Metadata

Release files for django-static-jquery3 6.3.7.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-static-jquery3 6.3.7.2
File Size Uploaded Provenance Actions
django_static_jquery3-6.3.7.2.tar.gz 443.9 kB Without provenance Details for django_static_jquery3-6.3.7.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-static-jquery3 6.3.7.2
File Interpreter ABI Platform Actions
django_static_jquery3-6.3.7.2-py3-none-any.whl Python 3 none any Details for django_static_jquery3-6.3.7.2-py3-none-any.whl

Total release size: 897.5 kB

Release files / django_static_jquery3-6.3.7.2.tar.gz

Download URL django_static_jquery3-6.3.7.2.tar.gz
Size 443.9 kB
Tags Source
SHA-256 checksum
How to use checksums
45524cf4bf6b76447d8496efcfd5796dd221652d781fa6bfa11323aba9c15fd1
BLAKE2b-256 checksum
How to use checksums
30ce9dfb7fd802486bc88cb9ae3fa3eb3a3b08303c4a6190f6e067d39a46938e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.11.12

Release files / django_static_jquery3-6.3.7.2-py3-none-any.whl

Download URL django_static_jquery3-6.3.7.2-py3-none-any.whl
Size 453.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
db4308ec40ef265224e1d3fd110e577cabef812f7e2166386d893f7e11accaec
BLAKE2b-256 checksum
How to use checksums
beeed87dd086abf784eacdfe0dea9883deb6d2bf469306aa7ab0419b1b2cac29
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.11.12

Security for django-static-jquery3 6.3.7.2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page