From owner-freebsd-python@FreeBSD.ORG Sat May 31 23:16:41 2014 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E99EBF0B; Sat, 31 May 2014 23:16:41 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D595D26D7; Sat, 31 May 2014 23:16:41 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 27F841A3D1F; Sat, 31 May 2014 16:16:39 -0700 (PDT) Message-ID: <538A62DA.2020608@freebsd.org> Date: Sat, 31 May 2014 16:16:42 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: python@freebsd.org, Marcus von Appen Subject: Re: Question on virtualenv (python) and FreeBSD References: <538A2A5F.2000601@freebsd.org> <20140531195031.GA854@medusa.sysfault.org> <538A41D5.8020203@freebsd.org> <20140531225107.GA56181@medusa.sysfault.org> In-Reply-To: <20140531225107.GA56181@medusa.sysfault.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2014 23:16:42 -0000 On 5/31/14 3:51 PM, Marcus von Appen wrote: > On, Sat May 31, 2014, Alfred Perlstein wrote: > > >> 3) other? >> >> thank you Marcus. > I won't block the process in either direction here, since I am generally > pretty indifferent about pulling in sqlite3 as dependency for lang/python. It > is wide-spread enough that it would end up on a majority of web application > systems anyway (although most large-scale web apps probably will use a > scalable database back-end, such as mysql, pg or oracle). > > Which brings me to the target group for your request: it'd be (mostly) > developers, not? Which would bring me to the toolchain script and FAQ and > responsibility over the dev machines again :-). > > [1] https://docs.djangoproject.com/en/dev/intro/install/ Sure, that's how to install it onto the host when using a single version of django AND it requires root for that. Virtualenv (once installed) lets people install almost all packages as non-root and leaves the worry off of the sysadmin. If you google "django virtualenv" you'll get this list of links: http://www.jeffknupp.com/blog/2012/02/09/starting-a-django-project-the-right-way/ http://thecodeship.com/deployment/deploy-django-apache-virtualenv-and-mod_wsgi/ https://docs.djangoproject.com/en/1.6/topics/install/ : "(optional) Take a look at virtualenv and virtualenvwrapper. These tools provide isolated Python environments, which are more practical than installing packages systemwide. They also allow installing packages without administrator privileges. It’s up to you to decide if you want to learn and use them." http://www.tonido.com/blog/index.php/2013/11/25/working-with-virtualenv-on-django-projects/#.U4phVZRdX2g https://community.webfaction.com/questions/4253/simple-virtualenv-usage-with-django I really believe the only blocker is sqlite right now. What I really want is people to be able to use virtualenv without having to switch OS, because the method I recommend is way complex. Both python and ruby teams are heavily recommending these "virtual environments" we should support it out of the box, particularly since the change seems very light. -Alfred