A Pygments plugin for IPython code & console sessions
IPython is an interactive Python shell. Among other features,
it adds some special convenience syntax, including %magics, !shell commands
and help?. This package contains lexers for these, to use with the Pygments syntax
highlighting package.
- The
ipythonlexer should be used where only input code is highlighted - The
ipythonconsolelexer works for an IPython session, including code, prompts, output and tracebacks.
These lexers were previously part of IPython itself (in IPython.lib.lexers),
but have now been moved to a separate package.
Release files for ipython-pygments-lexers 1.1.1
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 |
|---|---|---|---|---|
| ipython_pygments_lexers-1.1.1.tar.gz | 8.4 kB | With provenance | Details for ipython_pygments_lexers-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ipython_pygments_lexers-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for ipython_pygments_lexers-1.1.1-py3-none-any.whl |
Total release size: 16.5 kB
Release files / ipython_pygments_lexers-1.1.1.tar.gz
| Download URL | ipython_pygments_lexers-1.1.1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09c0138009e56b6854f9535736f4171d855c8c08a563a0dcd8022f78355c7e81
|
|
BLAKE2b-256 checksum How to use checksums |
ef4c5dd1d8af08107f88c7f741ead7a40854b8ac24ddf9ae850afbcf698aa552
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 17, 2025.
Transparency logRelease files / ipython_pygments_lexers-1.1.1-py3-none-any.whl
| Download URL | ipython_pygments_lexers-1.1.1-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9462224a505ade19a605f71f8fa63c2048833ce50abc86768a0d81d876dc81c
|
|
BLAKE2b-256 checksum How to use checksums |
d9331f075bf72b0b747cb3288d011319aaf64083cf2efef8354174e3ed4540e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 17, 2025.
Transparency logSecurity for ipython-pygments-lexers 1.1.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ipython_pygments_lexers-1.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 17, 2025.
Transparency logA 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.
