<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 8 Feb, 2007, at 10:20, Tal Einat wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV><SPAN class="gmail_quote">On 2/8/07, <B class="gmail_sendername">Michael Haubenwallner</B> <<A href="mailto:michael@d2m.at">michael@d2m.at</A>> wrote:</SPAN></DIV> <BLOCKQUOTE class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><BR>On an aside: searching Google for idle extensions is not an easy thing.<BR><BR>Do you know of a listing of available extensions or even a repository to <BR>download from ?</BLOCKQUOTE> <DIV> </DIV> <DIV>AFAIK there is none.</DIV> <DIV><BR> </DIV> <BLOCKQUOTE class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If not, should there be one ?<BR>- <A href="http://wiki.python.org">wiki.python.org</A> could have a page with a list of links <BR>- <A href="http://code.google.com/hosting">code.google.com/hosting</A> could host such a repo</BLOCKQUOTE> <DIV> </DIV> <DIV>I believe there should be one, once the selection is sizeable (as it is starting to become) and installation ease is improved...</DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV>The cheeseshop is another option and is used by a number of the web frameworks. If you ask nicely the cheeseshop maintainer could even add a classifier/category for IDLE extensions.</DIV><DIV><BR><BLOCKQUOTE type="cite"> <DIV><BR> </DIV> <BLOCKQUOTE class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">How could we ease the process of installing an idle extension ?<BR>I see no problem to just make the extension a package and put it in the <BR>python path (site-packages).<BR>Then we would need to change idlelib.configHandler.IdleConf to accept<BR>the package path besides the idleDir and userDir config options.<BR>This lets us eggify an extension and use ez_install for download and <BR>installation.</BLOCKQUOTE> <DIV> </DIV> <DIV>This is a very good idea! A few points which need to be resolved first:</DIV> <OL> <LI>Even if we could get idleConf to work like this, we would still need a way for IDLE to know about extensions. Currently extensions are "registered" by them adding an entry in config-extensions. How would we do this otherwise?<BR></LI></OL></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV>Setuptools entry-points are one option for this. Another option is installing all plugins in a special magic pacage and load all modules in that package.<BR><BLOCKQUOTE type="cite"><OL><LI> </LI> <LI>Currently user config is in a single config-extensions file. How would we manage user configuration with each extension being a separate module?</LI></OL><P>Regarding #2, I think we could still have user config in a single config-extensions file, where config for all extensions is stored</P></BLOCKQUOTE><BLOCKQUOTE type="cite"><P></P><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">IDLE-dev mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:IDLE-dev@python.org">IDLE-dev@python.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://mail.python.org/mailman/listinfo/idle-dev">http://mail.python.org/mailman/listinfo/idle-dev</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>