tgext.pluggable.plug actually imports the package of the pluggable (in your example "photos"). There is currently no API in tgext.pluggable to drive from where they are imported, but as plain __import__ is used you can actually rely on the python lookup itself (sys.path, sys_meta_path, so on...)
Keep in mind that you cannot plug a pluggable multiple times anyway, even when imported from different paths. 2014/1/12 solab solab <[email protected]> > Hi all > I want to configure the pluggble to take as plugin a copy of the original > plugin > but located in a project specific location. > > Acctually In app_cfg.py I have > plug(base_config, 'photos') > and this is working correctly and takes the plugin located in > ..../python2.6/site-packages/tgapp_photos-0.2.7-py2.6.egg > > But i would prefer a copy of the plugin to be located in > "project_base/photos" > > Is there a way to specifiy an other location via pluggable.plug or via > base_config ? > > Some hints ? > > Cheers Gio > > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/groups/opt_out.
