Timeline for Python multiple inheritance, initializing from a common subclass
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2017 at 18:27 | vote | accept | teddybear123 | ||
| Feb 14, 2017 at 15:04 | history | edited | ᴀʀᴍᴀɴ | CC BY-SA 3.0 |
added 2 characters in body
|
| Feb 14, 2017 at 14:58 | answer | added | ᴀʀᴍᴀɴ | timeline score: 5 | |
| Feb 14, 2017 at 14:58 | comment | added | Sergius | This task really doesn't make any sense. Of course, you can call in all inheritance sequence, but still - why you need that? | |
| Feb 14, 2017 at 14:56 | answer | added | Daniel Roseman | timeline score: 4 | |
| Feb 14, 2017 at 14:52 | history | asked | teddybear123 | CC BY-SA 3.0 |