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

[Grig Gheorghiu]

I seem to remember reading somewhere that in these cases one solution
is to prefix the module name with something unique to your
organization. In your case you could name it aol_ldap.py for example.
Or just aoldap ;-)

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!
>
> --
> Jathan.
> --
>
> _______________________________________________
> socal-piggies mailing list
> socal-piggies at lists.idyll.org
> http://lists.idyll.org/listinfo/socal-piggies
>