Skip to content
This repository was archived by the owner on Sep 26, 2025. It is now read-only.
This repository was archived by the owner on Sep 26, 2025. It is now read-only.

What to do about pip 19.1 #12

@jsignell

Description

@jsignell

I have been thinking a lot about this since pip broke editable installs yesterday. (https://discuss.python.org/t/pip-19-1-and-installing-in-editable-mode-with-pyproject-toml/1553/5). I thought #11 would solve our problems, but it created new ones, so I wanted to capture what I have thought about so far.

I think there are several options.

  1. Pin to <19.1

    • fine solution if this is temporary
  2. Use the flag every time you pip install with editable: pip install -e . --no-use-pep517

    • PRO: smallest change
    • PRO: stay on latest pip
    • CON: flag is too long to remember
    • CON: flag is controversial and might go away
  3. Switch to using python setup.py develop

    • PRO: get rid of pyproject.toml
    • PRO: does special things that pip doesn't do (build panel models)
    • CON: no good way to specify build-time dependencies
    • CON: conda doesn't recognize as best version when package already in env

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