A heads up for the changes in upcoming major releases of devpi-client
Deprecations and Removals
- removed deprecated "quickstart" command.
- decoupled the functional tests from devpi-server and run devpi-server
in a Python 3 virtualenv when testing with Python 2.7.
- The selection of the Python interpreter used for ``devpi upload`` has
changed. If used the new ``-p/--python`` option has priority, then a
currently activated virtualenv, lastly the ``sys.executable`` under
which devpi is running.
Deprecations and Removals
- fix #518: There are no URLs on PyPI anymore that need to be scraped or
crawled, so the code for that was removed.
- removed support for long deprecated ``acl_upload`` and ``bases``
mirror index option. They were only kept for compatibility with
devpi-client <= 2.4.1.
- removed long deprecated ``pypi_whitelist`` index option. It was only
kept for compatibility with devpi-client <= 2.4.1.
- deprecated Python 2.7 support. This is the last major version
supporting Python 2.7. For upgrading to Python 3.x you have to export
your data using your current setup with Python 2.7 and import it in a
new installation with Python 3.x.
- major releases don't require an export/import cycle anymore except
when explicitly announced. You should always make a backup though! When
upgrading to devpi-server 5.0.0 you can keep the state as is and even
downgrade to the last 4.9.x release if necessary. Don't forget to backup
- the --storage option is now required when a storage plugin like
devpi-postgresql is in use. It's recommended to use a configuration file
for devpi-server to have everything in one place.
I'm currently reading up on monitoring and specifically Prometheus.
I'm thinking of adding instrumentation to devpi and create a
devpi-prometheus plugin for exposition. The instrumentation is pretty
lightweight and shouldn't affect anyone who won't use it.
Has anyone here used Prometheus and can provide some insights on what
kind of metrics would be useful?
Maybe someone has pointers to other Python/Pyramid software which
already added that?
I just noticed and reported that tox 3.8.0 breaks json test results:
Just a heads up for anyone who relies on them for reporting in devpi-web.
I was curious if anyone was using the devpi-postgresql package in a
live/heavy use environment. It still carries the experimental warning, so
figured I'd ask here before diving too deep :-)
We were working with an internal cloud deployment suite and it seemed that
the sqlite with smb mounts was not very reliable....so we were considering
a switch to this postgres module if possible Or any other ideas for cloud
deployments where the database needs to be remote from the app?
Please see the following ticket about an issue I discovered with the
authentication secret of a devpi-server and it's replicas. So far this
didn't matter, but there are certain scenarios and plugin ideas where it
will be a problem.
Anyone deploying replicas and cares about security (hopefully everyone)
is welcome to help come up with a solution.
I released devpi-client 4.2.0, devpi-server 4.8.0 and devpi-web 3.5.0.
Includes a fix for big releases causing aborted connections, CPU spikes
and possibly other symptoms.
Adds Markdown support for project descriptions.
I made bugfix releases devpi-common 3.3.1 and devpi-web 3.4.1.
The former fixes documentation upload with devpi-client < 4.1.0, the
latter fixes a traceback on Python 2.7 when a package has no
Does anyone have a pointer on what causes this error?
AttributeError: 'FlakesItem' object has no attribute '_collectfile'
Happens for me with devpi-server on Travis and I can't reproduce it
I already reinstalled all my development dependencies with the latest
versions to see if a new package release causes it.