effigies

Contemporary Python Packaging

This document lays out a set of Python packaging practices. I don't claim they are best practices, but they fit my needs, and might fit yours.

Validity

This document has been superseded as of January 2023.

This was written in July 2020, superseding this gist from 2019.

effigies

Contemporary Python Packaging

This document lays out a set of Python packaging practices. I don't claim they are best practices, but they fit my needs, and might fit yours.

Validity

This document has been superseded as of July 2020.

This was written in July 2019. As of this writing Python 2.7 and Python 3.5 still have not

wanirepo

% In this simulation we examined how reliable peak distance and pattern correlation
% by comparing two simulated data with the same ground truth patterns of signal.

% define SNR levels

snr_all = [.1 .3 .5 .7 .9 1.1];

% create ground truth pattern

pattern = [0.4 1.7 0.5 0.7 0.2

miykael

oliviaguest

#!/usr/bin/env python3

import csv
import time
import tweepy
import datetime

# Read http://docs.tweepy.org/en/v3.5.0/auth_tutorial.html to fill in the two lines below.
auth = tweepy.OAuthHandler('XXX', 'YYY')
auth.set_access_token('123', '456')

robertpainsi

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

joseluis

#!/usr/bin/env bash
# 
#          name : commitstrip-dl
#   description : download all the commitstrip strips
#       version : 1.0.0
#        author : José Luis Cruz © 2017
#   dependencies: bash<=4 curl [sxiv]
#       license : MIT
# 

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

lukas-h

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

• The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

• 🇫🇷 Cette liste en français

endolith

# https://github.com/matplotlib/matplotlib/issues/881
# Several of the ColorBrewer maps are "qualitative", meaning
# they are just a group of colors that can be used together 
# for categories of data.  So I remapped Accent to segments 
# instead of continuous:

# Actually, these should be used with ListedColormap, and 
# the number of colors should depend on the number of 
# categories in the data, with colors removed from the 
# list in a certain order?