On Fri, 2006-01-06 at 01:33 +0100, "Martin v. Löwis" wrote: > As you can see, this is done now. The value appears at the Python > level only for tags, though, because it will be unreliable for the > trunk and for branches. Cool, thanks. I can chuck my local diffs now. :) > > patchlevel.h seems like the natural place to put this, since any release > > manager is going to be modifying this file anyway. PEP 101 should be > > updated so that updating patchlevel.h be the last commit before an svn > > export is done (but that PEP needs an overhaul anyway to change the cvs > > references into svn commands). > > It would still be one level behind: patchlevel.h gets N, then 'svn cp' > creates the tag, producing N+1. OTOH, for a tag, the revision number > is nearly irrelevant. Unless we tagged and then modified the file in that tag as the very last thing we do before we create the tarball. Or is that too evil? -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/python-dev/attachments/20060105/cf8ba7be/attachment.pgp
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4