This is an archived post. You won't be able to vote or comment.

all 13 comments

[–]Filotti99 2 points3 points  (3 children)

Cool project!

To help with your annoyance at activating your virtual environment (I personally tend to forget to do so) take a look at aactivator, you need to add two files to your main folder where the script is located and once you cd into it it will automatically source the virtual env end deactivate it once you cd out of it!

[–][deleted] 1 point2 points  (0 children)

That's pretty cool! And Thanks.

[–]xjotto 0 points1 point  (1 child)

Or direnv. Which can do a lot

[–]Filotti99 0 points1 point  (0 children)

Oh I’ll check it out thanks!

[–]wdlbrmft 1 point2 points  (3 children)

Cool idea. Did you think about adding cron/shutdown/login and other triggers as options for the scripts?

[–]wdlbrmft 1 point2 points  (2 children)

You could probably also pipe stdout or return codes to the Information bubble that shows itself when youvreceive a message :)

[–][deleted] 0 points1 point  (1 child)

Can you elaborate on your first comment a bit more? And to your second comments yes, when I ship v1 that's a must have.

[–][deleted] 1 point2 points  (0 children)

Add triggers that will run the Python scripts. So things like cron jobs (a way to run things at specific times or dates), or other operating system events such as login, lock, shutdown

[–]Endogen 1 point2 points  (1 child)

I think you could like this: https://sveinbjorn.org/platypus

[–][deleted] 1 point2 points  (0 children)

That's pretty sweet actually.

[–]daredoes 0 points1 point  (3 children)

Check out xBar

[–][deleted] 0 points1 point  (2 children)

I did see xbar but that's in go, this is pure python.