| states = [ 'AK', 'AL', 'AR', 'AZ', 'CA', 'CO', 'CT', 'DC', 'DE', 'FL', 'GA', | |
| 'HI', 'IA', 'ID', 'IL', 'IN', 'KS', 'KY', 'LA', 'MA', 'MD', 'ME', | |
| 'MI', 'MN', 'MO', 'MS', 'MT', 'NC', 'ND', 'NE', 'NH', 'NJ', 'NM', | |
| 'NV', 'NY', 'OH', 'OK', 'OR', 'PA', 'RI', 'SC', 'SD', 'TN', 'TX', | |
| 'UT', 'VA', 'VT', 'WA', 'WI', 'WV', 'WY'] | |
| states = { | |
| 'AK': 'Alaska', | |
| 'AL': 'Alabama', | |
| 'AR': 'Arkansas', |
| from sqlalchemy import Column, Integer, String, ForeignKey, create_engine | |
| from sqlalchemy.ext.declarative import declarative_base | |
| from sqlalchemy.orm import relationship, backref, sessionmaker, joinedload | |
| # For this example we will use an in-memory sqlite DB. | |
| # Let's also configure it to echo everything it does to the screen. | |
| engine = create_engine('sqlite:///:memory:', echo=True) | |
| # The base class which our objects will be defined on. | |
| Base = declarative_base() |
| var countries = { | |
| ae: 'United Arab Emirates', | |
| ag: 'Antigua and Barbuda', | |
| ai: 'Anguilla', | |
| al: 'Albania', | |
| am: 'Armenia', | |
| ao: 'Angola', | |
| ar: 'Argentina', | |
| at: 'Austria', | |
| au: 'Australia', |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| import boto3 | |
| from termcolor import colored | |
| ec2 = boto3.resource('ec2') | |
| for i in ec2.instances.all(): | |
| print("Id: {0}\tState: {1}\tLaunched: {2}\tRoot Device Name: {3}".format( | |
| colored(i.id, 'cyan'), | |
| colored(i.state['Name'], 'green'), |
| # This is something that I always forget and had a surprisingly hard time finding (or better yet, understanding). Here's the | |
| # scenario: a colleague creates a new kubernetes cluster, named" cluster-foo.example.com". You want to look at it (for | |
| # troubleshooting, updating the deployment, whatever). To get your kubectl installation to "see" the new cluster, take the | |
| # following steps: | |
| # ASSUMPTION: You have pointed kops to some location where the cluster configurations are stored | |
| # (I have this in my ~/.bash_profile): | |
| export KOPS_STATE_STORE=s3://example-state-store | |
| # Use kops to get the list of clusters |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
Based off of: http://docs.sequelizejs.com/en/1.7.0/articles/express/
Create and initialize your a directory for your Express application.
$ mkdir sequelize-demo
| from btgym import BTgymEnv | |
| import IPython.display as Display | |
| import PIL.Image as Image | |
| from gym import spaces | |
| import gym | |
| import numpy as np | |
| import random |
| // 🔥 Node 7.6 has async/await! Here is a quick run down on how async/await works | |
| const axios = require('axios'); // promised based requests - like fetch() | |
| function getCoffee() { | |
| return new Promise(resolve => { | |
| setTimeout(() => resolve('☕'), 2000); // it takes 2 seconds to make coffee | |
| }); | |
| } |