I'm inclined to make the changes, skip the deprecation, and react
appropriately if anyone raises a use case that can't be achieved with the
new "bind to port 0" technique.
I found a few more things that could be removed, for example the "manage.py
test --liveserver=..." option. Only creating a
I've never personally used DJANGO_LIVE_TEST_SERVER_ADDRESS for another
purpose than preventing port conflicts which binding to port 0 solves.
It always looked strange to me to rely on an environment variable to
achieve this. It feels like it was done this way to avoid introducing yet
another
