Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 1.42 KB

project_name.md

File metadata and controls

42 lines (31 loc) · 1.42 KB

Project Name

Goals

To have a way to specify the name a project is listed under in an index.

Comparisons

Flit

Has a dist-name field.

When the import name matches the project name, the module field which also specifies the code to include in a wheel is used automatically.

Setuptools

Has a name field. There isn't an included way to infer the name from the package/module name.

Poetry

Has a name field.

This field also provides a default package name to figure out what code to put into a wheel.

Cargo

Has a name field.

Acts as the default name to infer the build names.

npm

Has a name field. There isn't any inference of what code to include.

Conclusions

  • Every tool has a way to manually specify the project's name
  • Nearly every tool has a name field (Flit is the only difference with dist-name)
  • 3 of the tools provide a mechanism to use a name/module specification to infer the other
    • Flit is the only one where the specification of what code to include infers the name instead of vice-versa