alexcasalboni

How to use Python3 Type Hints in AWS Lambda

TL;DR

Static Type Checkers help you find simple (but subtle) bugs in your Python code. Check out lambda_types.py and incrementally improve your code base and development/debugging experience with type hints.

Your Lambda Function code will go from this:

abresler

# load_packages -----------------------------------------------------------

packages <-
  c('nbastatR', #devtools::install_github("abresler/nbastatR")
    'explodingboxplotR', #devtools::install_github("timelyportfolio/explodingboxplotR")
    'ggplot2',
    'dplyr',
    'purrr',
    'magrittr')

lmarkus

Extracting Emoji From Slack!

Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.

If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3

HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.

Follow along...

gene1wood

LambdaContext

Here is the raw output from examining the Python LambdaContext context object in a AWS Lambda function when called from a CloudFormation stack. More information on the context object can be found here : http://docs.aws.amazon.com/lambda/latest/dg/python-context-object.html

LambdaContext object : print(context)

<__main__.LambdaContext object at 0x7fd706780710>

LambdaContext vars : vars(context)

gluc

library(shiny)
library(shinyjs)



# Get table metadata. For now, just the fields
# Further development: also define field types
# and create inputs generically
GetTableMetadata <- function() {
  fields <- c(id = "Id", 

paulsmith

from __future__ import print_function

from collections import namedtuple
import csv
import sys
import time
from urllib import urlopen

from bs4 import BeautifulSoup

yihui

---
title: HTML Dependencies
output: html_document
---

This example explains how HTML dependencies work in **htmltools**. Sometimes an HTML fragment may have additional dependencies to work correctly, such as JavaScript and/or CSS files. In R Markdown documents, you have to let **rmarkdown** know these dependencies, so they can be added to the HTML header when the document is rendered through Pandoc.

Another thing that you need to pay attention is you have to "protect" your HTML output so that Pandoc does not touch it, e.g. when you have four leading spaces, Pandoc may think this line is supposed to be a `<pre>` block whereas you only meant to indent the line for cosmetic purposes. In this case, the function `htmltools::htmlPreserve()` will be _automatically_ applied to your HTML content in R Markdown if the content is generated from `htmltools::tags` or wrapped in `htmltools::HTML()`.

Now we use a random CSS file in the **knitr** package to illustrate how dependencies work. The goal here is to generate a 

rich-iannone

# install.packages("downloader")
# devtools::install_github("rich-iannone/DiagrammeR")
# devtools::install_github("jeroenooms/V8")

library("downloader")
library("DiagrammeR")
library("V8")

# Create a function that uses the 'chromatography' JS library to generate a random
# set of colors from the CIE Lab color space 

datalove

identical          <- function(x) UseMethod("identical") 
identical.my_class <- function(x) do_something(x)
identical.default  <- base::identical

bayesball

# loading in Retrosheet data for the seasons 1960 through 2013 from my website 
load(url("http://bayes.bgsu.edu/baseball/pbp.1960.1979.Rdata"))
load(url("http://bayes.bgsu.edu/baseball/pbp.1980.1999.Rdata"))
load(url("http://bayes.bgsu.edu/baseball/pbp.2000.2013.Rdata"))

batter.matchup.ggplot <- function(Name, graph=TRUE, retroid=FALSE){
  # this function assumes the data frames pbp.60.79, pbp.80.99, and pbp.00.13 are
  # in the workspace
  fit.model <- function(y, n){
    require(LearnBayes)