Skip to content

robust path management and package specification #31

@tpapp

Description

@tpapp

Currently we map a package or a module to a path using undocumented internals (cf #30 which changes this).

I am not aware of a robust mechanism for doing this, other than calling internals. I wonder if we could just default to working on the current project.

It is still not clear how to query the path of the resulting cov files (again, other than hacks).

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