Breaking change introduced in MINOR version upgrade
See original GitHub issueHi, I’ve just noticed that there are breaking changes in pytest-mock when upgrading from 3.2.0 to 3.3.0.
The change I’ve noticed is that importing MockFixture
from pytest_mock
now breaks. I understand that the MockerFixture
type were introduced in 3.3.0 but MockFixture
was importable from the public API and it would be best to keep it that way for backwards compatibility in 3.x releases. I would only expect breaking of the public API in a MAJOR 4.x release.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Minor versions, breaking changes
See yesterday, we stumbled upon a breaking change. And yet we didn't do any major version upgrades. Luckily another colleague of mine, ...
Read more >why minor versions can't make incompatible changes? #365
If minor version can introduce a breaking change, it means for every minor upgrade a developer should make sure that nothing is broken, ......
Read more >Versioning and Breaking Changes
Major versions contain breaking changes. Minor versions add new features or deprecate existing features without breaking changes. Patch versions fix defects or ...
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
As soon as you realize that you've broken the Semantic Versioning spec, fix the problem and release a new minor version that corrects...
Read more >When is the right time to update a major version and not ...
A minor version would indicate new features, bug fixes, etc. Major versions would indicate a breaking change or other system-level modification.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the clarification!
Indeed, did not really foresee this use case. Not much can be done at this point thought.
Thanks anyway for the report!
Cheers,
@nicoddemus this is not a big issue for me anyway, though if this affects many users a 3.3.1 version could be released fixing that.