|
So just to clarify, updating helped or it didn't? Because if it helped, then there is nothing to look at as we already know why the error happened, fixed it, and released a new version.
This exact error as reported seems to be identical to a known issue in the original buggy 3.41.0 release. If your problem is fixed now, we want to know that. And if your problem is *not* fixed, then we definitely need to know that, so we can actually fix it! Because there were a lot of python changes in the latest version and it had to be rereleased three times. If there are still lingering bugs then we're not done...
|