Mailman 3 July 2016 - devpi-dev

Configure devpi-server to work behind proxy server at workplace
by RedDevil91 July 27, 2016

July 27, 2016

Hi! We want to use devpi-server to share packages between colleagues on 64-bit Windows using miniconda environment. The problem is we can't download packages from pypi and from our local index. The uploading works fine and the uploaded packages are visible on devpi-web. The pip.ini contains the http://localhost:3141/root/pypi/+simple/ index-url and trusted-host localhost (localhost=server hostname) configuration but I get the following error: [test] C:\Users\{username}>pip install simplejson Collecting simplejson Could not find a version that satisfies the requirement simplejson (from versi ons: ) No matching distribution found for simplejson Is it because of the company's proxy server or the conda environment? Best regards, RedDevil91

3 9

How do you enable access to devpi at your company?
by Ryan Rueth July 24, 2016

July 24, 2016

We're starting to deploy devpi at our company. We want to have a production instance of devpi that lives in our colo/the cloud, and then have developers run devpi locally and have a mirror of the production instance. Since, devpi will host our internally developed packages, we want some level of authentication/authorization in order to install packages from devpi (i.e. and not have devpi be completely public). Thus, I'm curious, how do most companies deploy devpi with authentication/authorization such that local developers can easily access the colo/cloud hosted instance of devpi when installing with pip? Do you use a VPN? Do you put devpi behind nginx? Do you use devpi-ldap? Something else completely? Thank you in advance for your response! Thank you, Ryan

1 0

devpi-server, -client and -web releases
by Florian Schulze July 16, 2016

July 16, 2016

We released devpi-server 4.1.0, devpi-client 2.6.4 and devpi-web 3.1.1. devpi-client 2.6.4 fixes upload of packages which print additional output during the build process, like numpy which compiles C extensions. devpi-web 3.1.1 doesn't look at inherited mirrors anymore during indexing of private indexes, which makes it slightly faster, especially after an import. devpi-server 4.1.0 has several fixes and one improvement: In complex inheritance situations, mirrors are now looked at last, so all private packages are found first and not cut short by a mirror when they aren't whitelisted. Private indexes which inherit from a mirror now show local releases when the mirror is down. The new feature is using Sqlite read only mode when possible: Sqlite can be used with a single writer and multiple readers without blocking. Unfortunately that behaviour isn't available in all setups. With Python 3.4 it is possible to explicitly request that behaviour when opening the database. So it is recommended that you run devpi-server using Python 3.4. Some setups compile sqlite in a way which allows to implicitly use the non blocking behaviour. It seems like OS X and FreeBSD have that by default. Most Linux setups lack that setting. You can check the devpi-server log to see if there are sqlite related warnings shortly after startup. If there are none, then the non blocking behaviour is used. Regards, Florian and Holger P.S.: we offer support contracts btw and thank in particular Dolby Laboratories, YouGov Inc and BlueYonder GmbH who funded a lot of the last year's devpi work and now agreed to be named in public - and no, we didn't get around to make a flashy web site yet. For now, just mail holger at merlinux to discuss support and training options.

1 0