Query setuptools entry points for plugins #6

Closed
pedersen opened this Issue Sep 24, 2012 · 4 comments

Comments

Projects
None yet
2 participants
Owner

pedersen commented Sep 24, 2012

This issue existed in Trac. The original can be viewed at http://trac.turbogears.org/ticket/2206

This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/61

Owner

pedersen commented Sep 24, 2012

Original Author: pedersen, Original Timestamp: 2011-03-29 01:59:36.786000

Original Body: In TurboGears 1.x plugins which use a specific entry point have a chance to do specific actions on startup/shutdown. For TurboMail? it would be very nice to have this functionality in 2.0.

Unnecessary resource usage for plugins the user does not want: It should be encouraged for plugin writers to have a special flag like 'mail.on' in the configuration. If that flag is not set to True, the plugin must not do anything so no memory wasted :-)

While I don't have the time to provide you with code and unit tests, I can write the docs if the feature goes in.

Owner

pedersen commented Sep 24, 2012

Original Author: pedersen, Original Timestamp: 2012-08-24 01:41:05.645000

Original Body: - version: 2.1.0 --> 2.1.5

  • milestone: 2.2.0 --> 2.3.0
Owner

amol- commented Jan 14, 2014

@pedersen as you were the original author of this ticket, do you remember the reason for this? Can we consider most of this covered by tgext.pluggable even thought it doesn't use setup.py entry_points?

Owner

amol- commented Apr 25, 2015

As there has been no discussion on this for a few years I consider it satisfied by tgext.pluggable

@amol- amol- closed this Apr 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment