</>PackageGraphPackageGraph

ipython-pygments-lexers

PyPIv1.1.1

Defines a variety of Pygments lexers for highlighting IPython code.

Not recommended for new projects

No — ipython-pygments-lexers should not be adopted for new projects. Last published 600 days ago. 3 releases in the last 2 years. No license declared — you have no explicit right to use this code.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • CMaintenance: grade C, Fair — worth a look.

    Last published 600 days ago. 3 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package, about 7.9 KB installed (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package lists no maintainer.

  • FLicense: grade F, Failing.

    No license declared — you have no explicit right to use this code.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding ipython-pygments-lexers to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

7.9 KB
Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Compatibility

Python
python >=3.8

Dependencies

Declared by ipython-pygments-lexers v1.1.1. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

pygments

Used by

Popular packages that depend on ipython-pygments-lexers.

Relationship graph

Dependencies (left) and dependents (right) of ipython-pygments-lexers.

ipythonipython-pygments-…
ipython-pygments-lexers dependencies dependents

Frequently installed together

Release history

3 releases in the last two years, typically about 1 day apart.

Recent versions of ipython-pygments-lexers
VersionPublishedSizeLicense
1.1.1latest1 year ago7.9 KB
1.1.01 year ago6.9 KB
1.0.01 year ago6.9 KB

Overview

ipython-pygments-lexers is an PyPI package that defines a variety of Pygments lexers for highlighting IPython code. It has 1 known dependents in the graph. The latest version is 1.1.1.

Who should use it

Teams working in the PyPI ecosystem who need defines a variety of Pygments lexers for highlighting IPython code and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your PyPI stack.

Pros

  • Lean dependency tree (1 direct dependencies).

Cons

  • No license detected — review usage terms before adopting.

Auto-generated from collected registry metadata. No external claims are inferred.

Frequently asked questions

Should I use ipython-pygments-lexers?

No — ipython-pygments-lexers should not be adopted for new projects. Last published 600 days ago. 3 releases in the last 2 years. No license declared — you have no explicit right to use this code.

How do I install ipython-pygments-lexers?

Run `pip install ipython-pygments-lexers` to add ipython-pygments-lexers to your PyPI project.

How many dependencies does ipython-pygments-lexers have?

ipython-pygments-lexers declares 1 direct dependency and pulls in 1 packages in total once its runtime tree is resolved totalling about 7.9 KB on disk.

What license is ipython-pygments-lexers released under?

No license was detected in ipython-pygments-lexers's metadata; review the repository before use.

How popular is ipython-pygments-lexers?

PyPI does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on ipython-pygments-lexers.

Is ipython-pygments-lexers still maintained?

The most recent release of ipython-pygments-lexers (v1.1.1) was published 1 year ago.