Code

Changes between Initial Version and Version 1 of Ticket #20313, comment 6


Ignore:
Timestamp:
05/27/13 01:47:22 (11 months ago)
Author:
thinkingpotato
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20313, comment 6

    initial v1  
    1111It feels a bit like overkill to me as well, but on the other hand seems like a price you have to pay for tight integration between different Django services. 
    1212 
    13 If I understand you correctly, developers would not be able to use methods starting with a keyword reserved by Django. Personally, I would be scared if framework interfered my design decisions so much. On the other hand, I bet that the first day after introducing it #django IRC would be flooded with questions on how to use it. Defining a class is clean and simple. Once sentence in the docs. Everyone who did object programming will understand it. 
     13If I understand you correctly, developers would not be able to use methods starting with a keyword reserved by Django. Personally, I would be scared if framework interfered my design decisions so much. On the other hand, I bet that the first day after introducing it #django IRC would be flooded with questions on how to use it. Defining a class is clean and simple. One sentence in the docs. Everyone who did object programming will understand it.