here is what i am doing

[Skaperen]

while thinking out some testing logic, i keep ending up with a lot of redundancy. but, i keep thinking to myself that at least this only happens once per file to be opened. that can still impact scripts intended to do things like scanning trees and opening every file to back them all up.

i'm now thinking i should avoid having the ability to mix the ways of providing various arguments and require one way be used in the API. then i can start by determine which way is being used, raise TypeError if 2 or 3 are used at same time (match or no match), and select the next test logic based on which way.

1. name and mode in positional arguments
2. name= and mode= in keyword arguments
3. name= and individual modes in keyword arguments:
    append=  (like 'a')
    binary=  (like 'b')
    exwrite= (like 'x')
    read=    (like 'r')
    text=    (like 't')
    update=  (like '+')
    write=   (like 'w')
these want true/false, anything that can follow if, not.