Miloš Prchlík

> @happz, seems that [unit tests](https://artifacts.dev.testing-farm.io/08109778-d78c-4d80-a925-2c63ff26e531/) will need some adjustments as well: > > ``` > > assert interpreted.note is None > E AssertionError: assert [] is None > ```...

> > Hopefully addressed in [f705e9e](https://github.com/teemtee/tmt/commit/f705e9eebc7829208426d9c90657f8e71a528736). > > Great, thanks! Tests are now green. > > I see three checklist items missing and I'd say they all make sense. What...

We can definitely add an "uninstall" action to package managers, but how to express "package python3-foo shall be uninstalled". We have `require` for "shall be present" and `recommend` for "may...

Ok, so if the idea is to implement this for the `prepare/install` plugin first, then it shouldn't be too hard. We already have a precedent for not-just-a-string "packages", test `require`...

That was a price for the "all playbooks must be under fmf tree root" rule which has been relaxed a bit recently. I suppose `prepare/ansible` should use its workdir, correct?...

> What do you think about putting these into a package `tmt.containers`... +1 to `tmt.containers`. I have it somewhere in my stash, I tried something similar: move basic classes and...

> Cool, I've moved the stuff around, I think after this the only things left to move would be `Common` and the Exceptions? Otherwise everything else would still be under...

> > `__future__.annotations` sounds good, I'm much less fond of stub files, it always felt detached from the code & two places that need to be updated when changing signatures....

> > > I was thinking stub files as additive to keep things cleaner from parts like `@overload`, but indeed I can see it can easily get out-of-sync. There is...

Adding this one to 1.38, let's see whether it can be done as a whole.