Skip to content

Question: would a docs PR recommending pipx for install-time conflicts be welcome? #889

@Pawansingh3889

Description

@Pawansingh3889

Quick question before I file a full proposal + PR.

pip install scanapi fails in two of my projects because ScanAPI 2.12.0's strict pins (MarkupSafe==2.1.2, rich==14.0.0) collide with transitive deps of newer Streamlit / Prefect. Installing via pipx — which gives ScanAPI its own isolated venv and still puts the CLI on PATH — fixes it cleanly.

Would a small README / wiki PR adding pipx as a documented install path (alongside the existing pip install scanapi, not replacing it) be welcome? Happy to write it if so.

If you'd rather the pins themselves were loosened, that's a bigger conversation and I'll hold off.

Came across this while using ScanAPI on real projects after watching your PyCon DE & PyData 2026 session — thanks for the talk.

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