Breaking change in public API not reflected in version number
aleh-rymasheuski opened this issue · comments
Renaming jsonrpcclient.request to jsonrpcclient.requests is breaking, but version number doesn't indicate it.
Basically, an upgrade from 3.1.0 to 3.2.0 breaks all code that relies on from jsonrpcclient import request.
+1
Yes I apologise for this, the module had to be renamed in order put back the convenience function, which we had in version 2.
I'm usually very strict in following semver, but in this case didn't want to make a version 4 so soon after version 3.