Opened 18 years ago
Closed 18 years ago
#4126 closed enhancement (fixed)
Visualize the Revision Number in the Trac UI
| Reported by: | Owned by: | Christopher Lenz | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | devel |
| Severity: | normal | Keywords: | setuptools |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
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.
Attachments (0)
Change History (10)
follow-up: 5 comment:1 by , 18 years ago
follow-up: 4 comment:3 by , 18 years ago
| Milestone: | → 0.11 |
|---|
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.
follow-up: 6 comment:5 by , 18 years ago
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.
follow-up: 7 comment:6 by , 18 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
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.
follow-up: 8 comment:7 by , 18 years ago
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.
comment:8 by , 18 years ago
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.
comment:9 by , 18 years ago
| Keywords: | setuptools added |
|---|
comment:10 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
fixed with setuptools-merge, see [4819]
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.