Stop doing `sudo pip install`

[dtantsur]

It's a well known no-go. Currently it replaces PyYAML with a much newer (3.* to 5.*) version, which has potential of breaking installed packages. We should either use virtualenv or pip install --user.

[hardys]

We could just install yq with go get seeing as we're already installing various go things for development https://mikefarah.github.io/yq/

Not sure about lolcat though, clearly we'll have to find a solution for that :D

[hardys]

Ok so short term we can go get yq, and install ruby from RPM then gem install lolcat.

Fairly soon the yq should be unnecessary though when we move the manifest/asset templating out of dev-scripts, ref #561

[dtantsur]

May I dare ask if we really need lolcat so much? :)

[russellb]

heh, +1 to remove lolcat if it helps clean up our dependencies.

[hardys]

Ok lolcat removed via #594, I'll push a pr that switches yq to go get later.

[hardys]

Ok just to follow up, that go based yq is yq.v2 which isn't the same as the python tool we're using, which is just a wrapper for jq (the go one doesn't support the filtering features we need).

https://github.com/kislyuk/yq is the one we need, and even installing from source you need to do pip install . so the setuptools stuff will do the build/install, so I'd say lets leave this until the manifest stuff gets removed (hopefully soon)

[hardys]

This will be closed via #561 so lets close this and track removing the short-term hacks that need yq there.

[dtantsur]

We could do pip install --user..

[hardys]

We could do pip install --user..

Yeah, Ok reopened so feel free to push a PR if you'd like to go that way - I was just thinking pretty soon this will go away so it's probably not a priority.

[russellb]

There's no pip calls in dev-scripts anymore