Getting the svnmerge-intergrated property right when merging
trunk->py3k->release30 is a little tricky. The most concise set of
instructions I have found which gets it right is to do the following in
the 3.0 maintenance branch after committing to the py3k branch:
svn update
svnmerge merge -r
svn
You know, all this path separator and list complication isn't really
necessary, when you can just take the os.path.dirname() of the return
from commonprefix().
Perhaps we could just add that recommendation to the docs?
At 04:46 PM 12/29/2008 -0600, s...@pobox.com wrote:
Jeff> For those
Jeff> For those that prefer not to add functions all willy-nilly, would
Jeff> it not be better to add a "delimiter" keyword that defaults to
Jeff> False? Then "delimiter=False" will function with the current
Jeff> functionality unchanged while
Jeff> os.path.commonprefix(["bob/
I was thinking that the user could just define the delimiter character due
to the differences amongst delimiters used in OS's... but if that isn't a
problem (Skip seemed to think it wouldn't be) then my solution is
functionally identical to the first one he proposed
Jeff Hall wrote:
... For those that prefer not to add functions all willy-nilly, would it not
be better to add a "delimiter" keyword that defaults to False? Then
"delimiter=False" will function with the current functionality unchanged
while
os.path.commonprefix(["bob/export/home", "bob/etc/pa
I think Nick's solution is "Don't let the best be the enemy of the good"
Had this been caught before 3.0 release it might be a different solution
Let's just add a new function that works "correctly"
Martin, it seems to me that a path. method shouldn't require me to pass path
components but inste
