[00:06:12] ** whit has joined us [02:20:33] ** cmlenz has joined us [02:46:34] ** cmlenz has left IRC () [03:11:48] ** cmlenz has joined us [05:18:40] [connected at Thu Aug 17 05:18:40 2006] [05:18:40] <> *** Looking up your hostname... [05:18:41] <> *** Checking ident [05:18:41] <> *** No identd (auth) response [05:18:41] <> *** Found your hostname [05:18:41] <> *** Your host is sterling.freenode.net[freebsd.widexs.nl/6667], running version hyperion-1.0.2 [05:18:41] [I have joined #peak] [05:22:40] ** cmlenz has left IRC (Read error: 104 (Connection reset by peer)) [06:03:55] ** cmlenz has joined us [08:39:35] ** coderanger_ has joined us [09:03:09] ** coderanger_ has left IRC (Read error: 104 (Connection reset by peer)) [09:06:38] ** coderanger_ has joined us [09:42:34] ** __doc__ has joined us [09:43:24] <__doc__> hi, is this the peak developer center channel? [09:45:47] <__doc__> I wonder how setuptools entry_point/plugin stuff works [09:54:14] __doc__: Something like that [09:54:27] __doc__: Its a fairly slow channel [09:55:03] What were you wondering about speicifcally? [10:02:19] <__doc__> hrm, well the setuptools documentation on the feature is quite sparse [10:02:49] Entry points are just a formalized bit of metadata [10:03:17] You can query eggs for what entry points they implement, and the contents of them [10:03:43] ** gldnspud has joined us [10:04:10] <__doc__> okay, so that's the piece of documentation missing on how to do that :D [10:04:24] Hmm, lemme find it [10:05:02] http://peak.telecommunity.com/DevCenter/PkgResources#distribution-methods [10:05:18] <__doc__> oh ic [10:05:20] Down towards the bottom of that section [10:06:39] <__doc__> http://peak.telecommunity.com/DevCenter/PkgResources#entry-points [10:07:01] Those are what are returned from the functions I mentioned [10:07:53] <__doc__> ok, so I maybe need a bit advice. [10:08:14] <__doc__> I've got multiple eggs representing my application, quite happy with that. [10:08:28] <__doc__> they're installed for a user [10:09:03] <__doc__> now what I think I require is a templates plugin, i.e. a collection of templates my application uses for rendering. [10:09:41] <__doc__> so I figure the entry_point mechanism of setuptools would be something that more or less fits that requirement [10:10:01] Well you would need to make some kind of plugin manager system [10:10:18] <__doc__> yes, of course beyond just locating the eggs. [10:10:25] That would load distributions from somewhere [10:10:51] And then load anything in myapp.templates or something [10:14:29] All that will do it import any modules you place in the "myapp.templates" entry point though [10:14:34] From there its up to you how to handle it [10:17:43] <__doc__> ok I think I roughly get it, thx [11:04:19] 7 people in #peak, thats gotta be some kind of record [11:04:26] (though 2 are me, and one is a bot) [11:08:38] and I'm a bot, too [11:11:34] ** gldnspud has left IRC ("Computer goes to sleep!") [12:19:52] ** pje has joined us [12:59:07] ** whit has left IRC () [12:59:55] ** whit has joined us [13:23:12] ** cmlenz has left IRC (Remote closed the connection) [13:31:47] ** bitmvnch has joined us [14:01:47] ** cmlenz has joined us [15:29:00] ** cmlenz has left IRC () [15:42:07] ** bitmvnch has left IRC (Read error: 110 (Connection timed out)) [15:48:09] ** cmlenz has joined us [16:14:16] pje is now known as pje_mtg [17:18:49] ** coderanger_ has left IRC (Success) [17:38:17] ** bitmvnch has joined us [17:47:22] pje_mtg is now known as pje [18:06:37] ** gldnspud has joined us [19:00:36] whit is now known as whit|out [19:55:25] ** gldnspud has left IRC ("Computer goes to sleep!") [20:06:33] ** cmlenz has left IRC () [20:16:02] ** pje has left IRC ("Client exiting") [20:33:25] ** cmlenz has joined us [20:49:32] ** cmlenz has left IRC ()