It does seem odd, but I can get the same Django project to start up without issue using an older version of the Jython beta. That leads me to believe it has to be something specifically different with b3.
This error message sounds suspect -- it's referring to a module name, yet somehow a $py.class is tagged onto the end. Maybe Django is special casing '.pyc' somewhere, but not $py.class, or something similar?
On Mar 12, 2009, at 6:47 AM, Josh Juneau wrote:
manage.py syncdbError: Could not import settings 'newdjango.settings$py' (Is it on
sys.path? Does it have syntax errors?): No module named settings$py