NonGNU ELPA vs pypiserver
NonGNU ELPA
elpa.nongnu.orgpypiserver
github.comSide by side
| Figure | NonGNU ELPA | pypiserver |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Package Registries | 7.3 (#22) | 8.3 (#11) |
| Integrations | The archive lists packages that connect Emacs with other tools and services, including Dockerfile mode, a Mastodon API client, and an rTorrent frontend. | The documentation shows integration with pip, easy_install, setuptools, twine, Docker, and reverse proxies including Nginx and Traefik. |
| Purpose | NonGNU ELPA is an Emacs Lisp package archive for extending GNU Emacs. | pypiserver is a minimal PyPI-compatible server for uploading and downloading Python packages with pip or easy_install. |
Plans
In their own words
NonGNU ELPA
NonGNU ELPA has no write-up on Specifiction yet; its figures are above.
pypiserver
pypiserver is a minimal, self-hosted package index for uploading and downloading Python packages with tools such as pip and easy_install. It serves packages from regular directories, including wheels, bdists, eggs and PGP signatures, and scans those directories recursively. Packages can be uploaded with pip, setuptools, twine or pypi-uploader, or copied to the server with scp. Upload access can be protected with an Apache htpasswd file; API users can configure custom authentication callables. The maintainers advise password protection for uploads, and the documentation recommends a reverse proxy to provide HTTPS. pypiserver can run as a WSGI application, with documented integrations for Docker, nginx, Apache, gunicorn and Paste. It provides a health endpoint that returns HTTP 200 when the service is running, with an option to configure the endpoint. The current version supports Python 3.10+ and PyPy3. It is free at free and is listed for Linux, macOS, Windows, API and self-hosted use. Its API covers the operations needed by common package tools rather than the full PyPI API; documentation uploads are accepted but not saved to disk.