Grab packaging data from setup.py?

[tmontes]

NOTES:

• IIUC, briefcase 2.x -- used to package Mu up until today -- seems to grab packaging (meta) data from setup.py.
• Here's an excerpt from the current setup.py in mu:

...
    entry_points={"console_scripts": ["mu-editor = mu.app:run"]},
    options={  # Briefcase packaging options for OSX                                      
        "app": {"formal_name": "mu-editor", "bundle": "mu.codewith.editor"},
        "macos": {"icon": "package/icons/mac_icon"},
    },
...

• How about we have pup optionally grab its metadata from there? :-)

[tmontes]

EXPLORED THIS:

• briefcase extracted data from setup.py becase it used to be implemented as a setuptools command.

WENT CREATIVE:

• Where in a standard wheel metadata could we store/keep pup-related packaging data.
• Came up with something crazy, that seems to work, but that is horribly brittle.
• pup will look into the standard wheel metadata for the project's dependencies.
• For all those dependencies associated with the pup extra:
  • Assume the dependency name is a pup packaging paramenter (like --icon-path, for example).
  • Assume that the dependency version is specified as <operator> <value> and i) disregard the operator, while ii) taking the value as the parameter's value.

BENEFITS:

• Should work with any tooling that produces standard wheel metadata.

TRADE-OFF:

• If/when ever pip starts validating extra dependency version formats, this no longer works and pup fails!

YIKES! :)

[tmontes]

PROGRESS:

• Merged PR Collect packaging parameters from the project's wheel metadata. #224 implementing the above described idea.

NEXT:

• Have the CLI options override whatever is collected from the package metadata extra deps.

[tmontes]

CLOSING after having merged PRs #224 and #226.