ID 536145 - Nuke's Python install incorrectly overrides' its own Shiboken Reloader class

Follow

Problem summary
Nuke's Python install incorrectly overrides' its own Shiboken Reloader class
 
Customer reported version
Nuke 14.0v1
 
Customer reported platform
CentOS 7
 
Steps to reproduce
1) Download Qt.py to your .nuke directory from the following link: https://github.com/mottosso/Qt.py/blob/master/Qt.py
2) Add from Qt import QtWidgets to a menu.py in the .nuke directory.
3) Launch Nuke and observe any errors in Nuke's console.
 
Expected behavior
Nuke should correctly use the Shiboken Reloader class and not report errors.
 
Actual behavior
An error is printed in Nuke's console for: 
Python error occurred. A Python exception occurred:TypeError: _module_valid_override() missing 1 required positional argument: 'mod'  File "C:\Program Files\Nuke14.0v1\pythonextensions\site-packages\shiboken2\files.dir\shibokensupport\__feature__.py", line 142, in _import    return original_import(name, *args, **kwargs)  File "C:\Program Files\Nuke14.0v1\pythonextensions\site-packages\hiero\core\shibokensignatures.py", line 44, in <module>    mapping.Reloader().update()  File "C:\Program Files\Nuke14.0v1\pythonextensions\site-packages\shiboken2\files.dir\shibokensupport\signature\mapping.py", line 210, in update    g.update(g.pop(proc_name)())  File "C:\Program Files\Nuke14.0v1\pythonextensions\site-packages\shiboken2\files.dir\shibokensupport\signature\mapping.py", line 580, in init_PySide2_QtMultimedia    check_module(PySide2.QtMultimediaWidgets)  File "C:\Program Files\Nuke14.0v1\pythonextensions\site-packages\shiboken2\files.dir\shibokensupport\signature\mapping.py", line 218, in check_module    if not Reloader.module_valid(mod):
 
Workaround
There is no available workaround at this time.
 
Reproduced by Support in:
Nuke 14.0v3 - Windows 10, macOS 10.15 Catalina
Nuke 14.0v1 - Windows 10, macOS 10.15 Catalina - regression
 
Unable to reproduce bug in:
Nuke 13.2v6 - Windows 10, macOS 10.15 Catalina
 
Earliest version tested
Nuke 13.2v6 - This issue doesn't appear in this version and has regressed 

    We're sorry to hear that

    Please tell us why