-
In
~/.ssh/config
, include the lines:Host * ControlPath ~/.ssh/sockets/%r@%h-%p
import time | |
from http.server import BaseHTTPRequestHandler, HTTPServer | |
HOST_NAME = 'localhost' | |
PORT_NUMBER = 9000 | |
class MyHandler(BaseHTTPRequestHandler): | |
def do_HEAD(self): | |
self.send_response(200) |
""" | |
Minimal character-level Vanilla RNN model. Written by Andrej Karpathy (@karpathy) | |
BSD License | |
""" | |
import numpy as np | |
# data I/O | |
data = open('input.txt', 'r').read() # should be simple plain text file | |
chars = list(set(data)) | |
data_size, vocab_size = len(data), len(chars) |
<html> | |
<head> | |
<title>Hello River</title> | |
<!-- | |
The Hello World of Rivers | |
https://github.com/scripting/river5/blob/master/docs/HELLOWORLD.md | |
--> |
You might want to read this to get an introduction to armel vs armhf.
If the below is too much, you can try Ubuntu-ARMv7-Qemu but note it contains non-free blobs.
First, cross-compile user programs with GCC-ARM toolchain. Then install qemu-arm-static
so that you can run ARM executables directly on linux
assets | |
business | |
accounts receivable | |
bank | |
personal | |
accounts receivable | |
bank | |
cash | |
gifts | |
online |
#!/usr/bin/env bash | |
# | |
# This is sp, the command-line Spotify controller. It talks to a running | |
# instance of the Spotify Linux client over dbus, providing an interface not | |
# unlike mpc. | |
# | |
# Put differently, it allows you to control Spotify without leaving the comfort | |
# of your command line, and without a custom client or Premium subscription. | |
# |
from __future__ import print_function | |
from ofxparse import OfxParser | |
import os | |
import re | |
import sys | |
if len(sys.argv) != 1: | |
print ('This utility does not take command-line arguments') | |
exit() |
# This file defines a decorator '@log_to()' that logs every call to a | |
# function, along with the arguments that function was called with. It | |
# takes a logging function, which is any function that accepts a | |
# string and does something with it. A good choice is the debug | |
# function from the logging module. A second decorator '@logdebug' is | |
# provided that uses 'logging.debug' as the logger. | |
from __future__ import print_function | |
from functools import wraps | |
from inspect import getcallargs, getargspec |