Skip to content

Ambiguity with BSD license trove classifier #5

@thatch

Description

@thatch

PEP 639 will make this a little better, but once documentation exists we should at least document that looping through the licenses looking for a trove classifier match is ambiguous in some very common cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions