converting virtualenvwrapper repo to git

If you have forked virtualenvwrapper, you’ll want to update your fork to use the new git repository at https://bitbucket.org/dhellmann/virtualenvwrapper, still hosted by our friends at bitbucket.org. The issue tracker contents have been migrated along with the source code. The old Mercurial repository is still available at https://bitbucket.org/dhellmann/virtualenvwrapper-hg until I’m entirely certain that the new repository is working correctly.

cliff — Command Line Interface Formulation Framework — version 1.3.3

cliff is a framework for building command line programs. It uses setuptools entry points to provide subcommands, output formatters, and other extensions.

What’s New In This Release?

  • Restore compatibility with prettytable < 0.7.2 by forcing no output if there is no data (instead of printing an empty table). Contributed by Dirk Mueller.
  • Update to allow cmd2 version 0.6.5.1. Contributed by Dirk Mueller.

Documentation

Documentation for cliff is hosted on readthedocs.org

Installation

Use pip:

$ pip install cliff

See the installation guide for more details.

Why virtualenvwrapper Is Not Written in Python

If you look at the source code for virtualenvwrapper you will see that most of the interesting parts are implemented as shell functions in virtualenvwrapper.sh. The hook loader is a Python app, but doesn’t do much to manage the virtualenvs. Some of the most frequently asked questions about virtualenvwrapper are “Why didn’t you write this as a set of Python programs?” or “Have you thought about rewriting it in Python?” For a long time these questions baffled me, because it was always obvious to me that it had to be implemented as it is. But they come up frequently enough that I feel the need to explain.

Read more

virtualenvwrapper 4.0

What is virtualenvwrapper?

virtualenvwrapper is a set of extensions to virtualenv. The extensions include wrappers for creating and deleting virtual environments and otherwise managing your development workflow, making it easier to work on more than one project at a time without introducing conflicts in their dependencies.

What’s New?

Warning: This release includes some potentially incompatible changes for extensions. The python modules for extensions are now always run with PWD=$WORKON_HOME (previously the value of PWD varied depending on the hook). The shell portion of any hook (anything sourced by the user’s shell when the hook is run) is still run in the same place as before.

  • All tests pass under Python 2.6, 2.7, 3.2 and 3.3.
  • Fix the name of the script in an error message produced by virtualenvwrapper_lazy.sh. (Contributed by scottstvnsn.)

Installing

Visit the virtualenvwrapper project page for download links and installation instructions.

virtualenvwrapper 3.7.1

What is virtualenvwrapper?

virtualenvwrapper is a set of extensions to virtualenv. The extensions include wrappers for creating and deleting virtual environments and otherwise managing your development workflow, making it easier to work on more than one project at a time without introducing conflicts in their dependencies.

What’s New?

  • Rename functions for generating help so they do not pollute the global namespace, and especially so they do not interfere with tab completion. Contributed by davidszotten.
  • Fix an issue with listing project templates if none are installed.
  • Fix an issue with the --python option to mkvirtualenv becoming sticky for future calls that do not explicitly specify the option.

Installing

Visit the virtualenvwrapper project page for download links and installation instructions.