On Tue, Aug 18, 2009 at 4:14 PM, Thierry<thi.l...@gmail.com> wrote: > Should I stick with custom class names and refer to them throughout my > project instead? > Thanks for any feedback, > Thierry. >
Hi, from side of python syntax, it is possible. See this example: mar...@kraksna:~/$ python Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> class Test(object): ... def test1method(self): ... print "test1method" ... >>> class Test(Test): ... def test2method(self): ... print "test2method" ... >>> mytest = Test() >>> mytest.test1method() test1method >>> mytest.test2method() test2method My opinion is that this construction is unclear and hard to read (because other code readers expect, that SomeClass which they know has common interface). You also have to import new class definition before every attempt of class usage, because when not, python dont print any warning/error, but maybe use generic class with old behaviour. Happy debugging ;). Regards, Marek --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
