Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Cracking the Coding Interview 6th Ed. Python Solutions

NotificationsYou must be signed in to change notification settings

OpenSourceLearningRepos/CtCI-6th-Edition-Python

 
 

Repository files navigation

These arePython solutions for the bookCracking the Coding Interview, 6th Edition byGayle Laakmann McDowell.

How to use?

To run the programs, just use thepython chapter_X/filename.py command.

To run the tests:pip install pytest andpytest

Contributions

Contributions welcome! Please submit separate pull requests for each solution you work on.

In general solutions should fall into one of the following three categories:

  • algorithm demonstration. This is the primary type of problem and solution that the text is concerned with. Assuch, solutions should not use standard library functions in cases that would make it unnecessary to implement thealgorithm. The goal of these solutions should be to have an easy to understand solution that demonstratesunderstanding of the algorithm.
  • python demonstration. We also accept solutions that solve the problem in a more practical way, using whateverstandard library functions are available. Please do not use any third party dependencies. These solutions shouldalso be easy to understand and good examples of pythonic ways of doing things.
  • speed demonstration. These alternative solutions may be accepted if the fastest way to do something is not veryreadable or intuitive and thus it doesn't fit into the first two categories.

If you want to do everything really well, here are some guidelines. Solutions should:

  • work with Python 3.6 or greater
  • not depend on third-party libraries (likenumpy)
  • followpython style conventions
    • camel_case for everything except classes
    • descriptive, longer variable names
  • be formatted using theblack code formatter
  • include tests to prove they work.pytest is supported
  • have a clean commit history ideally following theangular commit message conventionand including the problem being worked on in parenthesis. For examplefeature(C01_P04): added solution. The C01_P04referring to Chapter 1, Problem 4. Look at ourcommit history for more examples:

We'll still work with your contributions even if they don't follow these guidelines so don't let that stop you.

About

Cracking the Coding Interview 6th Ed. Python Solutions

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python100.0%

[8]ページ先頭

©2009-2025 Movatter.jp