3 ms·
The difference is tooling. Tools like Dependabot know that Jinja 2.0 is a major release of Jinja. They have no way of knowing that a package with a separate nam
by simonw 5y ago
The difference is tooling. Tools like Dependabot know that Jinja 2.0 is a major release of Jinja. They have no way of knowing that a package with a separate name is related to the first one.
- neolog 5y agoThe problem is that the two incompatible packages are only weakly "related": they're just two packages in the same space that may share some authors. What if I want to use code from both packages?
- simonw 5y agoYeah that's a reason in most languages to go with the separate package names. As a maintainer I'd much rather not have to put in that extra work just for the tiny minority of my users who might someday want to run two versions of my library in the same project.