[pygtk] Missing GNOMEVFS URI APIs?

[Mystilleef]

Thank you! :-)

On 2/9/06, Gustavo J. A. M. Carneiro <gjc at inescporto.pt> wrote:
> On Wed, 2006-02-08 at 21:22 -0500, Mystilleef wrote:
> > Hello,
> >
> > My apologies if I'm posting to the wrong list. I couldn't
> > find the right one. I'm trying to move my application fully
> > to gnomevfs to give it the ability to remotely open and edit
> > files. However, I'm experiencing some discrepancies in the
> > GNOMEVFS Documentation and the python-gnomevfs API.
> >
> > I'll focus primarily on the URI Manipulation APIs. Here is a
> > list of very useful functions the GNOMEVFS reference
> > documents which I can't find in the APIs of Python binding
> > (>>>dir(gnomevfs) >>>dir(gnomevfs.URI)).
>
>   Try:
>
> >>> dir(gnomevfs.URI("foo"))
> ['__class__', '__cmp__', '__delattr__', '__doc__', '__getattribute__',
> '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__',
> '__repr__', '__setattr__', '__str__', 'append_file_name', 'append_path',
> 'append_string', 'copy', 'dirname', 'fragment_identifier', 'host_name',
> 'host_port', 'is_local', 'is_parent', 'parent', 'password', 'path',
> 'resolve_relative', 'scheme', 'short_name', 'short_path_name',
> 'toplevel']
>
>   Yes, it sucks, but most attributes are only visible in URI instances,
> not in the class itself.
>
>   Regards,
>
> --
> Gustavo J. A. M. Carneiro
> <gjc at inescporto.pt> <gustavo at users.sourceforge.net>
> The universe is always one step beyond logic.
>
>