-
Notifications
You must be signed in to change notification settings - Fork 7k
Enhance documentation with brief, high-level descriptions/usage of patterns #53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I find this a good idea. Are you willing to update the README? |
If you'd be will to discuss the patterns that I'm not familiar with.
|
Go to town. I noted a couple of patterns that either weren't patterns (graph-search), or were somewhat obsolete (null) in modern Python. Feel free to either disagree, or remove them. |
You are right about graph search, it was checked in by a contributor and I decided to keep it not because it's a pattern but as an idiom that demonstrates how you can work with graphs in python. As for null, I'm not sure about how useful it is. Can you give references about what makes it obsolete in Python? |
Maybe you could create a new directory called "algorithms", or project GvR considered it unpythonic to either not check the value, or just catch http://legacy.python.org/dev/peps/pep-0336/ Abstract BDFL Pronouncement Since Python developers are usually encouraged to rely on exceptions rather On Mon, May 5, 2014 at 9:03 AM, Sakis Kasampalis
|
I'd hate to think that I'm the only one of the thousands of people who have starred this project, but I would greatly benefit from a list of the purposes of each pattern in the README document. It would keep me/us/others from having to peruse each individual module to determine their use when there are so many other interesting things that that equally demand attention.
Thoughts?
The text was updated successfully, but these errors were encountered: