Sithu Aung sithu

A Typical directory structure for running tests using `unittest`

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project

├── antigravity.py

Previous versions used homebrew to install the various versions. As suggested in the comments, it's better to use pyenv instead. If you are looking for the previous version of this document, see the revision history.

$ brew update
$ brew install pyenv
$ pyenv install 3.5.0
$ pyenv install 3.4.3
$ pyenv install 3.3.6
$ pyenv install 3.2.6
$ pyenv install 2.7.10

$ pyenv install 2.6.9

Executable fat jars are easy to deploy and upgrade, and don't need wrapper scripts to pull in the classpath. You can use the Gradle fatjar plugin to create executable, self-contained jars in Gradle, akin to the Shade plugin for Maven -

apply plugin: 'fatjar'
buildscript {
  dependencies {
  classpath 'eu.appsatori:gradle-fatjar-plugin:0.1.3'  
  }
}

	import io.netty.bootstrap.Bootstrap
	import io.netty.channel.ChannelHandlerContext
	import io.netty.channel.SimpleChannelInboundHandler
	import io.netty.channel.nio.NioEventLoopGroup
	import io.netty.channel.socket.nio.NioDatagramChannel
	import io.netty.util.CharsetUtil
	import io.netty.util.concurrent.DefaultThreadFactory
	import kotlinx.coroutines.experimental.async
	import kotlinx.coroutines.experimental.newFixedThreadPoolContext

	# docker build -t ubuntu1604py36
	FROM ubuntu:16.04

	RUN apt-get update
	RUN apt-get install -y software-properties-common vim
	RUN add-apt-repository ppa:jonathonf/python-3.6
	RUN apt-get update

	RUN apt-get install -y build-essential python3.6 python3.6-dev python3-pip python3.6-venv
	RUN apt-get install -y git

	cat /usr/share/grafana/grafana-backup.sh
	#!/bin/bash

	DB="/var/lib/grafana/grafana.db"
	BACKUP="/data/backup/grafana/grafana.db-$(date +%Y%m%d).bck"
	SQLITE=/usr/bin/sqlite3
	ZIP=/bin/gzip

	${SQLITE} ${DB} ".backup ${BACKUP}"
	${ZIP} ${BACKUP}

	#! /usr/bin/env python
	# Of course, the author does not guarantee safety.
	# I did my best by using SQLite's online backup API.
	from __future__ import print_function
	import sys, ctypes
	from ctypes.util import find_library

	SQLITE_OK = 0
	SQLITE_ERROR = 1
	SQLITE_BUSY = 5

	# source: http://st-on-it.blogspot.com/2010/01/how-to-move-folders-between-git.html
	# First of all you need to have a clean clone of the source repository so we didn't screw the things up.

	git clone git://server.com/my-repo1.git

	# After that you need to do some preparations on the source repository, nuking all the entries except the folder you need to move. Use the following command

	git filter-branch --subdirectory-filter your_dir -- -- all

	# This will nuke all the other entries and their history, creating a clean git repository that contains only data and history from the directory you need. If you need to move several folders, you have to collect them in a single directory using the git mv command.

	[user]
	name = Pavan Kumar Sunkara
	email = [email protected]
	[core]
	editor = vim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	excludesfile = ~/.gitignore
	[sendemail]
	smtpencryption = tls
	smtpserver = smtp.gmail.com

	A warning occurred (42 apples)
	An error occurred

Sithu Aung sithu

A Typical directory structure for running tests using unittest

A Typical directory structure for running tests using `unittest`