[Django] #36176: Run database migrations without black, program hang forever

[Django]

#36176: Run database migrations without black, program hang forever
-------------------------------------+-------------------------------------
Reporter: neoblackcap | Type: Bug
Status: new | Component: Core
| (Management commands)
Version: 5.1 | Severity: Normal
Keywords: migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
System: windows wsl2 Ubuntu 22.04.5 LTS

If i don't install black, run database migrations will cause program hang
forever
--
Ticket URL: <https://code.djangoproject.com/ticket/36176>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#36176: Run database migrations without black, program hang forever
-------------------------------------+-------------------------------------

Reporter: neoblackcap | Owner: (none)
Type: Bug | Status: closed
Component: Core (Management | Version: 5.1
commands) |
Severity: Normal | Resolution: needsinfo

Keywords: migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Simon Charette):

* resolution: => needsinfo
* status: new => closed

Comment:

This could relate to #35308 but it's impossible to tell from your report
for a few reasons.

1. You didn't provide exact steps to reproduce. Your report is lacking
Python and/or Django version and the exact step to reproduce (how did you
invoke the command? how is your WSL seetup)
2. ''Running data migrations'' usually means calling `migrate` but
[https://docs.djangoproject.com/en/5.1/ref/django-admin/#black-formatting
the latter doesn't make use] of `black` at all. You could have meant
`makemigrations` which does make use of `black` but again it's for you to
tell us no for us to guess.
3. You didn't provide any traceback or hints that led you to conclude that
Django is to blame here.

Please re-open if you can provide steps to reproduce in order to help us
help you.
--
Ticket URL: <https://code.djangoproject.com/ticket/36176#comment:1>