|
1 | | -# Python-Interview-Problems-for-Practice |
| 1 | +# Python-Interview-Problems-for-Practice [](http://github.com/ddavison/github-badges) [](http://github.com/ddavison/github-badges/fork) |
| 2 | + |
2 | 3 | 40+ Common code and interview problems solved in Python (it's growing...) |
3 | 4 |
|
4 | 5 | ### The core idea is not to utilize built-in functions or library and giving it a more logic-based approach, so that it can be language-friendly and not end up being another repository of "Python Tips and Tricks" . |
5 | 6 |
|
| 7 | +## How good is the code ? |
| 8 | +* It is well tested |
| 9 | +* It passes style checks (PEP8 compliant) [TODO] |
| 10 | +* It can compile in its current state (and there are relatively no issues) |
| 11 | + |
| 12 | +## How much support is available? |
| 13 | +* FAQs (coming soon) |
| 14 | +* Documentation (coming soon) |
| 15 | + |
| 16 | +## Issues |
| 17 | +Feel free to submit issues and enhancement requests. |
| 18 | + |
| 19 | +## Contributing |
| 20 | +Please refer to each project's style guidelines and guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow. |
| 21 | + |
| 22 | + 1. **Fork** the repo on GitHub |
| 23 | + 2. **Clone** the project to your own machine |
| 24 | + 3. **Commit** changes to your own branch |
| 25 | + 4. **Push** your work back up to your fork |
| 26 | + 5. Submit a **Pull request** so that we can review your changes |
| 27 | + |
| 28 | +NOTE: Be sure to merge the latest from "upstream" before making a pull request! |
| 29 | + |
6 | 30 | # LICENSE |
7 | 31 | MIT License |
0 commit comments