id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
16734	Set script prefix in django.setup() to allow its usage outside of requests	Dougal Sutherland	nobody	"The script prefix for `django.core.urlresolvers` doesn't get set to anything when being called through `manage.py`, because of course it doesn't know what that value should be. This is a problem if you're rendering views (or otherwise reversing urls) from a `manage.py` command (as one of my sites does to send emails).

This is solvable by calling `set_script_prefix` from `settings.py`, but that feels kind of dirty since it's then about to be rewritten in the WSGI handler.

I don't know what a good solution to this would be. Perhaps it would be nice to be able to set a global default script path somewhere that would then get incorporated into the default values of things like LOGIN_URL.

Maybe just a note in the documentation would be good. It took me a while to figure out, because I haven't been able to find anything else about this online. (I guess that non-`/` script paths are uncommon and reversing urls from `manage.py` is also uncommon, so both together are very uncommon.)"	New feature	closed	Core (Management commands)	dev	Normal	fixed		julenx@… Akos Ladanyi	Ready for checkin	1	0	0	0	0	0