Comment 2 for bug 1472986

My reply to that...

The list above is what I want as a final result from *my* tooling. But of course, I do not expect pbr to produce that directly. I just wish it made some kind of output that I could easily transform into the above. I can be what's in the *.egg-info/requires.txt, that's fine, as long as it doesn't actually write any file.

It doesn't have to be done through "python setup.py", it could be a pbr command line thing.

What's important here, is that I get a way to extract the information from setup.cfg, if it moves there. Just something that would do that from pbr could be enough, then I'll do the rest using my ugly (but useful and not for production) shell scripts! :)