Wagtail CodeField
Use CodeField from django-sb-codefield in Wagtail Admin.
This library bridges django-sb-codefield and Wagtail, allowing you to seamlessly integrate robust code editor fields into your Wagtail administration interface.
✨ Features
- Wagtail Integration: Use
CodeFielddirectly in Wagtail admin panels. - Easy Configuration: Simple setup via
INSTALLED_APPS. - Modern Stack: Built for Python 3.11+, Django 4.2+, and Wagtail 5.2+.
📋 Requirements
- Python 3.11.0 or higher
- Django 4.2.0 or higher
- Wagtail 5.2.0 or higher
- django-sb-codefield
📦 Installation
Using pip
pip install wagtail-sb-codefield
Using uv
uv add wagtail-sb-codefield
🚀 Usage
Add wagtail_sb_codefield, django_sb_codefield, and codemirror2 to your INSTALLED_APPS settings:
INSTALLED_APPS = [
# ...
"codemirror2",
"django_sb_codefield",
"wagtail_sb_codefield",
]
For more advanced usage and examples, check out our Wiki.
🛠️ Development
We welcome contributions! Please see our Contribution Guide for details on setting up your development environment, running tests, and submitting pull requests.
The project uses uv for dependency management, ruff for linting, and tox for multi-environment testing.
📜 Changelog
See the CHANGELOG.md for a history of changes.
👥 Contributors
See our list of contributors.
📄 License
This project is licensed under the Apache License 2.0. See the LICENSE file for details.
Metadata
Release files for wagtail-sb-codefield 0.5.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 | |
|---|---|---|---|---|
| wagtail_sb_codefield-0.5.0.tar.gz | 12.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wagtail_sb_codefield-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.0 kB
Release files / wagtail_sb_codefield-0.5.0.tar.gz
| Download URL | wagtail_sb_codefield-0.5.0.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96b93256496cc8c5a89da9b1e3a00f490cc6a7a09ad196ae87d247edf24198b3
|
|
BLAKE2b-256 checksum How to use checksums |
c306d91514219a7865be857a259d06750148411a1b90caa962bf967f45e83336
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / wagtail_sb_codefield-0.5.0-py3-none-any.whl
| Download URL | wagtail_sb_codefield-0.5.0-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94daeea9df21d6f19ac686fbf8452cc3d6d21cc7f8dec025fadc572a7446f6c4
|
|
BLAKE2b-256 checksum How to use checksums |
ef0183ebc8b72baf2b9a594810f958b966e3c3c0baa039067b650d69d2c73809
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for wagtail-sb-codefield 0.5.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.