On Sun, Jul 24, 2005 at 10:10:49PM +0100, Crispin Flowerday wrote: >On Sun, 2005-07-24 at 16:55 +0100, Magnus Therning wrote: >> I have a rather strange problem. Using pyphany to try to create an >> Epiphany extension I have problems getting Epiphany to run the code >> that's actually in the files in the filesystem. >> >> For development purposes I use links from >> /usr/lib/epiphany-1.6/extensions (root is required to write there) to my >> home dir. > >BTW, you can put your .py and .xml files in >~/.gnome2/epiphany/extensions/ This saves altering the system /usr/lib >directories. I also believe instead of the .py file, you can create a >dir of the name of your extension, and it will load the __init__.py file >inside. This would save you from having to alter the /usr/lib system >dirs. Cool. Very good advise indeed. Any advise on debugging Python extensions? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus therning org http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Black holes are where God divided by zero. -- Steven Wright
Attachment:
pgpTr5TKjC7Hv.pgp
Description: PGP signature