Filipe Laíns 🇵🇸
Filipe Laíns 🇵🇸
The main issue seems to be Windows runs with coverage, the others are fine IMO, they can range from more or less the same duration to a bit slower, but...
> We can add concurrently groups and auto cancel if you'd like. I was meaning to do this. I think it would be a good first step, and we can...
I think the following would also have caught it. ```ini [coverage:run] branch = true ``` I will add this to my TODO, we should enable branch coverage and add the...
Sorry for the short reply, it is late and I am on my phone. I am remodeling at home, so my setup will be dismantled until Wednesday, I should still...
Sorry for the delay. I will clarify my comment. I think this is a valid use case, though necessary, so I am okay with supporting it as long as we...
Getting back to this, I think allowing `--python` to receive a list may introduce some complexity. So, I'd like to understand the use-case where it would be wanted/needed. If there...
This is out of scope IMO. This package aims to be simple, as it is crucial for bootstraping Python environments, so I'd like to avoid bringing much complexity into it....
> The idea here is to avoid using constraints as requirements, because they are not that, though. I think I don't really understand this comment. Could you clarify?
Sorry, we are not required to. If we stay with pep517, we will have to at least ditch their runners and implement a custom runner that calls our own runner...
No, we need to change the runner API as the one in `pep517` does not let us set the environment, only update it.