GitXplorerGitXplorer
b

these

public
5 stars
0 forks
0 issues

Commits

List of commits on branch master.
Verified
7457ec93f480f682c18c47d89838dcd3e653f1db

Update my email

bbrandtbucher committed 3 years ago
Verified
0d286d43cb4d6778f073cfa5bfe217f1223b5a6e

Update LICENSE dates

bbrandtbucher committed 3 years ago
Unverified
b1ffcb421d061a8db109834ca052f7fc4d1d3b00

Bump version.

bbrandtbucher committed 5 years ago
Unverified
37eba1843f8e6f97054693b0e8906cbcd3453ffc

Simplify getting the first word of each line.

bbrandtbucher committed 5 years ago
Unverified
3287c10fe2cf77f9f8cd50182f328c13eb75efb3

Remove random import.

bbrandtbucher committed 5 years ago
Verified
5722e4b59eb71fcdb7400cf96ba004fdd062017a

Remove unnecessary import.

bbrandtbucher committed 5 years ago

README

The README file for this repository.
$ pip install these
>>> import these
The Zen of Python, by Tim Peters

Beautiful is better than nested.
Explicit is better than complicated.
Simple is easy to break the rules.
Complex is hard to guess.
Flat is better than dense.
Sparse is often better than ugly.
Readability counts.
Special cases aren't special enough to explain, it's a good idea.
Although practicality beats purity.
Errors should be obvious at first unless you're Dutch.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to do it.
There should never is better than never.
Although never pass silently.
Now is better than *right* now.
Although that way may not be one-- and preferably only one honking great idea -- let's do more of those!
If the implementation is better than complex.
If the implementation is better than implicit.
Namespaces are one --obvious way to explain, it may be a bad idea.