xonsh is a Python-powered, cross-platform, Unix-gazing shell language and command prompt
ENV_VAR=value python script.py
You can run things through the env command: env ENV_VAR=value python script.py
so, the way to configure cloud/serverless stuff is tooling like Teraform or Pulumi (or helm, if you have an existing kubernetes cluster). It's fairly straight-forward to set CD pipelines with those, with some fixed branches for different environments.
However, your concern with our service-based tooling in the past has been how easily people can contribute to it, and simply using AWS/GCP has a significant learning curve (in ways that Terafrom/pulumi can only sort of cover up). Using heroku means we just throw up a flask app and all the operational aspects are handled.
The flip side is cost: AWS/GCP have a lot more "pay what you use" options, which tend to be cheaper if you don't need stuff running all the time but more expensive if you do. (Our use case most likely falls into the former.) Heroku, meanwhile, would need to have a constant cost to keep the service running all the time (albeit a small one, like $10/mo). Footnote: Heroku hobby is free, but can spin-down. I would have to test if that means "requests will be rejected" or "the initial request will just take a long time".
refresh_interval in prompt_toolkit (https://github.com/prompt-toolkit/python-prompt-toolkit/blob/c7851c09ffbfa7d06458408abee77ab6f548852d/examples/prompts/clock-input.py ) and it works fine, not sure what is going on..
Hi, I am begginer of xonsh.
I read Tutorial: Subprocess Strings but I cannot understand how to unquote an embedded string.
https://xon.sh/tutorial_subproc_strings.html
In bash:
OPTIONS=""
if [[ some_condition ]]; then
OPTIONS="$OPTIONS -c optional_key=$VALUE"
fi
awesome_command \
-c key1=value1 \
-c key2=value2 \
$OPTIONSIn xonsh(wrong):
$OPTIONS = ""
if some_condition:
$OPTIONS = f"{$OPTIONS} -c optional_key={$VALUE}"
awesome_command \
-c key1=value1 \
-c key2=value2 \
$OPTIONS # $OPTIONS treated as one quoted string
I'm enjoying Xonsh, but having a lot of difficulty with command substitution. The following is something I do in bash a lot - could you show me what the Xonsh equivalent is?
grep -Ri foo $(find . -iname "*.py")
From the docs, I thought it would be grep -Ri foo @$(find . -iname "*.py"), but that clearly doesn't work the way I think it does.
@$(find . -iname "*.py") should be the same as @([i.strip() for i in $(find . -iname "*.py").split()]). Unless I'm missing something?Any how, you can explicitly pass in the list of files
grep -i foo @($(find . -iname "*.py").split())
