On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
> So 'DATABASE_NAME' should be the full name of a non-existant file. I
> had thought they wanted the path to where the file was located.
>
> !!Works fine now!!
>
> Two problems for Django with Python 2.5
FYI, the 0.95 tarball on the site is prett
So 'DATABASE_NAME' should be the full name of a non-existant file. I
had thought they wanted the path to where the file was located.
!!Works fine now!!
Two problems for Django with Python 2.5
bug 1)
ez_setup.py in Django .95 folder should have:
DEFAULT_VERSION = "0.6c3"
instead of
DEFAULT_VERS
The the name to a file in a directory - SQLite databases are a single file,
and it won't be able to create one if a directory already exists with the
same name.
-joe
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
>
> I tried to do:
> Python manage.py syncdb
> and got the error "No module name
I tried to do:
Python manage.py syncdb
and got the error "No module named pysqlite2". I edited the file
\Python25\Lib\site-packages\Django-0.95-py2.5.egg\django\db\backends\sqlite3\base.py
to read:
from sqlite3 import dbapi2 as Database
instead of
from pysqlite2 import dbapi2 as Database
and the e
>From Django Djumpstart I attemptd:
python manage.py syncdb
and got an error:
C:\Django\gtd>python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File
"C:\Python25\lib\site-packages\django-0.95-py2.5.egg\django\core\manageme
nt.
5 matches
Mail list logo
