Installation process

[chillum]

Hi,

Having a CLI interface to read logs is a very nice thing.

But I think, the installation process is a bit b0rked.

Now we have: I have to clone the repo and start the script from it.

What would I expect: a pip package, installable in venv or system-wide.

I hope, that makes sense.

[steve-scalyr]

Thanks for the suggestion. We'll look into putting together a pip package
as well.

On Wed, Apr 29, 2015 at 1:36 AM, Vasily Korytov [email protected]
wrote:

Hi,

Having a CLI interface to read logs is a very nice thing.

But I think, the installation process is a bit b0rked.

Now we have: I have to clone the repo and start the script from it.

What would I expect: a pip package, installable in venv or system-wide.

I hope, that makes sense.

—
Reply to this email directly or view it on GitHub
#1.

[ArbiterOfBuffoonery]

Adding to this, on Ubuntu 22.04, it seems #!/usr/bin/env python doesn't work. If I run the script as is, I get the message

/usr/bin/env: ‘python’: No such file or directory

However, if I change the shebang to #!/usr/bin/env python3 it works. I think this would be resolved if it was installed via pip, but I'm not 100% sure since I don't do a ton of dev in python.

[JohnRoesler]

I second @ArbiterOfBuffoonery 's comment. The script should be able to handle different environments where env python may not be available.

[Integralist]

👋🏻

I have arrived from the future to say...

env: python: No such file or directory

I don't have python but I do have python3 😬

Tip

Replace <PATH_TO>...
sudo sed -i '' 's|#!/usr/bin/env python|#!/usr/bin/env python3|' <PATH_TO>/scalyr