Issue with UUIDs not Matching

[curtiscook]

[x] Please checkout the F.A.Q page before creating a bug ticket to make sure it is not already addressed.

Describe the bug UUID appears to be detecting a type change. Validation passes if I exclude UUID types from validation. I could also not figure out what the new type was and validation still failed when I tried to ignore UUID -> int and UUID -> None

{'type_changes': 
	{"root['uuid']": {
		'old_type': <class 'uuid.UUID'>, 
		'new_type': , 
		'old_value': UUID('a0173d6a-df46-4ad3-bd6d-781629c03d1b'), 
		'new_value': UUID('a0173d6a-df46-4ad3-bd6d-781629c03d1b')}, 
	"root['account_uuid']": {
		'old_type': , 
		'new_type': , 
		'old_value': UUID('8b918a6b-661f-4f9e-801f-571fbaa98830'), 
		'new_value': UUID('8b918a6b-661f-4f9e-801f-571fbaa98830')}}}

To Reproduce I'm currently comparing 2 dictionaries with UUID fields. Validation passes if I exclude UUID's. Unfortunately I don't have a MRE available

Expected behavior I would expect the UUID types to match

OS, DeepDiff version and Python version (please complete the following information):

• OS: OSX
• Versions deepdiff = "^5.8.1" Python 3.8.8

[seperman]

Hi @curtiscook Can you please provide a piece of code that I can just copy paste and it will reproduce this problem?