[socal-piggies] Best practice in naming a module that extends another

[Joshua Gauthier]

Ldapalicious.py

Ldapinator.py

Ldaponkulous.py

I'm just spitballin here

On Jun 22, 2011 4:20 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!

--
Jathan.
--

_______________________________________________
socal-piggies mailing list
socal-piggies at lists.idyll.org
http://lists.idyll.org/listinfo/socal-piggies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/socal-piggies/attachments/20110622/ab02bfcb/attachment.htm>