single-instance class

[Skaperen]

none of the argument/options parsers i have seen fit my needs. it appears i need to create my own. this is a case where i need only one instance. i would not be making multiple instances of it. i do not see a reason for this to be a class other than for the convenient reference naming which a module name can do anyway. what is the best way to construct this?

[metulburr]

I still just use a class and create only one instance.

[Gribouillis]

Same for me. It is a classical technique. It is related to the refactoring that Martin Fowler calls "Replace Function with Command". His arguments are the better flexibility of a class, the possibility of creating methods and fields to decompose a complex task, the possibility of inheritance, etc.

[Skaperen]

i consider the module to be the created instance after it is imported. then it is like each function in that module is a method.