Timeline for Duck typing, data validation and assertive programming in Python
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2015 at 18:28 | vote | accept | warvariuc | ||
| Jun 17, 2013 at 15:46 | comment | added | btilly | Let's put it this way. I find that inheritance maps poorly to how I like to evolve designs. I prefer composition. So I shy away from asserting that this has to be of that class. But I'm not opposed to assertions where I think that they save me something. | |
| Jun 17, 2013 at 8:12 | comment | added | warvariuc | I prefer v.3, especially when designing the interface - writing new classes and methods. Also i consider v.3 useful for API methods - because my code is new for others. I think assertive approach is a good compromise, because it gets removed in production when running in optimized mode. > Blowing up on that is more likely to catch a typo than it is to stop someone from doing something reasonable. < So, you don't mind having such validation? | |
| Jun 17, 2013 at 6:58 | history | answered | btilly | CC BY-SA 3.0 |