| #!/usr/bin/python | |
| import os | |
| import sys | |
| import csv | |
| import urllib | |
| try: | |
| filename = sys.argv[1] | |
| url_name = sys.argv[2] |
Imagine you're a bitcoin miner. You have a huge power bill, you have your capital that is depreciating like a glass of milk in the sunshine, but as long as the price per bitcoin is high and the local government isn't driving you out of the country, things are pretty good. I mean, figuratively speaking, you're printing money.
But think about this for a minute. It's not as if the bitcoin network would work any worse if you and 99% of the mining capacity would turn
| #!/bin/bash | |
| # sudo apt-get install xml-twig-tools | |
| _source="$HOME/.local/share/gnote" | |
| _dest="$HOME/gnote_export/" | |
| rm -rf "$_dest" | |
| mkdir -p "$_dest" | |
| #_file="simple_desktop_creator.desktop" | |
| #_focus=$_dest$_file |
| #!/usr/bin/env python3 | |
| """A sublime-text build script, to do the right thing?. | |
| This script takes the currently open file as a | |
| reference point and uses it to determine which commands | |
| to run. This means that you don't have to select a build | |
| commands when switching between projects, the fact that | |
| you have a different file open is enough to indicate | |
| which build you want to run. |
| # -*- coding: utf-8 -*- | |
| """Store simple data between multiple executions of a script. | |
| Python2.6+, no external dependencies. | |
| A simple class to store small amounts data between | |
| multiple executions of a script (for one-off scripts). | |
| Copyright: Manuel Barkhau 2020 Dedicated to the public domain. | |
| CC0: https://creativecommons.org/publicdomain/zero/1.0/ |
| #!/bin/bash | |
| set -e; | |
| # change this | |
| PROJECT_NAME=bidict | |
| CONDA_ROOT=$HOME/miniconda3 | |
| CONDA_BIN=${CONDA_ROOT}/bin/conda | |
| PLATFORM=$(uname -s) |
| https://www.youtube.com/watch?v=EQs5VxNPhzk | |
| 0:22 Arch 34 - Kaiserstrasse, after of station "Bruch" - 51.2342321,7.0766762 - https://youtu.be/DgfRq4kEFro?t=175 | |
| The building at the left of Arch 41, before the bend onto Göthestraße is still standing | |
| 1:04: Arch 47 - Before the bend, looking up to either "Hammerstein" or the north end of "Schrödersbusch". | |
| I don't recognize the house on the hill anywhere today. | |
| 1:17: Arch 96 - After station "Sonneborner Straße" - 51.2385451,7.1009054 - https://youtu.be/DgfRq4kEFro?t=365 | |
| To the right, the three buildings on the are still standing. |
| #!/bin/bash | |
| set -e; | |
| REPOUSER=mbarkhau | |
| mkdir -p $HOME/workspace | |
| cd $HOME/workspace | |
| if ! [[ -d fast-export ]]; then |
I have often read the error message in a stacktrace and then reread it after I realized I was reading the code to produce the error message, rather than the error message itself. Often this will not matter, but if you are using a format string to produce the error message, I recommend putting the string generation on a separate line to the raise of the exception.
Variation 1, we have two lines with the error message/reason string, but only the last line one of them has the expanded format string (it includes 1234567890 which presumably is important).
$ python3 ../exception_format_string.py 1
Traceback (most recent call last):
File "../exception_format_string_demo.py", line 6, in <module>
raise Exception(f"My error message with formatting: '{arg}'")
Exception: My error message with formatting: '1234567890'
| """Context manager for coarse grained performance measurement. | |
| Usage: | |
| with trace("section title"): | |
| your_code_here() | |
| Output: | |
| ts: 0.104 ┌ section title | |
| ts: 123.410 └ d: 123.000 ms |