Hi Jason, Jason K wrote: > Any idea how to fix this? It's not the end of the world, but I do like > the convenience of using the launcher, and also find it useful to drop > into the manage.py shell. Doesn't help much if they use different > datastore's..
The Django helper does this to allow you to develop multiple Django projects in parallel. The SDK uses the same datastore location for every project, while the Django helper inserts the name of your project into the datastore filename. You can use the --datastore_path and --history_path options to dev_appserver to point it to the locations used by the Django helper rather than the defaults. Having said that, the aim was for you to be able to use manage.py for almost everything when developing a Django project rather than having to use a combination of manage.py and dev_appserver. From what you have described you should be able to use a combination of manage.py runserver and manage.py shell and the helper will handle pointing you to the appropriate datastore in the background. Cheers Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
