namex
PyPIv0.1.0A simple utility to separate the implementation of your Python package and its public API surface.
Not recommended for new projects
No — namex should not be adopted for new projects. Last published 471 days ago. 2 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 471 days ago. 2 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 5.8 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- 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 namex to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Python
- No constraint declared
Used by
Popular packages that depend on namex.
Relationship graph
Dependencies (left) and dependents (right) of namex.
Frequently installed together
Fundamental package for array computing in Python
Render rich text, tables, progress bars, syntax highlighting, markdown and more to the terminal
Core utilities for Python packages
Abseil Python Common Libraries, see https://github.com/abseil/abseil-py.
Read and write HDF5 files from Python
ml_dtypes is a stand-alone implementation of several NumPy dtype extensions used in machine learning.
Optimized PyTree Utilities.
Release history
2 releases in the last two years, typically about 8 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.1.0latest | 1 year ago | 5.8 KB | — |
| 0.0.9 | 1 year ago | 5.7 KB | — |
| 0.0.8 | 2 years ago | 5.7 KB | — |
| 0.0.7 | 3 years ago | 5.6 KB | — |
| 0.0.6 | 3 years ago | 5.6 KB | — |
| 0.0.5 | 3 years ago | 5.6 KB | — |
| 0.0.4 | 3 years ago | 5.6 KB | — |
| 0.0.3 | 3 years ago | 5.6 KB | — |
| 0.0.2 | 3 years ago | 5.6 KB | — |
| 0.0.1 | 3 years ago | 5.5 KB | — |
Overview
namex is an PyPI package that a simple utility to separate the implementation of your Python package and its public API surface. It has 1 known dependents in the graph. The latest version is 0.1.0.
Who should use it
Teams working in the PyPI ecosystem who need a simple utility to separate the implementation of your Python package and its public API surface 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
- Zero runtime dependencies — minimal footprint.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use namex?
No — namex should not be adopted for new projects. Last published 471 days ago. 2 releases in the last 2 years. No license declared — you have no explicit right to use this code.
How do I install namex?
Run `pip install namex` to add namex to your PyPI project.
What license is namex released under?
No license was detected in namex's metadata; review the repository before use.
How popular is namex?
PyPI does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on namex.
Is namex still maintained?
The most recent release of namex (v0.1.0) was published 1 year ago.