That answer is about reversing across apps, which I'm quite familiar with, and which still requires that the URL-owning app and its URLConfs be imported to the Django project where the reversing is being done. The trouble is that the URLConf also has to import the views; which in turn won't import if all their dependencies are available.
Thinking about it another way, I need to access a shared URLConf that doesn't need to import the view classes/functions that get called when a URL is actually accessed. The information in the URLConf itself should be enough to reverse a URL, since the format and variables for each path are recorded in the URLConf. But you can't create a URLConf without importing the views it calls; and Django will consider it invalid and refuse to parse/reverse those URLs for you if it doesn't have access to the views.
Is there any sensible way to work around that?