Skip to content

man pages not available when installed with pipx #1023

Open

Description

@jmdevin

Description

When installed via pipx install bpython, the man pages for bpython are not available (even the .rst files don't seem to be present).

I took a look at pipx's documentation and they linked to (pycowsay) as an example. From what I can tell the only difference is pycowsay has the man pages built and included in the repo, whereas bpython just has the .rst files.

Version info

OS: Ubuntu 24.04.01
pipx: 1.4.3
python: 3.12.3
bpython: 0.24

Activity

  1. sebastinas commented on Sep 1, 2024

    @sebastinas
    Contributor

    The man pages are only built and installed if sphinx is available.

  2. jmdevin commented on Sep 8, 2024

    @jmdevin
    Author

    Would it be possible to include the built pages in the repository? It would be useful for users with a situation like mine.

  3. jmdevin commented on May 11, 2025

    @jmdevin
    Author

    @sebastinas I tried installing sphinx with pipx, then installing bpython, but it still didn't build the man pages. I assume this is caused by pipx's manner of installing packages, so in this case I think it's more accurate to say that the man pages just aren't built if someone is using pipx.

  4. sebastinas commented on May 11, 2025

    @sebastinas
    Contributor

    So is pipx ignoring data_files?

  5. sebastinas commented on May 11, 2025

    @sebastinas
    Contributor

    No, it doesn't. But installing sphinx with pipx get sphinx installed in a different virtual env. So it's not available when building bpython.

  6. jmdevin commented on May 11, 2025

    @jmdevin
    Author

    Yes, I didn't quite have time to check the docs yesterday but I had started to suspect that. I don't have a definitive answer for whether pipx would generate the docs if sphinx were installed globally via regular pip or apt or something, but that isn't recommended anyway so it's somewhat irrelevant.

    Overall, I think if you want to start tracking the generated man file as part of the repo itself that would be great, but otherwise we can close this issue as a "won't fix" since the actual problem has been identified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions