Miloš Prchlík
Miloš Prchlík
> > Ah, wait, after think twice, maybe we should let custom config surpass the default one in mrack.py, > > Yeah, this sounds reasonable to me: To allow users...
> > Just to clarify the motivation: So users will be able to configure (and maintain) their own hardware translation rules? > > yep > > > Do we expect...
> Thanks for the detailed clarification. I've shortly tested with `gpu.driver` and it seems to be working: > > This config: > > ```yaml > beaker: > translations: > -...
> But the more I think about it, what are the purpose of using `ModuleImporter` over just `try import` in each relevant module? Mostly my dislike of constructs like https://github.com/teemtee/tmt/blob/main/tmt/steps/provision/testcloud.py#L42,...
/packit test
> Why the dependency? `mrack` fails to import without `pkg_resources`. But as I read it now, I mistook `pkg_resources` for something else, tmt does not depend on it.
Sounds like a good idea. There can be different levels, though: accepting shortened options, accepting shortened commands, supporting user-defined command aliases, and providing hints on mistyped commands and options ("did...
Let's investigate! See the third point, check for possible alternatives too. Possible issues: 1. `requre` stores possibly a lot of data, Polarion tests are kept in a separate repository; 2....
> > LGTM. My only comment is that the `normalize_*` should be generalized to reduce duplication, but that's for a different PR. > > haha, Milos has the same concern,...
@skycastlelily a test, even a small one, and a release note would be nice.