Converted all relative imports to in-package absolute ones in ./django.

[lyova24]

Trac ticket number

N/A

Branch description

Replaced all relative imports (e.g., from ..utils import ...) with in-package absolute imports (e.g., from django.contrib.postgres.utils import ...) across the codebase in ./django.

Use absolute imports for other Django components and relative imports for local components.
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/#imports

FYI: used my own pre-commit-hook shrimport

Checklist

• This PR targets the main branch.
• The commit message is written in past tense, mentions the ticket number, and ends with a period.
• I have checked the "Has patch" ticket flag in the Trac system.
• I have added or updated relevant tests.
• I have added or updated relevant docs, including release notes if applicable.
• I have attached screenshots in both light and dark modes for any UI changes.

[lyova24]

@sarahboyce @nessita I saw you guy reviewing other PRs.

Is there some rule that i missed and didn't follow or should i just w8 my turn?

[nessita]

@sarahboyce @nessita I saw you guy reviewing other PRs.

Is there some rule that i missed and didn't follow or should i just w8 my turn?

Hi! If you haven't already, I'd recommend reviewing the contributing guidelines and more importantly the FAQ for contributing. They explain how the review process works and what to expect in terms of timing. Specifically for this change, it's unclear if it's worth the entry in the (very curated) git history of Django.

Also, just a small note on inclusivity: phrases like "you guys" can feel gender biased. You might find heyguys.cc helpful, it offers some good alternatives.

[sarahboyce]

Use absolute imports for other Django components and relative imports for local components.
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/#imports

To me the changes here are not clearly violating the above. Depending on what you define as a component, they feel to be from the same component

[lyova24]

I apologize @nessita, I didn't mean to offend you with my last comment. I'm not a native speaker, so I may not know some of the intricacies of communication in it. I'll take your remark about the phrase "you guys" into account.

---

Regarding the changes i made: you, @sarahboyce, are absolutely right, it all depends on what exactly we call a component. By component I mean a package. If I understand correctly, the specifics of the language indicate that the folder with the __init__.py file is a package - an assembly of combined modules.

For example, django.contrib.postgres.utils and django.contrib.postres.fields are different packages. Using a relative import of the first package from the second is not correct in my opinion, since field does not directly relate to utils and vice versa. Also, the django.contrib.postgres.fields package has it's own utils.py in it. Similarly with other examples in the PR.

I understand that the changes may seem insignificant, but nevertheless they increase the readability of the code, and its logical coherence.

I respectfully ask you to look at this PR again, excuse me for my lack of education in English and make a decision on whether this PR is useful.

---

With respect, lyova24. translated with translate.google.com