plugins
Duncan M. McGreggor
Can I get a vote on plugin naming convention? If we go the plugin
route, developers will need to create python packages in
PREFIX/plugins. Since these packages need to be named after multi-word
service checks like "HTTP status" or "FTP download", we will be
violating PEP 8 (the more-than-one-word-for-packages bit). So, what I'd
like to hear people's opinions on are *how* we should violate it :-)
1) use camel case: PREFIX/plugins/HttpStatus
2) use lower case: PREFIX/plugins/httpstatus
I think I'm leaning towards #1 for a couple reasons:
1) it's more legible
2) these are *plugins*, not official python packages, and
3) the naming convention for python eggs is CamelCase, and since there
could be eggs in the plugin directory, there would at least be symmetry
in the casing
Thoughts?
d
Raúl Alexis Betancor Santana
> 1) use camel case: PREFIX/plugins/HttpStatus
> 2) use lower case: PREFIX/plugins/httpstatus
My vote if for option 1
--
Saludos.
Raúl Alexis Betancor Santana
Director Gerente
Dimensión Virtual S.L.
Allan Bailey
>
>One more thing before I sleep:
>
>Can I get a vote on plugin naming convention? If we go the plugin
>route, developers will need to create python packages in
>PREFIX/plugins. Since these packages need to be named after multi-word
>service checks like "HTTP status" or "FTP download", we will be
>violating PEP 8 (the more-than-one-word-for-packages bit). So, what I'd
>like to hear people's opinions on are *how* we should violate it :-)
>
>1) use camel case: PREFIX/plugins/HttpStatus
>2) use lower case: PREFIX/plugins/httpstatus
+1 for 1)
>I think I'm leaning towards #1 for a couple reasons:
>1) it's more legible
>2) these are *plugins*, not official python packages, and
>3) the naming convention for python eggs is CamelCase, and since there
>could be eggs in the plugin directory, there would at least be symmetry
>in the casing
>
>Thoughts?
>
>d
>
>
>>
--
.allan.