Timeline for Python classes with only one instance: When to create a (single) class instance and when to work with the class instead?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 28, 2015 at 14:29 | history | edited | Aaron Hall | CC BY-SA 3.0 |
added 114 characters in body
|
| Aug 6, 2015 at 6:53 | vote | accept | langlauf.io | ||
| Aug 5, 2015 at 6:21 | comment | added | langlauf.io | One more remark: You write "since all you want is a namespace". What I want is to group related code, i.e. functions and data, in one place, and have an interface to it. It is not so much about creating a "Type". During design, this would result in a class in a class diagram anyway, wouldn't it? | |
| Aug 5, 2015 at 6:15 | comment | added | langlauf.io | Thanks for your answer. Would you really suggest creating a new module (a new .py file) for every function (incl. variables)? This could result in many small .py files. Or would you group all (at least somehow related) "class-less" functions and variables in one module? | |
| Aug 4, 2015 at 23:46 | history | edited | Aaron Hall | CC BY-SA 3.0 |
added 191 characters in body
|
| Aug 4, 2015 at 22:55 | history | edited | Aaron Hall | CC BY-SA 3.0 |
added 6 characters in body
|
| Aug 4, 2015 at 22:48 | history | answered | Aaron Hall | CC BY-SA 3.0 |