current problems in UbuntuExpress

Juan Jesús Ojeda Croissier juanje at interactors.coop
Tue Aug 16 20:42:17 CDT 2005


El mar, 16-08-2005 a las 05:28 -0400, kamstrup escribió:
> Importing modules
> 
> ----------------------------
> 
> I once got flamed (in a polite way :D) on #python that
> __import__(mymodule) should never be used... The same effect can be
> obtained with the pydoc.importfile("mymodulepath") in a safe way - I'm
> no expert though...

Ummm.... interesting. Thanks
But putting the full module's path seems ugly to me. Anyway, the current
method is not very nice either.

> On front-back communications
> 
> -----------------------------------------------
> 
> Have you checked out the DBUS Python tutorials?
> http://dbus.freedesktop.org/doc/dbus-tutorial.html#python-client

Yeah, but just a brief glance.

> 
> The Python bindings for DBUS are quite easy to use... I don't think I
> understand the exact problem in the front-back communication though. Is
> it that you need a generic (ie. non-gtk-specific) way to do inter
> process communication between the *-ends?

Yes I need that.

> A simpler way might be to let the backend do non-blocking writes to a
> named pipe and let the front-end read from that pipe end update the
> progress bar at each read.

May you put a example of that? I searched info about pipes and so on in
python, but it didn't see well how to do what you say.

> I am wondering why exactly you choose processes over threads? Normally
> it seems to me that threads are easier to work with.

People told me threads messing to much with the gtk interfaces and is
better to avoid when it's possible.


Man, thanks a lot for your words. They help really me.
Cheers

-- 
   \|/  interactors              | juanje arroba interactors.coop
  \|/    |_ activando redes      | http://interactors.coop
 \|/     |_ activating networks  | http://metadistros.hispalinux.es
 / 



More information about the ubuntu-devel mailing list