[BUG] Undocumented breaking change in v3.21.0 - unable to import NOT_SET
from schemathesis.utils
#1890
Closed
3 tasks done
Labels
Status: Needs Design
Issue requires more design work
Type: Bug
Errors or unexpected behavior
Type: Compatibility
Compatibility with other tools
Type: Documentation
Documentation improvements
Checklist
Describe the bug
My project compares
Case.body
toNOT_SET
to determine if the case has a body. Commit dfbcce1 movedschemathesis.utils.NOT_SET
toschemathesis.constants
. As my use ofNOT_SET
is in a library and components using that library use different minor versions ofschemathesis
, I'm unable to upgrade to 3.21 without upgrading all of them at the same time, which I'd like to avoid.In general, this appears to be an undocumented breaking change, the only mention being this line in the changelog:
To Reproduce
🚨 Mandatory 🚨: Steps to reproduce the behavior:
schemathesis==3.20.*
.NOT_SET
fromschemathesis.utils
.schemathesis==3.21.0
.ImportError
due to dfbcce1.Please include a minimal API schema causing this issue:
N/A
Expected behavior
No breaking changes between minor versions; I should be able to import
NOT_SET
fromschemathesis.utils
.Environment
N/A
Additional context
If
NOT_SET
is not part of the public API, perhaps it should be moved into a private (i.e. underscore-prefixed) module, or prefixed with an underscore itself. (If we're using SemVer or similar here, that change should wait for v4.)The text was updated successfully, but these errors were encountered: