Skip to content

regression: editable packages not showing up correctly in --list-all #70

Open
@virtuald

Description

@virtuald

I bisected to 0325313 as the breaking change. The key difference in the PKG_CONFIG_PATH shows what's happening:

Works:

% pkgconf --list-all
> Running the Python pkgconf
> $ PKG_CONFIG_PATH=:/Users/virtuald/projects/semiwrap/examples/demo/swdemo:/Users/virtuald/projects/semiwrap/src/semiwrap:/Users/virtuald/projects/mostrobotpy/subprojects/native.wpiutil/src/native/wpiutil /Users/virtuald/.virtualenvs/myvenv/lib/python3.13/site-packages/pkgconf/.bin/pkgconf --list-all

Does not works:

% pkgconf --list-all
> Running the Python pkgconf
> $ PKG_CONFIG_PATH=:/Users/virtuald/.virtualenvs/myvenv/lib/python3.13/site-packages/swdemo:/Users/virtuald/.virtualenvs/myvenv/lib/python3.13/site-packages/semiwrap:/Users/virtuald/.virtualenvs/myvenv/lib/python3.13/site-packages/native/wpiutil /Users/virtuald/.virtualenvs/myvenv/lib/python3.13/site-packages/pkgconf/.bin/pkgconf --list-all

I'm using hatching in editable mode, and it seems that it's finding the site-packages directory and not where the package actually lives (which is where the .pc files are).

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