Pystandalone (the binary) has its own crypto API (which still needs to be documented). However, when writing a script that uses it, you might want to verify that it works. You could generate a binary with no payload (which acts as a single binary python interpreter) to test your script with, but it might also be a nice idea to create a compatibility layer within the pystandalone python/builder package.
For example: from pystandalone import crypto, which underwater supports the _pystandalone crypto implementation, but provides a similar compatibility implementation using something like pycryptodome.
The _pystandalone.c code is our own and not part of upstream pystandalone, so we can be flexible in how it should behave.
Pystandalone (the binary) has its own crypto API (which still needs to be documented). However, when writing a script that uses it, you might want to verify that it works. You could generate a binary with no payload (which acts as a single binary python interpreter) to test your script with, but it might also be a nice idea to create a compatibility layer within the pystandalone python/builder package.
For example: from pystandalone import crypto, which underwater supports the _pystandalone crypto implementation, but provides a similar compatibility implementation using something like pycryptodome.
The _pystandalone.c code is our own and not part of upstream pystandalone, so we can be flexible in how it should behave.