Module name conflict with standard library

[Felix Wiemann]

Jorge Godoy wrote:

> Felix Wiemann writes:
>
>> So I hope that absolute imports will get implemented in Python 2.4.  I
>> think I'll name my module 'Curses', as John suggested (even if that's
>> asking for trouble on Windows systems).
>
> Do you really need to use the same name?  How about something like
> "mCurses" (myCurses) or "oCurses" (own Curses), etc. ?

Hmmm, yes.  Or maybe "ncurses" (even though it's actually wrong, but at
least it's obvious).

> It avoids the name clash on Windows and states that you are really not
> referring to the standar curses module.

True.

-- 
Felix Wiemann -- http://www.ososo.de/