Bug 519615

Summary: Review Request: python-virtualenv - Virtual Python Environment builder
Product: [Fedora] Fedora Reporter: Peter Halliday <phalliday>
Component: Package ReviewAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: fedora-package-review, notting, phalliday
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 460182 Environment:
Last Closed: 2009-08-28 12:42:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Halliday 2009-08-27 02:33:04 UTC
Spec URL: http://www.excelsiorsystems.net/media/files/python-virtualenv.spec
SRPM URL: http://www.excelsiorsystems.net/media/files/python-virtualenv-1.3.3-1.fc11.src.rpm
Description:     
    virtualenv is a tool to create isolated Python environments.

    The basic problem being addressed is one of dependencies and versions,
    and indirectly permissions.  Imagine you have an application that
    needs version 1 of LibFoo, but another application requires version
    2.  How can you use both these applications?  If you install
    everything into ``/usr/lib/python2.4/site-packages`` (or whatever your
    platform's standard location is), it's easy to end up in a situation
    where you unintentionally upgrade an application that shouldn't be
    upgraded.

Comment 1 Peter Halliday 2009-08-28 12:42:33 UTC
I just recognize taht this duplicates 460182.

*** This bug has been marked as a duplicate of bug 460182 ***