Skip to main content

Setting Up a Python Project

  • Chapter
  • First Online:
Pro Python Best Practices

Abstract

When we started writing a small program from scratch, we did not worry much about organizing files. We simply collected everything in the same place, and that was fine. The MazeRun game started with a few Python files and a few images. But as the project grew, other files started accumulating. We already have seen various input and output files, tests, test data, configuration files, documentation, and of course more Python modules. How to organize these files properly? And how can we keep dependencies on external Python modules in check? Realizing that only a part of the software consists of code, what are Best Practices for organizing files and structuring a Python project in general?

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 19.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 29.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Kristian Rother

About this chapter

Cite this chapter

Rother, K. (2017). Setting Up a Python Project. In: Pro Python Best Practices. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2241-6_13

Download citation

Publish with us

Policies and ethics