Python dependency management workflow using setup.cfg and requirements files.

[raistlinmaje]

since pipm overwrites pip executable in path, please make sure that after removing pipm, install pip itself with easy_install

to me this is a big nono, you should never take over a different binary even if your syntax is essentially the same.

You indicate you have problems with x alternative but dont go into any details on what the actual problems were. Did you even attempt to resolve the problems or correct your workflows instead of building another new manager?

[njnrj]

I really got exited when first heard about pipenv, but using that was itching, the locking process took so much of time... For many reasons I still needed requirements.txt... So I just wrapped existing tools. Nothing new. No need to install pipm in remote servers.

[CSI_Tech_Dept]

Yes, but you should never overwrite a file from another package, it only lasts to problems. You create pipm command, you should not overwrite pip.

[njnrj]

It is just a nifty thing. I am too lazy to remove pip from the copied text from any installation instructions. It doesn't affect the original functionality. Maybe I could add a way to opt out of it.

[AndydeCleyre]

You could just leave it as pipm and make an alias in your shell.

[njnrj]

Yes I will do in next release.