no ambiguous antecedents (plugins documentation edition)

[exarkun]

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

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.

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.

[jafd]

In this case, you probably also want to support yourproject/plugins/ directories for ease of development. To do so, you need to make yourproject/plugins directory a regular Python package, and its __init__.py should contain at least the following lines.

Would that be okay?

[indigo]

please review. merge with .misc topfile?

[exarkun]

(In [32747]) Branching to 'ambiguous-antecedents-5156'

[exarkun]

(In [32748]) Apply plugins-ambiguous-antecedents-5156.patch

refs #5156

[exarkun]

Thanks for taking a look at this.

1. There's a typo in the first new sentence.
2. I don't think supporting these plugins directories is an example. It's just something you might want to do. So the "For example" is off-putting.

Otherwise fine. I'll tweak that first sentence trivially and apply. Thanks again.

[exarkun]

(In [32749]) Fix typo, tweak phrasing

refs #5156

[exarkun]

(In [32751]) Merge ambiguous-antecedents-5156

Author: indigo Reviewer: exarkun Fixes: #5156

Clarify the language in the plugin howto regarding how to create new splittable plugin-holding directories (in the way twisted/plugins/ can exist in multiple places and have all contents merged).