Visualize the Revision Number in the Trac UI

[ilias@…]

it would be nice to have the revision number visualized, e.g.:

0.11dev.r4078 (instead of the simple 0.11dev)

This would allow users of development version to report the revision number without having much effort.

[Noah Kantrowitz (coderanger) <coderanger@…>]

Subversion offers no direct way to do this. On the plus side setuptools does, so once that migration is complete the revision number will be visible in the egg name.

[markus]

This could be done by using svn:keywords

[cboos]

No, it can't: you'd get the last revision for the file which contains the keyword, usually not a very interesting information...

As Noah said, the setuptools branch addresses that.

[markus]

Replying to cboos:

No, it can't

Mea culpa.

[ilias@…]

Replying to Noah Kantrowitz (coderanger) <coderanger@yahoo.com>:

Subversion offers no direct way to do this. On the plus side setuptools does, so once that migration is complete the revision number will be visible in the egg name.

I understand.

For development versions (fetched/updated from svn), the setuptools functionality would not help.

Possible solution a post-commit function, which retrieves the HEAD rev number and places it within a file, where it can be retrieved programmatically.

[cmlenz]

Replying to ilias@lazaridis.com:

For development versions (fetched/updated from svn), the setuptools functionality would not help.

It does. It shows you the version number and the revision.

[ilias@…]

Replying to cmlenz:

Replying to ilias@lazaridis.com:

For development versions (fetched/updated from svn), the setuptools functionality would not help.

It does. It shows you the version number and the revision.

ok.

I assume that this would need an "python setup.py develop" after the svn update, but this would still be sufficient.

[mgood]

Replying to ilias@lazaridis.com:

Replying to cmlenz:

Replying to ilias@lazaridis.com:

For development versions (fetched/updated from svn), the setuptools functionality would not help.

It does. It shows you the version number and the revision.

I assume that this would need an "python setup.py develop" after the svn update, but this would still be sufficient.

"python setup.py egg_info" is all that's needed to update the package's metadata where the version is stored.

[ilias@…]

fixed with setuptools-merge, see [4819]