When thinking about your development environment, there are three important things to keep in mind: isolation, determinism, and similarity. They\u2019re each important, and they work in concert with one another.<\/p>\n
Isolation means that you\u2019re not inadvertently leveraging tools or packages installed outside the environment. This is particularly important when it comes to something like Python<\/a> packages with C<\/a> extensions: if you\u2019re using something installed at the system level and don\u2019t know it, you can find that when you go to deploy or share your code that it doesn\u2019t operate the way you expect. A tool like virtualenv<\/a> (http:\/\/www.virtualenv.org\/<\/a>) can help create that sort of environment.<\/p>\n Your environment is deterministic if you\u2019re confident about what versions of your dependencies you\u2019re relying on, and can reproduce that environment reliably.<\/p>\n Finally, similarity to your production or deployment environment means you\u2019re running on the same OS<\/a>, preferably the same release, and you\u2019re using the same tools to configure the development environment<\/a> that you use to configure your deployment environment. This is by no means a requirement, but as you build bigger, more complex software, it\u2019s helpful to be confident that any problem you see in production is reproducible in your development environment and limit the scope of the investigation to the code you wrote.<\/p>\n","protected":false},"excerpt":{"rendered":"