You should read the Typer Tutorial - User Guide before referring to this summary. Information icons ℹ️ link to the relevant sections of the Typer Tutorial.
- Documentation: https://typer.tiangolo.com
- Source Code: https://github.com/tiangolo/typer
""" | |
Testing on CPython3.13a1+ | |
Requires some recent patches from main. | |
pip install hypercorn | |
Have successfully run the following apps: | |
- fastapi==0.99.0 | |
- Flask | |
""" |
You should read the Typer Tutorial - User Guide before referring to this summary. Information icons ℹ️ link to the relevant sections of the Typer Tutorial.
The gist includes exercises for the "Mastering Multi-Region Deployments With YugabyteDB" workshop. Attend the summit and follow the steps below to get a practical experience.
# search replace AWS_ACCOUNT_ID with your AWS account ID and adjust the variables below (line 3-7), especially your API key | |
# if your flow needs access to other AWS resources other than S3, add those in the task role policy: line 96-108 | |
export AWS_REGION=us-east-1 | |
export ECS_CLUSTER_NAME=prefectEcsCluster | |
export ECS_LOG_GROUP_NAME=/ecs/prefectEcsAgent | |
export ECS_SERVICE_NAME=prefectECSAgent | |
export PREFECT_API_KEY=your_Prefect_Cloud_API_key | |
export AWS_PAGER="" | |
aws ssm put-parameter --type SecureString --name PREFECT__CLOUD__API_KEY --value $PREFECT_API_KEY --region $AWS_REGION --overwrite |
git_current_branch () { | |
local ref | |
ref=$(command git symbolic-ref --quiet HEAD 2> /dev/null) | |
local ret=$? | |
if [[ $ret != 0 ]] | |
then | |
[[ $ret == 128 ]] && return | |
ref=$(command git rev-parse --short HEAD 2> /dev/null) || return | |
fi | |
echo ${ref#refs/heads/} |
If you're a privacy enthusiast, you probably clicked a link to this post thinking it's going to vindicate you; that it's going to prove how you've been right all along, and "normies just don't care about privacy", despite your best efforts to make them care. That it's going to show how you're smarter, because you understand the threats to privacy and how to fight them.
Unfortunately, you're not right. You never were. Let's talk about why, and what you should do next.
So, first of all, let's dispense with the "normie" term. It's a pejorative term, a name to call someone when they don't have your exact set of skills and interests, a term to use when you want to imply that someone is clueless or otherwise below you. There's no good reason to use it, and it suggests that you're looking down on them. Just call them "people", like everybody else and like yourself - you don't need to turn them into a group of "others" to begin with.
Why does that matter? Well, would *y
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.
import tempfile | |
import prefect | |
from prefect.storage import S3 | |
from prefect import task, Flow, Parameter | |
from prefect.engine.serializers import Serializer | |
from prefect.engine.results import S3Result | |
from yellowbrick.datasets import load_mushroom | |
from sklearn.pipeline import Pipeline |
from prefect.environments.storage import S3 | |
from prefect.environments import FargateTaskEnvironment | |
from prefect.engine.executors import DaskExecutor, LocalDaskExecutor | |
from prefect import task, Flow, Parameter | |
import prefect | |
STORAGE = S3(bucket="demo-prefect-flows-14") | |
ENVIRONMENT = FargateTaskEnvironment( | |
networkMode="awsvpc", |