get_svn_revision() should be more robust

[rjaarts]

When Django is used in the Google App Engine (GAE)environment there is a problem with the django get_svn_revision() function. This occurs only in when using the GAE SDK and when a checked out version of Django is used.
The get_svn_revision() function checks for existence of a ".svn/entries" file. This file will exist if Django was checked out, but GAE will prevent reading that file, which results in an raised error. Would be nice if this error could be catched, and perhaps a warning logged, and simple "unknown" would be returned.

[Alex Gaynor]

This isn't a feature and thus isn't for the 1.1 beta.

[Valera_Grishin]

There is another problem with get_svn_version. Tortoise SVN client (don't known if others do so too) allows for changing default name of directory .svn to _svn. Using this feature will cause get_svn_version to always fail, since .svn is hardcoded.

[Malcolm Tredinnick]

This is a utility function that works for a normal subversion checkout. So if Tortoise SVN renames things to something non-standard, they just don't see the revision number. Same as people who aren't using subversion as their primary system for checking out the code (I never see the version number, for example). We shouldn't raise errors, but if the version number doesn't display, that's the way it goes. No harm done. If you must see the version number, don't rename the .svn directory and always use subversion to check out the code.

[Jacob]

(In [10377]) Fixed #10372: made get_svn_revision() more robust. Thanks, mboersma.

[Jacob]

(In [10378]) [1.0.X] Fixed #10372: made get_svn_revision() more robust. Thanks, mboersma. Backport of r10377 from trunk.

[Jacob]

Milestone 1.1 deleted