On Wed, Feb 11, 2009 at 5:00 PM, smcoll wrote:
> How about requiring that any urls.py file at least have a
> corresponding __init__.py before processing it?
That's not really something Django can do: if you don't have an
__init__.py, the urls.py can't be imported to make the check. In other
word
i had a problem recently where a stray urls.py was choking the reverse
function. This particular urls.py was just thrown to the side in a
directory, so it took me a while to realize what was going on.
How about requiring that any urls.py file at least have a
corresponding __init__.py before proc
