From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Down with PYTHONPATH! Date: Mon, 17 Jun 2019 12:20:12 +0200 Message-ID: References: <87muikr3bq.fsf@mdc-berlin.de> <87ef3s37nq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38363) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcoka-0006n8-6Q for guix-devel@gnu.org; Mon, 17 Jun 2019 06:20:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hcokX-0005Bc-Ng for guix-devel@gnu.org; Mon, 17 Jun 2019 06:20:31 -0400 In-Reply-To: <87ef3s37nq.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, Ricardo Wurmus Hi Ludo, > How does virtualenv work, if not by setting PYTHONPATH? It creates a new filetree corresponding to a complete new Python installation, and the uses soft links to share most of the actual files with the parent installation. > Setting up an environment all about augmenting the search path, so I > naively thought that virtualenv sets PYTHONPATH or the corresponding > Python variable. PYTHONPATH only adds directories to the search path. The standard library and packages installed via pip are already on the search path before PYTHONPATH is looked at. So virtualenv could not work by modifying PYTHONPATH. Konrad.