Jeremy McMillan aphor

Exporting a Networkx graph as a Cypher query

This little project defines a function that can be used to construct a Cypher query which when executed against a Neo4j database server will store the graph to the server.

Background

A Graph is an abstract mathematical model composed of Nodes connected through Edges that can be used to describe complex systems composed of a set of parts (corresponding to nodes) and their connections (corresponding to edges).
Examples of graphs are road networks (junctions connected via roads), electronic circuit networks (components and their connections) and others
Networkx is an excellent Python module for manipulating such Graph objects of any kind.
Neo4j is a graph database. It uses the Graph as a data model to store such objects to a data store.

HEY: I've turned this into a blog post, which is a little more in depth.

🚨 https://eev.ee/blog/2016/06/04/converting-a-git-repo-from-tabs-to-spaces/ 🚨

Death to tabs, long live spaces

Do this

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

"Build tools for others that you want to be built for you." - Kenneth Reitz
"Simplicity is alway better than functionality." - Pieter Hintjens

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
Atomic/related changes all in one commit is something worth striving for. Having your dev

	#!/bin/sh
	#
	# Use posixregex CLI tool from: https://github.com/syzdek/dmstools/blob/master/src/posixregex.c

	RE_IPV4="((25[0-5]\|(2[0-4]\|1{0,1}[0-9]){0,1}[0-9])\.){3,3}(25[0-5]\|(2[0-4]\|1{0,1}[0-9]){0,1}[0-9])"

	posixregex -r "^(${RE_IPV4})$" \
	127.0.0.1 \
	10.0.0.1 \
	192.168.1.1 \

	---
	# salt state file for restarting a minion under its own control

	{% set delay = salt['config.get']('minion_restart_in_seconds', 5) %}

	restart-the-minion:
	file.managed:
	- name: /tmp/run_command_later.py
	- source: salt://run_command_later.py
	- mode: 775