On Sat, Apr 4, 2009 at 6:04 PM, Chris McDonough <span dir="ltr"><<a href="mailto:chrism@plope.com">chrism@plope.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Using an interface class for a constant "container" would often be handy but it<br>
might be an inappropriate use of interface classes. </blockquote><div><br>I would argue that it is appropriate, but that's probably related to my experience with languages other than Python.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
FTR, I do often put<br>
constants in an "interfaces.py" module at module scope (if there are more than<br>
one related, sometimes in a dictionary or within a non-interface class<br>
statement) in order to not feel I need to create some "constants.py" module.<br>
Maybe we could just agree that doing so isn't some sort of violation of intent?<br>
<div><div></div><div class="h5"></div></div></blockquote><div><br>That works, too.<br><br>Seeing as I how I don't see much interest, I'll consider this something not worth pursuing further.<br><br>Thanks,<br>Chris<br>
<br></div></div><br>