Hi all, trying to set up the django example to see how helpful pants will be in terms of packaging a project for distribution in the future and I'm running into some issues while attempting to use the manage.pex files on a different ip and port. Is that standard or is it specifically locked by the binary targets of the example?

The django example repo uses this to figure out the dev port for manage.py: https://github.com/pantsbuild/example-django/blob/67681a5acc71b0435c180e640730c038c570a81f/helloworld/util/discovery.py#L13

I was doing general testing to see how the pex files would interact with arguments and I wanted to make the dev server match the config that I normally utilise from my VM... In this case I wanted to get some form of output accessible from the host the VM is sitting on, thus I wanted to output to

0:8008

, such that the port forwarding we have in place knows to hand this off to the localhost of the host machine

The pex should behave the same as running raw

manage.py

, so it should take the same flags. But in the example we munge those flags, e.g., here: https://github.com/pantsbuild/example-django/blob/67681a5acc71b0435c180e640730c038c570a81f/helloworld/util/service.py#L31