Timeout asserts in _config.py stripped by python -O

[omnislash157]

Hey —

Testing an analysis tool I built on existing reputable repos to see if it works. The tool's for non-technical dummies like me to be able to have a seat at the table. Anyway it ran and found that the 4 asserts in Timeout.__init__ guard against conflicting arguments but get stripped by python -O:

# _config.py, Timeout.__init__
assert connect is UNSET
assert read is UNSET
assert write is UNSET
assert pool is UNSET

Under -O, a user passing both timeout=5 and connect=10 gets no error — both values coexist silently.

Same validation, survives optimized mode — same line you had but swap to:

if connect is not UNSET:
    raise ValueError("Cannot set both `timeout` and `connect`.")

Happy to PR it if you're open to it, or just rip it and fire it off as your own — I'm just testing the one-shot-for-dummies stack I built. Funny things happen when you give stuff away for free because that's not how people generally are.