One of the DateTime library tests fails with this error message:

Expected error 'ValueError: Unsupported input 'None'.' but got 'ValueError: Invalid timestamp 'None'.'.

My expectation is that the keyword is used with Python None object and earlier the type has been validated internally and rejected as unsupported type. Now that the keyword has a type hint defined as a union with str as one of the accepted values, the given None is converted to a string and now the type isn't anymore invalid but the value itself is. I consider the new behavior fine so the fix is updating the test.

I recommend you to run at least DateTime library tests locally before committing changes.

Notice that I reviewed this PR at silentw0lf#1. I assume the code is same there so comments apply also to this PR. The other should be closed now.

One of the DateTime library tests fails with this error message:

Expected error 'ValueError: Unsupported input 'None'.' but got 'ValueError: Invalid timestamp 'None'.'.

My expectation is that the keyword is used with Python None object and earlier the type has been validated internally and rejected as unsupported type. Now that the keyword has a type hint defined as a union with str as one of the accepted values, the given None is converted to a string and now the type isn't anymore invalid but the value itself is. I consider the new behavior fine so the fix is updating the test.

I recommend you to run at least DateTime library tests locally before committing changes.

You are correct. The Python None object is no procosessed as a str type within the python function/keyword convert_time (right from entering the the function, no conversion within).