[Distutils] copy_file semantics changed?

[Greg Ward]

On 22 June 2000, I spoke too soon:
> That assumes that I changed the interface to return boolean arbitrarily.
> I did not: I believe there is code that depends on it returning
> boolean.  And now there is also code that depends on it returning the
> output filename.  Damn!  Time to grep the source for copy_file and see
> how it's *really* used...

Well, from poking through the CVS logs, it appears that 'copy_file()'
has *always* returned boolean.  And from scanning the source, it appears
that no code actually expects it to return boolean -- the only bits that
pays attention to the return value are my recent additions that use
'copy_file()'s supposed string return value to build list of files
copied.

So, Bastian's patch is exactly the right thing.  (Except you forgot to
fix the docstring!  Don't worry, I did it.)  Applied, checked in, and
now maybe things will work again.

        Greg
-- 
Greg Ward - geek-at-large                               gward@python.net
http://starship.python.net/~gward/
The NSA.  We care: we listen to our customers.