Needs a dedicated man page

So, pipenv ships with a man page that can be opened with pipenv --man, but that man page has a few issues regarding usability, because it is just built from the sphinx docs.

1. I don’t need any information about how to install pipenv. I already have it. (I don’t need user testimonials either.)
2. It doesn’t list the general cli usage at the top, which is one of the most useful sections.
3. The docs have a couple of links, which don’t convert to a man page.
4. Example files are good, but more useful at the bottom
5. More, that I don’t care to list right now.

Basically, it’s not really a man page. It’s a user guide in form of a man page. That said, it’s still good that there is something you can access (without an internet connection), but in the current state it’s pretty lackluster. Pipenv needs a dedicated man page imho.

[techalchemy]

I don’t think there’s anything wrong with big man pages, it’s pretty common. And it’s not that common to split things up. As a user of man pages I’d probably find that annoying

[kennethreitz]

we can’t ship a proper man page that works with man, i’ve looked into it heavily.

we can improve the “man” functionality, but i’d rather just remove it.

On Tue, Nov 21, 2017 at 8:30 PM, FichteFoll [e-mail] wrote:

What does this have to do with pip?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kennethreitz/pipenv/issues/1100#issuecomment-346215330, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHUVTi5COoAUjf4Qy3NIcRgt_XFZ5WSks5s43lLgaJpZM4Qjk5U .