Closed graingert closed 4 years ago
@takluyver ^
Be aware that the libmodernize
name is exposed for selecting fixers (python-modernize -f libmodernize.fixes.fix_open
), so moving everything to modernize
could break scripts.
@takluyver we could hack it so modernize depended on a pypi libmodernize shim, but I think releasing v1 and documenting the breakage makes most sense?
Your call. I think we made it so that the short names work as well (python-modernize -f open
), so people have an easy way to avoid relying on the package name. But I'm sure something will break.
@takluyver I can release this in 0.9 as a semver breaking change. I've only been using the short names
Up to you. It's bound to break something, somewhere, but maybe not much stuff, and I'm sure plenty of people are using modernize without pinning it to ensure a strictly semver-compatible version. But it's nothing people can't cope with.
I'd like to move everything under the
modernize
name and usemodernize/__main__.py