Russell Keith-Magee
Russell Keith-Magee
#2146 is tracking the license metadata issue; we can solve that without necessarily solving the rest of PEP621 compliance.
I don't think we'll be able to *completely* replace the `[tool.briefcase]` section, because there will be settings that aren't part of PEP 518 that Briefcase requires (e.g., differentiating Formal Name...
Agreed that we can/should do some validation of the path of the Briefcase project if we know it will cause problems. We already do a version of this sort of...
> * How this interacts with "delivery" technology like Electron and Toga/Positron. > > This last point probably requires some very minor liaison with BeeWare to make sure we're doing...
Thanks for the suggestion. Briefcase tries wherever possible to adhere to current Python packaging best practices. Our migration to PEP 621 is a work in progress (see #1219 and #1235);...
> But what do we do with these situations? > > * `license = "[non-SPDX expression]"` (pre-PEP 621) This case is currently coerced into `license.file = "LICENSE"`, regardless of whether...
@mEp3ii2 Due to the wonders that is Github UI, I can't assign you to this ticket until you've commented on it
Looks great - thanks for your work on all this @JMah007 & @mEp3ii2 !
... huh. I'm more than a little surprised by this one, honestly. I didn't know that PEP 508 allowed specifying a module name that *isn't* valid Python module... I guess...
@manognya-b Absolutely! We don't formally assign bugs, so feel free to submit a fix (and an update for the existing test!)