Skip to content

Help Wanted: Guidance on Python Package Metadata #3

@kemitchell

Description

@kemitchell

I would greatly appreciate advice on how best to support Python dependencies. I've done a bit of Python programming, but I'm not up-to-date on package or project management.

Supporting a package type in License Zero boils down to two operations:

  1. Given a project directory for a project using dependencies, find all Python dependencies in it, and read metadata about them. For npm packages, the CLI recurses node_modules and reads licensezero properties of package.json files.

  2. Given a project directory for a License Zero project, write metadata in such a way that it will end up in depending projects' directories. For npm packages, the CLI writes a licensezero property to package.json metadata to licensezero.json files.

A few specific questions:

  1. Should the CLI write information to setup.py or its own metadata file, like licensezero.json?

  2. Any gotchas with a licensezero.json file? MANIFEST.in?

  3. Do Python developers have a CLI tool installed that will list all project dependencies and their paths?

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is neededquestionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions