[socal-piggies] Best practice in naming a module that extends another
Dan Stromberg
strombrg at gmail.com
Wed Jun 22 16:06:53 PDT 2011
Not very creative, but why not ldap_wrapper.py? Or
<nameofbusinessunit>_ldap_wrapper.py?
On Wed, Jun 22, 2011 at 2:19 PM, Jathan McCollum <jathan at gmail.com> wrote:
> Hello!
>
> So I have this module I wrote that extends the interface to
> python-ldap, which is imported as 'ldap' when installed. I plan to
> bundle my new ldap wrapper into a package (e.g. aol.ldap).
>
> It will inevitably cause a problem if I name it ldap.py. So I'm
> looking for feedback on how I should name this! Opinions, please!
>
> Things I've considered:
>
> ldapper.py
> _ldap.py
> ldap_.py
>
> None of them feel right. Blah!
>
--
Dan Stromberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/socal-piggies/attachments/20110622/b718c99a/attachment.htm>
More information about the socal-piggies
mailing list