When you clone the repository, it will give you the 'default' branch to
start working with. By convention, this is the branch where new development
happens, and other branches are split off to make more stable releases. At
present, rpy2's primary focus of development is the 'version_2.2.x' branch,
so you have to check that out after cloning it. I stumbled on this as well.

Laurent, perhaps it would be simpler to rename the current version_2.2.x
branch to default, and then create a new 2.2.x branch when it's ready for a
stable release.

Thomas

On 27 January 2011 14:47, <rpy-list-requ...@lists.sourceforge.net> wrote:

> i just needed to remove the '2.1.0dev' which installed by default when i
> ran setup.py after cloning the repository and do the following:
>
> hg update -C <latest version>
>
> before running setup.py install.
>
> this may be obvious but just in case someone else gets confused...
>
> cheers,
> peter
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to