winregistry version change compatability issue.

[DuncanM-XR]

It looks like when winregsitry has been updated from 1.1.1 to 2.0.0+ The import used in py-machineid here has become broken.

Trying the import in console with winregistry 1.1.1:

Python 3.12.7 | packaged by conda-forge | (main, Oct  4 2024, 15:47:54) [MSC v.1941 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from winregistry import WinRegistry
>>>
>>> import machineid
>>> machineid.id()
'41a48b3f-a696-4b8f-aa6a-3126feb1b2a5'

Trying the import in console with winregistry 2.0.1:

Python 3.12.7 | packaged by conda-forge | (main, Oct  4 2024, 15:47:54) [MSC v.1941 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from winregistry import WinRegistry
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'WinRegistry' from 'winregistry' (C:\Users\USERNAME\anaconda3\envs\debug_env\Lib\site-packages\winregistry.py)
>>>
>>> import machineid
>>> machineid.id()
'C3E5DCE8-76B5-B3A3-2E6B-13E152D43228'

I believe the change in return value of machineid.id() is due to this import issue, whereby the code path that would previously be acquiring the ID from the registry will now fall back to the powershell approach. This can result in machines reporting a different ID for the fingerprint when activating a license through keygen.

[ezekg]

Can you provide a PR that updates the dependency? For now, lock your version to Winregistry v1.

[DuncanM-XR]

Yeah I've pinned my version of winregistry to 1.1.1 for the time being. If I get time I'll put together a PR.