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?
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights 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
DOI: https://doi.org/10.1007/978-1-4842-2241-6_13
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2240-9
Online ISBN: 978-1-4842-2241-6
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)