New improvements, and easier pip install Re: pip + virtualenv: excellent for codenode usage - and python projects in general

Skip to first unread message

Alex Clemesha

Aug 4, 2009, 4:23:52 AM8/4/09

I wanted to update this thread on installing via pip and virtualenv,
aimed mainly at those who want to try the latest improvements very easily.
I'll also mention a couple new improvements, with some screenshots.

Installing the latest codenode
1) get pip and virtualenv:
$ easy_install pip virtualenv

2) make a clean virtualenv for the latest codenode:
$ virtualenv --no-site-packages codenode_env

3) Install codenode from the core git repository:
$ pip -E codenode_env install -e

Now you can try the latest codenode as usual, and when you are done trying it,
you can just type "rm -rf codenode_env" and *every trace* of what you installed
will be gone. No lingering hidden files, no dependency mismatches
later, etc. It's good stuff.

Some recent improvements
In the latest codenode there is nice new "Revision History" functionality,
which I have attached 2 screenshots of, one showing the notebook, and the other
is the "Revision History / Revert" page for that notebook.

Also, in the latest codenode, you can find the clean new human-readable notebook
url functionality by James, which gives the *option* to use the nice
urls if desired, but
remains transparent to a regular user who may have several notebooks
with the same
title, etc.

Finally, a new release will be happening soon such that you can just type
"easy_install codenode" and get the latest from PyPI. This will happen in
about a week. For now, go try the pip+virtualenv install!


On Tue, Jun 30, 2009 at 10:57 PM, Alex Clemesha<> wrote:
> Hi,
> This is just a quick note on a new and _much_ better way I have been
> managing the complexity of developing lots of python projects.
> "virtualenv" is a tool that creates isolated python environments,
> and "pip" is an new and improved "easy_install" tool that plays
> very well with virtualenv.
> I'd say the biggest benefit of virtualenv is that is frees you
> from having to install packages globally - although there are
> several other benefits (ask google).
> Example usage
> ============
> the quickest way to get started using "pip", is actually like this:
> $ easy_install pip
> (although it can be used as a standalone file "")
> now try using pip to get "virtualenv":
> $ pip install virtualenv
> now make a new virtualenv:
> $ virtualenv myenv
> or
> $ virtualenv --no-site-packages myenv #clean environment
> and now do a:
> $ source myenv/bin/activate
> to activate this virtualenv
> The awesome part - codenode install
> =============================
> Tying codenode together with pip and virtualenv usage:
> Type the following lines in your shell (you must have git)
> ---------------------------------------------------------------------------
> $ virtualenv --no-site-packages mycodenode_env
> $ pip -E mycodenode_env install -U twisted django
> $ pip -E mycodenode_env install -e
> git://
> --
> The awesome parts (in case you missed them :-)
> ---------------------------------------------------------------------
> Line #1: You can easily create fresh virtualenvs in seconds
> Line #2: You can install the latest packages in your virtualenvs (and
> not worry about global dependencies collisions).
> Line #3 You can install packages straight from source code repositories
> Now you can run codenode as usual:
> -------------------------------------------------
> cd mycodenode_env/
> codenode-admin init -name mycodenode
> cd mycodenode
> codenode-admin run
> Happy hacking,
> -Alex

Alex Clemesha

Reply all
Reply to author
0 new messages