$ cat t.py
from pprint import pprint
from pytheory import Tone, Fretboard, charts_for_fretboard
tones = (
Tone.from_string("F2"),
Tone.from_string("C3"),
Tone.from_string("G3"),
Tone.from_string("D4"),
$ cat t.py
from pprint import pprint
from pytheory import Tone, Fretboard, charts_for_fretboard
tones = (
Tone.from_string("F2"),
Tone.from_string("C3"),
Tone.from_string("G3"),
Tone.from_string("D4"),
proxy_cache_path /tmp/cacheapi levels=1:2 keys_zone=microcacheapi:100m max_size=1g inactive=1d use_temp_path=off; | |
server { | |
listen 443 ssl http2 default_server; | |
listen [::]:443 ssl http2 default_server; | |
server_name example.com; | |
location /api/ { | |
# Rate Limiting | |
limit_req zone=reqlimit burst=20; # Max burst of request |
import datetime | |
from functools import wraps | |
from werkzeug.security import ( | |
generate_password_hash, | |
check_password_hash | |
) | |
from flask import abort |
import os | |
import time | |
''' | |
mongo backup by python | |
developrt: mr-exception | |
github: mr-exception | |
''' | |
# configs: |
While I'm learning how to use Nginx, I was instructed to update the server_names_hash_bucket_size
(/etc/nginx/nginx.conf
) value from 32 to 64, but I don't understand why should I increase the value to 64.
References that have been read so far:
package main | |
import "crypto/tls" | |
import "crypto/sha1" | |
import "crypto/x509" | |
import "fmt" | |
import "encoding/pem" | |
import "os" | |
import "time" | |
import "bufio" |
Now located at https://github.com/JeffPaine/beautiful_idiomatic_python.
Github gists don't support Pull Requests or any notifications, which made it impossible for me to maintain this (surprisingly popular) gist with fixes, respond to comments and so on. In the interest of maintaining the quality of this resource for others, I've moved it to a proper repo. Cheers!
These are snippets of py.test in action, used in a talk given at | |
PyCon AU 2012 in Hobart, Tasmania. They are all relevant for | |
py.test 2.2 except where specified. Where taken from open source | |
projects I have listed a URL, some examples are from the py.test | |
documentation, some are from my workplace. | |
Apart from things called test_*, these functions should probably | |
be in your conftest.py, although they can generally start life in | |
your test files. |