Looking for a new maintainer

[jgonggrijp]

I'm about to release version 1.1.0 of pip-review. In addition to features and bugfixes that were requested or contributed in the past few years, that release will include a notice that I'm looking for a new maintainer to take over.

Until there is a new maintainer, at least in the foreseeable future, I will continue to accept pull requests and release new versions to PyPI once in a while. However, please be prepared that my time investment in pip-review will continue to be as slim as it has been for the past few years.

The reason my time investment in pip-review declined, is that I'm no longer using it myself. For the same reason, I now feel that I'm not the right person to keep this tool in the air.

pip-review is a very small and relatively simple project. If you are actively using pip-review and you don't mind adopting it, please submit a pull request and mention in the pull request that you're interested in taking over.

[Jacksole]

While, I'm not the prolific Python programmer, I'm willing to take a shot at taking over or assist in maintaining the program. @jgonggrijp

[jgonggrijp]

Thank you for the kind offer, @Jacksole! Let's ride together in this for a while and see what happens.

Other people are still welcome to express their interest as well.

[Jacksole]

Ok, thanks @jgonggrijp . So what would you need me to do?

[jgonggrijp]

Perhaps pick an issue from the list and see what you can do about it. Maybe you can figure out the issue that you reported yourself.

[jgonggrijp]

@Jacksole also, please take your time and feel free to ask questions. I'm not in a hurry and it is okay to be new at this.

[Jacksole]

@jgonggrijp Thanks

[berislavlopac]

@jgonggrijp Have you thought about pitching the project to PyPA? It looks like something that might make sense as actual part of pip itself...

[jgonggrijp]

@berislavlopac Thanks for the suggestion. I think the odds are bleak, though. pip-review was removed from pip-tools. I just adopted it because I didn't want it to disappear. Even pip-tools, which is much more sophisticated and has a much larger user base than pip-review, is not a part of pip, even after many years of existence. Although it is a building block of pipenv.

[jonpalle]

@jgonggrijp you mentioned that you are not using pip-review anymore. May I ask why that is? I think it is a neat little tool 😃

[jgonggrijp]

@jonpalle Of course you may ask. Nowadays, when developing a Python project, I always create a dedicated virtualenv for that project. I pin the dependencies using pip-tools and I rarely update the packages in the virtualenv, except when an automated dependency tracker like @dependabot warns me about a security issue (in which case I'm updating only one dependency, by accepting a pull request) or when dusting off a stale project. In the latter case, pip-compile -U ; pip-sync does a much cleaner job than pip-review -a; the former produces a coherent set of compatible dependencies and removes packages that are no longer needed, while the latter will eventually accumulate obsolete packages and might install incompatible packages side by side.

Of course, I could do pip-review -i instead of pip-review -a, but it feels like more effort. I think it could be sensible to use pip-review -i for user-wide or system-wide packages, but I happen to use MacPorts for that already.

[jonpalle]

Thanks @jgonggrijp for enlightening me (and hopefully others)! 😉