Display development server address after server bind

[fmwviormv]

Currently Django will display server name and port before actual binding;
so there is a problem with port 0 (automatic port):

$ ./manage.py runserver 127.0.0.1:0
...
Starting development server at http://127.0.0.1:0/
Quit the server with CONTROL-C.

in this case port number is chosen automatically by operating system dynamically;
so there is no way we can find it before binding.
Django should display port number after binding (real port number):

$ ./manage.py runserver 127.0.0.1:0
...
Starting development server at http://127.0.0.1:25837/
Quit the server with CONTROL-C.

I also have a pull-request in github:
​https://github.com/django/django/pull/14250

[Abhijeet Pal]

Hi, there has not been any activity in the last 12 months and the original PR was closed. I am assigning the ticket to myself to move it forward.

[Abhijeet Pal]

PR ​https://github.com/django/django/pull/15748

[Gav O'Connor]

Happy to pick up the PR updates if @TheAbhijeet isn't available?

[Abhijeet Pal]

Hi, was busy for a couple of weeks, I would try to make the asked changes over this weekend.

[Carlton Gibson]

Additional tests needed (and maybe adjustment) on the changes to basehttp.run, but looking about right beyond that.

[Dhanush]

PR ​https://github.com/django/django/pull/16319

[Abhijeet Pal]

Hi, sorry.

But I was waiting for some comments on it to move forward to closing the ticket on my PR.

I missed Carlton's notification of

Patch needs improvement: set

Never mind I wish you luck.

[Mariusz Felisiak <felisiak.mariusz@…>]

In a18d20c:

Fixed #32813 -- Made runserver display port after binding.

Thanks Florian Apolloner for the review.

[Mariusz Felisiak <felisiak.mariusz@…>]

In a0623b11:

[4.2.x] Fixed #32813 -- Made runserver display port after binding.

Thanks Florian Apolloner for the review.

Backport of a18d20ca97e6799152c1e0b6f007fde943053dcb from main