Logged In: YES 
user_id=80475

While unfortunate, this function already suffers from excess
complexity.  Changing the behavior and adding backwards
compatability features would make the situation worse.

Also, the two different behaviors were not accidental. 
Someone put them in for a reason.  There may be orthogonal
use cases.  Ideally, that need would have been been through
two different functions/methods.  But, if you change the
behavior, you're likely breaking an entire class of use cases.

So, I'm -1 on mucking with this prior to Py3.0.