Minor refactoring. The BaseTable implementation is now split into an actual "BaseTabl...
authorMichael Elsdörfer <michael@elsdoerfer.info>
Wed, 24 Mar 2010 16:30:36 +0000 (17:30 +0100)
committerMichael Elsdörfer <michael@elsdoerfer.info>
Wed, 24 Mar 2010 16:30:36 +0000 (17:30 +0100)
commitf5e5b2fd1cf3e66087aafdf9a33376d4d21b5537
treee2bb519bf050475389aecc72ea13d432e80dfb9b
parentf51042824b6fb9ab6b1d830f93df6c5840574887
Minor refactoring. The BaseTable implementation is now split into an actual "BaseTable", and a "MemoryTable". This is because in the future we'd like to offer at least one additional table implementation, an SQlTable, which is capable of doing raw queries. As a result, a better split of the base funtionality and what is provided by a base class is appropriate.
README
django_tables/__init__.py
django_tables/base.py [moved from django_tables/tables.py with 85% similarity]
django_tables/memory.py [new file with mode: 0644]
django_tables/models.py
tests/test_basic.py
tests/test_memory.py [new file with mode: 0644]
tests/test_templates.py