tjnel

import re
import time

import requests
import logging as logme

class TokenExpiryException(Exception):
    def __init__(self, msg):
        super().__init__(msg)

tjnel

echo "testing"

tjnel

tjnel

import re


def line2csv(line):
    print(line)
    a = re.compile(r"([0-9]{2}\/[0-9]{2}\/20[0-9]{2})-([0-9]+\:[0-9]+\:[0-9]+\.[0-9]+)\s+\[\*\*\]\s+\[([0-9]+)\:(["
                   r"0-9]+)\:([0-9]+)\]\s+(.*)\[\*\*\]\s+\[Classification\:\s+([aA-zZ 0-9]+)\]\s+\[Priority\:\s+(["
                   r"0-9]+)\]\s+\{([aA-zZ 0-9]+)\}\s+(.*)\s+->\s(.*)")
    results = a.match(line)
    return results.groups(0)

tjnel

Keybase proof

I hereby claim:

• I am tjnel on github.
• I am idr0p (https://keybase.io/idr0p) on keybase.
• I have a public key whose fingerprint is 7FDE E36A 4A4D EEAF 917F AD45 F769 1246 5675 20E7

To claim this, I am signing this object:

tjnel

There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

tjnel

print("Hello")

tjnel

import requests
from bs4 import BeautifulSoup
r = requests.get("http://www.coindesk.com/price/")
soup = BeautifulSoup(r.text, "lxml")
latest = soup.find("div", class_='bpi-value bpiUSD').text
print(latest)