| from multiprocessing import Pool | |
| def pmap(f, collection, size=10): | |
| """ | |
| Applies `f` in parallel over `collection`. | |
| Pool `size` has a sensible default of 10. | |
| """ | |
| with Pool(size) as p: | |
| return p.map(f, collection) |
| #!/usr/bin/blaze pex flask flask-restful -- | |
| import shelve | |
| from flask import Flask, request | |
| from flask_restful import Resource, Api | |
| app = Flask(__name__) | |
| api = Api(app) | |
| with shelve.open('ministore.db') as db: |
#! blaze sh
One of the problems with tech documentation (api, installation instructions etc) is that they get stale. APIs change, software and plugins alter their interface and commands, and websites go away.
To solve this, I propose we write our documentation in a way that can be executed, or verified.
Luckily, I wrote blaze to execute codeblocks inside of markdown, which means that with a little help from a few common unix tools, we can solve this problem.
| (defn tester [x] | |
| {:pre [(is (even? x))]} | |
| x) |
| #!/usr/bin/env sh | |
| requirements=$1 | |
| script=$2 | |
| exec pex $requirements -- $script |
| (import [multiprocessing.pool [ThreadPool]]) | |
| (defmacro future [code] | |
| (def t (gensym)) | |
| (def pool (ThreadPool :processes 1)) | |
| `(do | |
| (def ~t (pool.apply-async (fn [] ~code))) | |
| ~t)) |
| <html> | |
| <head> | |
| <script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/vis/4.20.0/vis.min.js"></script> | |
| <link href="https://cdnjs.cloudflare.com/ajax/libs/vis/4.20.0/vis.min.css" rel="stylesheet" type="text/css" /> | |
| <style type="text/css"> | |
| #mynetwork { | |
| width: 600px; | |
| height: 400px; | |
| border: 1px solid lightgray; |
| (defn return_after_5_secs [message] | |
| (do (Thread/sleep 5000) message)) | |
| future = (future return_after_5_secs “hello”) | |
| (realized? future) | |
| (Thread/sleep 5000) | |
| (realized? future) | |
| (println @future) |