Скачать или смотреть Simplifying STATIC and MEDIA Settings in Django 3.1

Discover the best practices for setting up static and media files in Django 3.1 with easy-to-follow instructions.
---
This video is based on the question https://stackoverflow.com/q/63436120/ asked by the user 'Flavio Oliveira' ( https://stackoverflow.com/u/13045151/ ) and on the answer https://stackoverflow.com/a/63436619/ provided by the user 'Roham' ( https://stackoverflow.com/u/13155572/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Django new version 3.1, the settings file have some changes

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Simplifying STATIC and MEDIA Settings in Django 3.1

As an evolving framework, Django continuously updates its features and conventions to improve developer experience. One of the noteworthy updates in Django version 3.1 is how we handle static and media file settings in the settings.py file. If you have recently upgraded to Django 3.1, you may have noticed some changes that could disrupt your workflow. In this guide, we’ll explore how to configure your static files correctly under the new version.

The Problem

Many developers have been accustomed to setting up their static and media files in Django using the os module. However, with the new update, there’s an improved way to achieve the same setup without the need for redundant imports. This change has caused confusion as the traditional method no longer works properly.

Previous Configuration (Before Django 3.1)

Previously, your settings.py might look something like this:

[[See Video to Reveal this Text or Code Snippet]]

New Configuration (Django 3.1 and Beyond)

With Django’s update, the focus shifts from using os to a more Pythonic approach with the pathlib module. The new approach simplifies your code and eliminates any unnecessary imports.

The Solution

Here’s how you can adjust your settings for static and media files in Django 3.1:

Updated Code for settings.py

Replace your existing static and media configurations with the following code:

[[See Video to Reveal this Text or Code Snippet]]

Breakdown of the Configuration

from pathlib import Path: This import allows us to work with file paths in a clean and readable manner.

BASE_DIR: This line defines the root directory of your project using Path methods. It’s a straightforward way to ensure you’re pointing to the correct directory.

STATIC_ROOT and MEDIA_ROOT: Instead of using os.path.join, we can leverage the / operator with Path to create paths, making the code more intuitive.

Why This is Best Practice

Readability: The use of pathlib enhances code readability and makes it easier to understand for other developers who are familiar with this approach.

Less Code: It reduces the amount of boilerplate code since you do not need to import os, thus simplifying your settings.

Consistency: Using pathlib aligns your Django configurations with modern Python practices, promoting uniform coding styles.

Conclusion

Transitioning to Django 3.1 might seem daunting at first, especially regarding changes in configuration settings. However, adopting the updated methods for STATIC and MEDIA settings can streamline your development process. By implementing the above adjustments to your settings.py, you’re not only ensuring compatibility with the latest version but also adhering to best practices in Python development.

If you follow these guidelines, you’ll have a more efficient setup that avoids redundancies. Happy coding with Django 3.1!