Skip to content

Pip installation results in spurious docs package #296

@xkortex

Description

@xkortex

Hi,

Really nice project.

I noticed while building a lambda layer that the package creates the docs dir in site-packages alongside picodi.

In a blank dir:
mkdir python && pip install picodi -t python/

creates the structure:

.
└── python
   ├── docs
   │  └── conf.py
   ├── picodi
   │  ├── __init__.py
...
   │  ├── integrations
   │  │  ├── __init__.py
...
   │  │  └── starlette.py
   │  ├── py.typed
   │  └── support.py
   └── picodi-0.36.6.dist-info
      ├── INSTALLER
      ├── licenses
      │  └── LICENSE
...

with

       │ File: docs/conf.py
...
  14   │ project = "Picodi"

I'm pretty sure it's this line: https://github.com/yakimka/picodi/blob/bb729050c1a2c98a43509a97aa66fc7992041c15/pyproject.toml#L70C2-L70C31

I believe the easiest fix is just add docs to exclude =.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions