Skip to main content

Starter project for python modules

Project description

# Starter repo for python modules
[![CircleCI](]( [![PyPI version](](
[![PyPI license](](
[![Documentation Status](](

The purpose of this project is to create a shared basis for future python modules precongifugred with continuous integration, delivery, and automated releases.

## Table of Contents
<!-- TOC depthFrom:2 -->
- [Usage](#usage)
- [Installation](#installation)
- [Development](#development)
- [Configuration](#configuration)
- [Structure](#structure)
- [Source Files](#source-files)
- [CircleCI Configuration](#circleci-configuration)
- [Commits](#Commits)
- [Versioning](#Versioning)
- [Generating Releases](#generating-releases)
- [Generating an Initial Release](#generating-an-initial-release)
- [Contributing](#contributing)
<!-- /TOC -->

This project is preconfigured with [CircleCi]( for continuous integration and delivery, and serves as the starting point for the development and deployment of future Python modules that automate releases via `semantic-release.`

## Usage
To create a module while using this repo as a template, create a new repo and set this project as the remote upstream. This means that when you `git fetch` and `git merge` (or `git pull`, if you prefer), your module project will be updated with changes made in this starter project.

To set the upstream of your project:
git remote add upstream

If you don't want to keep your downstream module project sycned with changes made to this starter project, feel free to just clone or create a fork.

## Installation
To install this module:
pip install module-starter.leon
Downstream modules can be installed in the same way once deployed via `semantic-release`, just replace `module-starter.leon` with the name of the module specified in [``](

## Development
In order to utilize the structure of this project for downstream modules, you should consider the following notes.

### Configuration
All module metadata lives within [``]( This is where you link depenencies, specify source directories, and other important package metadata. A snippet of our [``](
description='Starter project for python modules',
keywords='module starter',
author='Aumit Leon',
extras_require={'dev': DEVELOPMENT_MODULES},
'console_scripts': ['command=src.command_line:main'],

### Structure
The following is an overview of the directory structure:

[``]( should live in the root of your project. Other files that should live in the root of your project:

* [``]( Specifies a list of files outside of your specified `packages` (in this case, `src`) that should be included in your distribution.
* [`setup.cfg`](setup.cfg): Includes configuration information for `semantic-release`.
* [`requirements.txt`](requirements.txt): Dependencies for your project.
* [`requirements-dev.txt`](requirements-dev.txt): Development dependencies for your project, including any dependencies required for testing.
* [`LICENSE`](LICENSE): This project uses the [MIT License](

### Source Files
All source files (i.e your python files for the module itself) should live in the [`src`](src) directory. You could use a different directory name, if you do, be sure update the `packages` option within [](

This project currently support modules that are meant to be run as command line tools-- see [issue #10]( for information on future work necessary to provide support for modules meant to be consumed by other python tools.

Make modifications to your source files as necessary.

### CircleCI Configuration
This project is equipped with a basic [`config.yml`](.circleci/config.yml). The details surrounding CircleCI configuration will vary project to project based on whatever workflows you deem necessary. For more information on CircleCI config files, check out their [website](

### Commits
All commits should follow the [Angular Commit Message Convention](# It is important that you follow these guidelines, since automatic versioning parses commits messages when generating a release. For more information on semantic release and commits, check out their [github project](

### Versioning
All versioning is automatically handled by [`python-semantic-release`]( This project uses [`semantic-versioning`](, said to make versioning "[unromantic and unsentimental]("

The `VERSION` variable is defined in [``](, and is made avaible to `semantic-release` by our [`setup.cfg`](setup.cfg):
version_variable =
upload_to_pypi = true

When generating new releases, `semantic-release` will automatically bump this variable to the new version number. This is pushed automatically to github via the `release` workflow in our [`config.yml`](.circleci/config.yml).

## Generating Releases
Releases and versioning are automatically handled by [`python-semantic-release`]( In the `release` workflow within our [`config.yml`](.circleci/config.yml), we have a step that generates the distribution and publishes to the [Python Package Index]( (PyPI):
- run:
name: upload to pypi
command: |
git config --global ""
git config --global "aumitleon"
. venv/bin/activate
semantic-release publish
This step is only run on *merges into master*. Regular PR branches only run the `build_and_test` workflow, which is meant to give the developer information on if builds are passing with their code.

### Generating an Initial Release
`semantic-release` is dependent upon git tags to generate and bump new releases and versions. When initially deplpying module projects to github, make sure to push a git tag with the initial version before expecting `semantic-release` to automatically generate releases.

If your code is starting at `version==1.0.3`, before automating releases, create a tag
git tag v1.0.3
Push the tag to the remote:
git push -u origin v1.0.3
Moving forward, `semantic-release` should be able to automatically generate releases for you.

## Contributing
If you find this project useful and would like to contribute back to it, feel free to check out the [`CONTRIBUTING`]( page.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for module-starter.leon, version 0.1.1
Filename, size & hash File type Python version Upload date
module_starter.leon-0.1.1-py2-none-any.whl (6.0 kB) View hashes Wheel py2
module-starter.leon-0.1.1.tar.gz (5.0 kB) View hashes Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page