It's a shame there's no library for handling modulemd files, or is there?

I would suggest curling latest modulemd from upstream: https://pagure.io/modulemd/blob/master/f/spec.yaml

Please use modulemd library as @contyk mentioned in the comment. https://pagure.io/modulemd/blob/master/f/modulemd

base-runtime is already built, we don't need fakes anymore. Let's get it from real data (e.g. base-runtime's and shared-userspace's API)

subprocess.check_output does exactly this, pretty much

• tights to yum
• using repoquery probably not best idea for such things

I would also appreciate a subcommand, which would get all build dependencies of an RPM a reported which of them are available in some modules and which are not.

use RPM bindings.

most useless description ;)

sounds weird. most probably should be /usr/bin/env python

not python3 compatible

f25 should not be hardcoded

actually, this file should not have shebang as it doesn't have __main__

Response from @psabata how to get info of which rpms are provided by base-runtime:

11:36 <contyk> ttomecek: yes, it's the API -- it's available in three places ;)
11:37 <contyk> ttomecek: 1) in the module itself, 2) in the base-runtime github repo in two forms -- api.txt, a simple machine-readable list and in README.md with comments
11:37 <contyk> ttomecek: I would suggest the info in modulemd
11:38 <contyk> and the README file if you're curious about a specific component and why it is or isn't included

Also as @ignatenkobrain commented wrt urllib3 -- I would suggest usingrequests, no need to use the plumbing library.

What about if file does not exist? It finishes with traceback, isn't it? Can it be handled via try and catch?

What about if file does not exist? It finishes with traceback, isn't it? Can it be handled via try and catch?