Ticket #4126 (closed enhancement: fixed)
Opened 6 years ago
Last modified 5 years ago
Visualize the Revision Number in the Trac UI
| Reported by: | ilias@… | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | devel |
| Severity: | normal | Keywords: | setuptools |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 follow-up: ↓ 5 Changed 6 years ago by Noah Kantrowitz (coderanger) <coderanger@…>
comment:2 Changed 6 years ago by markus
This could be done by using svn:keywords
comment:3 follow-up: ↓ 4 Changed 6 years ago by cboos
- Milestone set to 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.
comment:4 in reply to: ↑ 3 Changed 6 years ago by markus
comment:5 in reply to: ↑ 1 ; follow-up: ↓ 6 Changed 6 years ago by 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.
comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 6 years ago by cmlenz
- Owner changed from jonas to cmlenz
- Status changed from new to 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.
comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 6 years ago by 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.
comment:8 in reply to: ↑ 7 Changed 6 years ago by 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.
comment:9 Changed 6 years ago by ilias@…
- Keywords setuptools added
comment:10 Changed 5 years ago by ilias@…
- Resolution set to fixed
- Status changed from assigned to 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.