-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've actually written a few plugins that depend on others "api" or base plugins (e.g. clientsplugin, xmlrpc plugin, contacts plugin). I've not submitted a few of these back in part because I didn't think there was a good way to enforce the dependency other than silently failing. install_requires is a good idea and I will use that in the future. So yes, plugin dependencies are needed, but it looks like we can do that with setuptools.
Thanks, CM Lubinski - --- http://cmlubinski.info Noah Kantrowitz wrote: > Plugins can use install_requires just like any other package and setuptools > will make sure its dependencies are loaded first. This is one of the many > advantages of plugins being real packages. This won't work for "single-file" > plugins, but the same goes for a bunch of other features. > > --Noah > > On Apr 27, 2010, at 6:09 AM, Remy Blank wrote: > >> Carsten Klein wrote: >>> This would basically require all plugin authors to reinvent the wheel >>> everytime they have more complex requirements than what the usual >>> deployment scenarios are. >> Well, that's exactly the point: we haven't had this request before, and >> I interpret this as the majority of plugins *don't* need this functionality. >> >> But maybe authors of plugins having more complex requirements could >> chime in at this point and share their experience? >> >> -- Remy >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvbCV4ACgkQfzi1OiZiJLD6NQCffNV6rfaU4yLcJLcQ02kWxWnP lEEAmwYBe+5nCIJBe9dzmZGa3aCR/4AO =TLY4 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
