Issue 62 in contentmirror: contentmirror-rc2 not pinned to SA <0.6

[conten...@googlecode.com]

Status: Assigned
Owner: runyaga
CC: kapilt
Labels: Type-Defect Priority-Medium

New issue 62 by runyaga: contentmirror-rc2 not pinned to SA <0.6
http://code.google.com/p/contentmirror/issues/detail?id=62

SA 0.6 has not been tested nor is it currently supported in CM 0.6.
Although when I followed the instructions it pulled the cm0.6 egg from pypi.
Which then pulled SA 0.6.

http://code.google.com/p/contentmirror/source/browse/ore.contentmirror/trunk/setup.py

clearly states "SQLAlchemy>=0.5.5,<0.6"

Just pulled rc2 tarball; looks like it was incorrect.
"SQLAlchemy>=0.5.5",

So just a new release of contentmirror will fix that problem

[conten...@googlecode.com]

Comment #1 on issue 62 by runyaga: contentmirror-rc2 not pinned to SA <0.6
http://code.google.com/p/contentmirror/issues/detail?id=62

I think we should just pin it specific to 0.5.8

[conten...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 62 by kapilt: contentmirror-rc2 not pinned to SA <0.6
http://code.google.com/p/contentmirror/issues/detail?id=62

rc3 has the version pin for sqlalchemy.

[conten...@googlecode.com]

Updates:
Labels: Milestone-Release0.6

Comment #3 on issue 62 by kapilt: contentmirror-rc2 not pinned to SA <0.6
http://code.google.com/p/contentmirror/issues/detail?id=62

(No comment was entered for this change.)