pypi-json-data
Automatically updated pypi API data, available in bulk via git or sqlite (by pypi-data)
packaging.python.org
Python Packaging User Guide (by pypa)
| pypi-json-data | packaging.python.org | |
|---|---|---|
| 6 | 4 | |
| 49 | 1,361 | |
| - | 0.7% | |
| 0.0 | 9.5 | |
| 4 days ago | 7 days ago | |
| Python | ||
| MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pypi-json-data
Posts with mentions or reviews of pypi-json-data.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-16.
-
Infosys leaked FullAdminAccess AWS keys on PyPI for over a year
Unknown, but all(?) GH PRs respond to ".patch" on the end of the PR: https://github.com/orf/pypi-data/pull/2.patch which redirects to https://patch-diff.githubusercontent.com/raw/orf/pypi-data/p...
-
Pypi.org is running a survey on the state of Python packaging
Just to be clear, package metadata already is sort of available through the pypi json api. I've got the entire set of all package metadata here: https://github.com/orf/pypi-data
$ gzcat release_data/c/d/cdklabs.cdk-hyperledger-fabric-network.json.gz | jq '. | to_entries | .[].value.info.requires_dist' | head - GitHub - orf/pypi-data: Automatically updated PyPi API data, available in bulk via git
- PyPI-data: Automatically updated PyPI API data, available in bulk via Git
packaging.python.org
Posts with mentions or reviews of packaging.python.org.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-19.
- ABI compatibility in Python: How hard could it be?
-
Making Sense of pyproject.toml, setup.cfg, and setup.py
[metadata] name = sample_pkg version = 1.0.0 author = Sharon Fitzpatrick description = this is the smallest description long_description = This is a longest description url = https://github.com/pypa/packaging.python.org keywords = python,example [options] python_requires = >=3.8, <4 install_requires = numpy matplotlib [options.extras_require] test = pytest coverage [options.package_data] sample = sample_data.csv'
-
How to Build a pyproject.toml File
# tells pip what build tool to use to build your package [build-system] requires = ["setuptools>=61.0"] build-backend = "setuptools.build_meta" # tells pip how to build your pypi webpage & what dependencies to install [project] name = "sample_pkg" dynamic = ["readme"] version = "0.0.30" authors = [ { name="Sharon Fitzpatrick", email="[email protected]" }] description = "A tool that performs xyz" dependencies = ["matplotlib", "numpy<1.23.0"] license = { file="LICENSE" } requires-python = ">=3.8" classifiers = [ "Programming Language :: Python :: 3", "License :: OSI Approved :: MIT License", "Operating System :: OS Independent", ] # (BETA) tells setuptools you will be using a readme file for the long description field for your pypi profile. [tool.setuptools.dynamic] readme = {file = ["README.md"]} # (OPTIONAL) tells pypi that these urls are where your project's source code and issue tracker reside [project.urls] "Homepage" = "https://github.com/pypa/packaging.python.org" "Bug Tracker" = "https://github.com/pypa/packaging.python.org/issues"
-
Pypi.org is running a survey on the state of Python packaging
If the package is available as a wheel, you don't need to execute code to see what the requirements are; you just need to parse the "METADATA" file. However, the only way to get the METADATA for a wheel (using PyPA standard APIs, anyway) is to download the whole wheel.
For comparison, pacman (the Arch Linux package manager) packages have fairly similar ".PKGINFO" file in them; but in order to support resolving dependencies without downloading the packages, the server's repository index includes not just a listing of the (name, version) tuple for each package, it also includes each package's full .PKGINFO.
Enhancing the PyPA "Simple repository API" to allow fetching the METADATA independently of the wheel would be a relatively simple enhancement that would make a big difference.
----
As I was writing this comment, I discovered that PyPA did this; adopting PEP 658 in March of this year. https://github.com/pypa/packaging.python.org/commit/1ebb57b7...
What are some alternatives?
When comparing pypi-json-data and packaging.python.org you can also consider the following projects:
securitytxt.org - Static website for security.txt.
ring-xous - Pure-Rust port of Ring for 32-bit embedded targets.