Legend:

In the "Alternate Plugin Packages" section of the plugin howto document, these sentences appear:

2

2

3

However, if you have developed an interface of your own, you may want to mandate that plugins for it are installed in your own plugins package, rather than in Twisted's. In this case, you probably also want to support yourproject/plugins/ directories for ease of development. To do so, you should make the __init__.py for that package contain at least the following lines.

3

However, if you have developed an interface of your own, you may want to mandate that plugins for it are installed in your own plugins package, rather than in Twisted's. In this case, you probably also want to support yourproject/plugins/ directories for ease of development. To do so, you should make the !__init!__.py for that package contain at least the following lines.

4

4

5

5

Followed by a code snippet to put in said `__init__.py`. However, the phrasing of the last sentence, ''for that package'', is ambiguous. It could refer to either `yourproject` or `yourproject.plugins`. It should be clarified that this documentation is referring to the `__init__.py` for `yourproject.plugins`, ie `yourproject/plugins/__init__.py`.