v argument. Use the signatures below rather than copying a Python 3 v=2 call.
GetMachineCode
Compute this device’s machine code.Result
Returns the machine code computed by this implementation. Operating-system commands or unexpected system information can raise an exception. Handle a failure to compute an identifier before activating.Checks
Computes an identifier only. It does not contact the licensing API or verify a license.Example
The legacy helper has no version parameter. Use the same identifier when activating and comparing the returned license.IsOnRightMachine
Check whether the license contains the expected device or process identifier.Parameters
Result
ReturnsTrue when an activation matches, otherwise False. In floating mode, this implementation expects exactly one returned activation.
A missing license object or a failure while computing its machine code can raise an exception. Check that license loading or activation succeeded first.
Checks
Compares the identifier using the legacy floating/overdraft format when requested. It does not verify the signature, expiry or floating deadline. Machine checks require Maximum Number of Machines greater than 0.FAQ
Can I Pass v=2 to the Legacy Machine Helpers?
Can I Pass v=2 to the Legacy Machine Helpers?
No. Neither
GetMachineCode nor IsOnRightMachine in this implementation has a v parameter. You can supply an identifier to IsOnRightMachine through custom_machine_code; activate with the same value.Can I Use a Custom ID for a Floating Process?
Can I Use a Custom ID for a Floating Process?
Yes. Pass your process ID as
machine_code to activation and as custom_machine_code to IsOnRightMachine, with is_floating_license=True. Keep that ID until the process stops. This legacy floating check expects one activation in the returned license.