1325a7ab15
In various roles I maintain I use `python3 -m pip install` to directly install a Python project (usually a fedora-messaging consumer), to avoid the pointless bureaucracy of packaging them. The roles install all the deps of these projects as packages first, so pip doesn't have to install any deps, it only installs the project itself. Well...that's the idea. It's possible for this to go wrong (say I forget to update the roles when adding a dep to the project), and in that case I think we'd rather have things blow up (so I know something's wrong) than have pip silently install some random upstream wheel system-wide to make it work. The intent is that all the deps still come from proper Fedora packages, only these projects themselves get installed directly. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
|---|---|---|
| .. | ||
| defaults | ||
| handlers | ||
| tasks | ||
| templates | ||