thank you for reaching out to us and pointing this out. This is indeed not correct and will be fixed in an upcoming release. I have added the 'to fix' tag to this posting to track and report the change when it has been done.
the example has been fixed and both computations now will reflect the correct result. The fixed example will be included with an upcoming release of the Python SDK documentation.