Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about the
best practices when it comes to developing a plugin system for a
Python package.
Should plugins be modules in a separate package?
On 22 Feb 2007 04:53:02 -0800, Flavio [EMAIL PROTECTED] wrote:
Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about the
best practices when it comes to developing a plugin system for a
Flavio wrote:
Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about the
best practices when it comes to developing a plugin system for a
Python package.
Should plugins be
On Feb 22, 11:00 am, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Flavio wrote:
Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about the
best practices when it comes to developing
I will search the archives. I am aware of the setuptools feature It is
quite nice. But the documentation is not very clear on how to define
entry point groups on the importing end, i.e. how to prepare a an
application to accept plugins it doesn't even now exist.
The entry-points are just a
On Feb 22, 11:01 am, Jean-Paul Calderone [EMAIL PROTECTED] wrote:
On 22 Feb 2007 04:53:02 -0800, Flavio [EMAIL PROTECTED] wrote:
Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about
On Feb 22, 10:53 am, Flavio [EMAIL PROTECTED] wrote:
Hi,
Nowadays the addition of functionality to programs by means of
plugins is very frequent.
I want to know the opinions of experienced Python developers about the
best practices when it comes to developing apluginsystemfor a
Python
Simple plugin system proposal:
have a package (directory with __init__.py) called plugins where the
actual plugins are modules in this directory.
When the main script imports the plugins package, all plugin modules
would be available as plugins.pluginA, plugins.pluginB , etc.
A
On Feb 22, 12:36 pm, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Simple plugin system proposal:
have a package (directory with __init__.py) called plugins where the
actual plugins are modules in this directory.
When the main script imports the plugins package, all plugin modules
would be
On Feb 22, 12:51 pm, Flavio [EMAIL PROTECTED] wrote:
On Feb 22, 12:36 pm, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Simple plugin system proposal:
have a package (directory with __init__.py) called plugins where the
actual plugins are modules in this directory.
When the main
On Thu, 22 Feb 2007 15:36:42 +0100, Diez B. Roggisch [EMAIL PROTECTED]
wrote:
Simple plugin system proposal:
have a package (directory with __init__.py) called plugins where the
actual plugins are modules in this directory.
When the main script imports the plugins package, all plugin
Jean-Paul Calderone wrote:
On Thu, 22 Feb 2007 15:36:42 +0100, Diez B. Roggisch
[EMAIL PROTECTED] wrote:
Simple plugin system proposal:
have a package (directory with __init__.py) called plugins where the
actual plugins are modules in this directory.
When the main script imports the
On 22 Feb, 16:13, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Darn. You're right of course - I just got the basic idea, and formed in my
mind the get the modules filename, thus the path, glob over it for *py,
and thus get the subsequent module names-pattern. Which is trivial of
course, but not
On Feb 22, 2:04 pm, Paul Boddie [EMAIL PROTECTED] wrote:
On 22 Feb, 16:13, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Darn. You're right of course - I just got the basic idea, and formed in my
mind the get the modules filename, thus the path, glob over it for *py,
and thus get the
14 matches
Mail list logo
