On Sun, 2010-09-12 at 15:29 -0700, Ben Bangert wrote: > On Sep 12, 2010, at 3:13 PM, Chris McDonough wrote: > >>> What's the best way to figure out the entry point name to use and the >>> right syntax, for any arbitrary entry point? >> >> It's egg:<DistributionName>#entrypointname >> >> The entry point names for a given package are in >> EGG-INFO/entrypoints.txt . >> >> Paste defaults to using the name "main" as the entry point name, so >> these two Paste names are equivalent: > > Also, not sure what type of license Ian has his Paste docs under, but I want > to pull in the necessary information about how to configure INI files, such > that a user doesn't have to go to the PasteDeploy docs to look-up how to set > a filter middleware, etc. Having this in one Configuration section of the > Pylons docs also means we can provide a list of all the available middleware > (and entry point names!) so that someone could look through, see what they > want in their stack, and easily add it to the appropriate INI file (cause the > dev.ini will prolly differ from the prod.ini). > > Right now, its kind of a pain to: > A) See what middleware is available with stock Pylons > B) Figure out what the heck the entry point name is, without which, you can't > use it in the INI file, I usually have to read the source to find the damn > entry point names, we should save our users from doing that > C) Know what options each piece of middleware can take in the INI file
Most of this is already handled via "paster points", e.g. do "env/bin/paster points paste.filter_app_factory" in a virtualenv that has Pylons installed. What that doesn't do is give you the "egg name", although you don't really need the egg name; it gives you the dotted name to the middleware factory, which can also be used. - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
