mivade

"""A simple demonstration of running background tasks with Tornado.

Here I am using a basic TCP server which handles streams and keeps
them open while asynchronously performing a fake task in the
background. In order to test it, simply telnet to localhost port 8080
and start typing things to see that the server receives the messages.

The advantage to running on an executor instead of conventional
threads is that we can more easily shut it down by stopping the
tornado IO loop.

sphvn

var traverse = function(o, fn) {
  for (var i in o) {
    fn.apply(this,[i,o[i]]);  
    if (o[i] !== null && typeof(o[i])=="object") {
      traverse(o[i], fn);
    }
  }
}

// usage

evi1m0

#!/usr/bin/env python
# coding=utf8
# author=evi1m0
# website=linux.im

'''
    12306 Captcha Picture:
    author: Evi1m0@20150316
        1. Download Captcha
        2. Pic Conver Text

powerman

Asciidoc cheatsheet for GitHub

wen-long

#!/bin/sh
qqwry_dat_url="http://update.cz88.net/soft/setup.zip";
qqwry_dat_local_path="/usr/local/share/QQWry.Dat"
curl=`which curl`
wget=`which wget`


workdir="/tmp/QQWry/"
zipname="QQWry.setup.zip"

binderclip

import smtplib
from getpass import getpass

def prompt(prompt):
    return input(prompt).strip()

fromaddr = prompt("From: ")
toaddrs  = prompt("To: ").split()
subject  = prompt("Subject: ")
print("Enter message, end with ^D (Unix) or ^Z (Windows):")

JJediny

There are two types of markup in Liquid: Output and Tag.

• Output markup (which may resolve to text) is surrounded by

{{ matched pairs of curly brackets (ie, braces) }}

• Tag markup (which cannot resolve to text) is surrounded by

jvmsangkal

class ConnectionPool():
    """
    Usage:
        conn_pool = nmi_mysql.ConnectionPool(config)

        db = conn_pool.get_connection()
        db.query('SELECT 1', [])
        conn_pool.return_connection(db)

        conn_pool.close()

toolness

Adventures in Python Core Dumping

After watching Bryan Cantrill's presentation on [Running Aground: Debugging Docker in Production][aground] I got all excited (and strangely nostalgic) about the possibility of core-dumping server-side Python apps whenever they go awry. This would theoretically allow me to fully inspect the state of the program at the point it exploded, rather than relying solely on the information of a stack trace.

mondain

23.21.150.121:3478
iphone-stun.strato-iphone.de:3478
numb.viagenie.ca:3478
s1.taraba.net:3478
s2.taraba.net:3478
stun.12connect.com:3478
stun.12voip.com:3478
stun.1und1.de:3478
stun.2talk.co.nz:3478
stun.2talk.com:3478