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
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com