[socal-piggies] Best practice in naming a module that extends another
Jathan McCollum
jathan at gmail.com
Wed Jun 22 14:19:53 PDT 2011
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.
--
More information about the socal-piggies
mailing list