[pygtk] Expected Behaviour of gnomevfs.XFER_NEW_UNIQUE_DIRECTORY

Alexander Larsson alexl at redhat.com
Tue Apr 24 17:11:35 WST 2007


On Mon, 2007-04-23 at 17:51 +0200, Gian Mario Tagliaretti wrote:
> 2007/4/23, John Stowers <john.stowers.lists at gmail.com>:
> 
> Hi John,
> 
> > I am trying to copy files using gnomevfs using xfer_uri
> >
> > I am unable to perform a copy from
> >
> > foo/file1 to
> > foo/bar/file1
> >
> > without first creating the bar directory. I thought that
> > gnomevfs.XFER_NEW_UNIQUE_DIRECTORY created all needed directories for
> > the copy - this does not seem to be the case however.
> >
> > Is this a bug or a lack of my understanding? (see example code below)
> 
> since I don't think it's a problem of the python bindings I've cc'd
> gnome-vfs-list, maybe you can get more help.

Seems like a bug in the docs. GNOME_VFS_XFER_NEW_UNIQUE_DIRECTORY is a
toplevel operation that causes gnome_vfs_xfer to create a new uniquely
named directory. It doesn't do any copying after that.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl at redhat.com    alla at lysator.liu.se 
He's a benighted pirate rock star who hangs with the wrong crowd. She's a 
brilliant hip-hop stripper from the wrong side of the tracks. They fight 
crime! 



More information about the pygtk mailing list