On Aug 6, 2007, at 1:39 AM, cropr wrote:

When I do "setuptools Pylons" on a freshly installed box, the version
0.9.6rc2 is being installed.  I was a little surprised not to get the
0.9.5 release by default.
The installation breaks as PasterScript requires an svn version.
 - Although I can install subversion on the machine to solve it, I
don't like it because the machine is set up as a deployment system
rather than a development box.
 - I did not request a dev version of Pylons, so I should not get a
dev version of the package or of some dependent packages.  Otherwise
what is the purpose of having dev versions and stable versions of
packages.
Will this be solved  with 0.9.6?  I am reluctant to put a dev version
on a deployment box.

This should install the PasteScript from the egg we posted, and not require svn. To manually install: easy_install -U http://pylonshq.com/download/0.9.6rc2/ PasteScript-1.3.6dev-r6751.tar.gz

Alternatively, try running setuptools again, it appears a link didn't update when rc2 was pushed out, which is now fixed. This should alleviate the need to install subversion.

Regarding being able to ask for a dev version, Pylons 0.9.6RC2 is just about ready for final release at this point. I wouldn't consider it a 'development' version. However, setuptools does have a fault where it always goes to the latest version number, regardess of if its a RC, a beta, or even an alpha (we've been fighting with nose installs on this because it tries to grab an alpha which doesn't work right). The setuptools dev's know about this issue and I believe are planning a fix to allow one to indicate they always want releases, and not alpha/beta/dev versions.

The pylonshq.com/download/ page is intended as a way of ensuring that deployment installs get the proper version of the packages, and avoid beta/alphas that are un-tested. The latest Pylons also contains additional setup commands to search there first which should also help this issue.

HTH,
Ben

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to