Hello community, here is the log from the commit of package python-virtualenv for openSUSE:Factory checked in at Thu Apr 14 13:07:24 CEST 2011.
-------- New Changes file: --- /dev/null 2010-08-26 16:28:41.000000000 +0200 +++ /mounts/work_src_done/STABLE/python-virtualenv/python-virtualenv.changes 2011-04-13 20:37:20.000000000 +0200 @@ -0,0 +1,104 @@ +------------------------------------------------------------------- +Wed Apr 13 18:25:47 UTC 2011 - [email protected] + +- Update to 1.6: + * Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy. + * Fixed creation of virtualenvs on Mac OS X when standard library modules + (readline) are installed outside the standard library. + * Updated bundled pip to 1.0. +- Regenerate spec file with py2pack. + +------------------------------------------------------------------- +Sun Sep 19 23:39:18 UTC 2010 - [email protected] + +- Update to 1.5.1: + - Added ``_weakrefset`` requirement for Python 2.7.1. + - Fixed Windows regression in 1.5. + +------------------------------------------------------------------- +Wed Sep 15 02:36:21 UTC 2010 - [email protected] + +- Update to 1.5: + - Include pip 0.8.1. + - Add support for PyPy. + - Uses a proper temporary dir when installing environment requirements. + - Add --prompt option to be able to override the default prompt prefix. + - Fix an issue with --relocatable on Windows. + - Fix issue with installing the wrong version of distribute. + - Add fish and csh activate scripts. + +------------------------------------------------------------------- +Fri May 28 01:50:35 UTC 2010 - [email protected] + +- Update to 1.4.9: + * Include pip 0.7.2. + +------------------------------------------------------------------- +Fri Apr 23 13:01:48 UTC 2010 - [email protected] + +- Update to 1.4.8: + * Fix for Mac OS X Framework builds that use + ``--universal-archs=intel`` + * Fix ``activate_this.py`` on Windows. + * Allow ``$PYTHONHOME`` to be set, so long as you use ``source + bin/activate`` it will get unset; if you leave it set and do not + activate the environment it will still break the environment. + * Include pip 0.7.1. + +------------------------------------------------------------------- +Mon Apr 19 02:00:28 UTC 2010 - [email protected] + +- Update to 1.4.7: + * Include pip 0.7. + +------------------------------------------------------------------- +Wed Mar 31 22:56:52 UTC 2010 - [email protected] + +- Update to 1.4.6 + * Allow ``activate.sh`` to skip updating the prompt (by setting + ``$VIRTUAL_ENV_DISABLE_PROMPT``). +- Spec file cleaned with spec-cleaner. + +------------------------------------------------------------------- +Mon Mar 15 01:24:36 UTC 2010 - [email protected] + +- Added python-setuptools as Requires; +- Generated changes file from spec file; +- Removed old tarballs; +- Update to 1.4.5 + - Include pip 0.6.3 +- Aditional changes from 1.4.4: + - Include pip 0.6.2 and Distribute 0.6.10 + - Create the virtualenv script even when Setuptools isn’t installed + - Fix problem with virtualenv --relocate when bin/ has subdirectories + (e.g., bin/.svn/); from Alan Franzoni. + - If you set $VIRTUALENV_USE_DISTRIBUTE then virtualenv will use + Distribute by default (so you don’t have to remember to use --distribute). + +------------------------------------------------------------------- +Sat Nov 21 00:00:00 UTC 2009 - [email protected] + +- 1.4.3 + * Include pip 0.6.1 + +------------------------------------------------------------------- +Mon Nov 9 00:00:00 UTC 2009 - [email protected] + +- Update to 1.4 + * Updated setuptools to 0.6c11 + * Added the --distribute option + * Fixed packaging problem of support-files + + +------------------------------------------------------------------- +Thu Mar 3 00:00:00 UTC 2009 - [email protected] + +- Update to 1.3.2 + - Remove the [install] prefix = ... setting from virtualenv distutils.cfg as has been causing problems for a lot of people, in rather obscure ways. + - If you use a boot script it will attempt to import virtualenv and find a pre-downloaded Setuptools egg using that. + - Added platform-specific paths, like /usr/lib/pythonX.Y/plat-linux2 + +------------------------------------------------------------------- +Wed Nov 5 00:00:00 UTC 2008 - [email protected] + +- Initial import and build - 1.3 calling whatdependson for head-i586 New: ---- python-virtualenv.changes python-virtualenv.spec virtualenv-1.6.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-virtualenv.spec ++++++ # # spec file for package python-virtualenv # # Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # %{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")} %{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib(1)")} %define mod_name virtualenv Name: python-%{mod_name} Version: 1.6 Release: 1 Url: http://www.virtualenv.org Summary: Virtual Python Environment builder License: MIT Group: Development/Languages/Python Source: %{mod_name}-%{version}.tar.bz2 BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: python-devel %if 0%{?suse_version} %py_requires %if 0%{?suse_version} > 1110 BuildArch: noarch %endif %endif %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 platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt be upgraded. Or more generally, what if you want to install an application and leave it be? If an application works, any change in its libraries or the versions of those libraries can break the application. Also, what if you cant install packages into the global site-packages directory? For instance, on a shared host. In all these cases, virtualenv can help you. It creates an environment that has its own installation directories, that doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either). %prep %setup -q -n %{mod_name}-%{version} %build export CFLAGS="%{optflags}" python setup.py build %install python setup.py install --prefix=%{_prefix} --root=%{buildroot} %clean rm -rf %{buildroot} %files %defattr(-,root,root,-) %doc PKG-INFO docs %python_sitelib/%{mod_name}* %{_bindir}/%{mod_name} %changelog ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Remember to have fun... -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
