devpi-server: reliable private and pypi.org caching server
devpi-server: server for private package indexes and PyPI caching
You can point pip or easy_install to the root/pypi/+simple/ index, serving as a transparent cache for pypi-hosted packages.
User specific indexes
Each user (which can represent a person, project or team) can have multiple indexes and upload packages and docs via standard twine or setup.py invocations. Users and indexes can be manipulated through devpi-client and a RESTful HTTP API.
Each index can be configured to merge in other indexes so that it serves both its uploads and all releases from other index(es). For example, an index using root/pypi as a parent is a good place to test out a release candidate before you push it to PyPI.
Good defaults and easy deployment
Get started easily and create a permanent devpi-server deployment including pre-configured templates for nginx and process managers.
Separate tool for Packaging/Testing activities
The complementary devpi-client tool helps to manage users, indexes, logins and typical setup.py-based upload and installation workflows.
See https://doc.devpi.net on how to get started and further documentation.
- Fix traceback when trying to delete already deleted release or toxresult.
- Preserve index config settings of plugins during import instead of aborting, even if the plugin isn’t installed during import.
- Added --no-checksum option to devpi-fsck to skip checksum validation and only check for file existence.
- Split keyfs cache into a small changelog cache and a relpath cache, this lowers overall memory usage and prevents cache trashing.
- Lower memory usage by avoiding to read release files into memory and instead use existing file objects.
- Switch to platformdirs from appdirs.
- Add streaming replica protocol, which is faster and uses less memory, especially when rebuilding a replica.
- Better logging and handling if a thread unexpectedly dies.
- Fix #871: authentication info in mirror_url wasn’t passed on to release links anymore.
- Open database connection after file was downloaded during replication to avoid conflicts and locking.
- Avoid hashing data twice when writing to storage.
- Close HTTP responses and sessions when done to free resources as early as possible instead of waiting for garbage collection.
Deprecations and Removals
- As announced with 6.0.0, support for Python 3.6 has been dropped, because it has reached its end of life.
- When an installer user agent is detected the full list of projects is returned unsorted and with less info to improve performance and reduce memory usage.
- Use __slots__ for some classes to reduce memory usage.
- Fix exceptions related to logging for some edge cases.
- Fix #864: enable settings from ~/.netrc and HTTP_PROXY/HTTPS_PROXY env vars for aiohttp.
- Use aiohttp (asyncio) for fetching release links from mirrors to return stale links immediately in case of a timeout, but update the database in the background for the next request.
- fix #853: prevent duplicate mirror indexes in sro method when there are multiple inheritance chains to the same mirror
- fix #860: don’t check for existing files and validate them during mirror links update, the operation is way to expensive and there is a low possibility for errors.
- Add missing lazy package dependency. Previously this was only a transitive dependency coming from the devpi-common package.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for devpi_server-6.5.1-py3-none-any.whl