ELel3ctron·May 15, 2016Submission
A collection of design patterns/idioms in Python
2 points · Open discussionfaif
python-patterns
Python2012–2022
faif / python-patterns
python-patterns
A collection of design patterns/idioms in Python
14Distinct people
14Mentions
1Explicit recommenders
43.1KGitHub stars
What to know before exploring
What it is
A collection of design patterns/idioms in Python
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I showed up 30 seconds after you posted your comment to say the exact same thing. It’s funny that the catchy name was the first one we both went and looked at.…
sillysaurusx used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year14 dated mentions
Observed mentions: 2012-08-03 18:17:04 UTC to 2022-05-31 15:48:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 3 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 1 | 2 |
What Hacker News says
4 sourcesA collection of design patterns/idioms in Python
4 points · Open discussionThe problem is that few design patterns are designed to be platform agnostic. They're designed to solve problems or leverage features from a specific language/language-set. Agnostic patterns tend to be heavily abstract and require specific implementation to be idiomatic.
Ask a Rust developer about implementing a Factory pattern in Rust and they'll look at you like "Why?".
You can even see this in his examples, per the Command Pattern:
//Remarks: Taken from feedback on Reddit.
//The only reason to have the Command Pattern is if your language doesn't have functions/lambdas as a first-class construct.
//A Command object is a poor-mans function.
//This is/was true of Java (depending on which version you're running),
//but is not true of Javascript, making the Command Pattern in Javascript completely pointless.
That
Read the rest
all being said, you can find a good set of design patterns in Python here:
https://github.com/faif/python-patterns
Java's design is hugely influenced by the Gang of Four book:
https://en.wikipedia.org/wiki/Design_Patterns
and so any of those will apply.
A collection of design patterns/idioms in Python
3 points · Open discussion