Filipe Laíns 🇵🇸
Filipe Laíns 🇵🇸
I didn't know about REUSE, thank you for pointing it out. I've only skimmed it a bit, but I can't tell how it wouldn't be compliant? You can still have...
Agreed. I have pinged the discourse thread. Let's see if we can get it to move forward. (cc @CAM-Gerlach)
It's here :blush: https://discuss.python.org/t/pep-639-round-2-improving-license-clarity-with-better-package-metadata
The issue is that AFAIK there's no way to do this without custom code on Windows. To install the libraries inside the module, I think you can pass `install: false`...
> And it's actually `meson-python` that cleans things up; `pip`'s `--no-clean` works as advertised for the build env itself. We should consider this a bug, I think. There's no reason...
> > They then went all-in and declared that they were removing support for interacting with setuptools via a command line. > > I completely agree that that's a mistake...
> `importlib.machinery.EXTENSION_SUFFIXES` here is only as a safety check. We can remove it. But I would be very surprised if there are no other things that break. I think the...
That issue has already been discussed at length in the proper places, so I am not gonna repeat that discussion here. Your proposal had nothing to do with avoiding the...
As a reply to me saying that direct `setup.py` invocations were deprecated for good reasons, you said you didn't think so and then mentioned your proposal, so I read it...
I converted the PR to draft while we wait for a resolution in #29, so that the state of PR log is easier to understand. @dnicolodi I hope that is...