I guess that db/__init__. Py does something like from django. Conf import Settings and for whatever reason, it's sometimes being given the system's version of Django rather than your own You could try changing it to use a relative import, like from ..conf import Settings which should mean it uses the version in the same package as itself.
That works from Python 2.5, which is what Appengine uses.
I guess that db/__init__. Py does something like from django. Conf import Settings, and for whatever reason, it's sometimes being given the system's version of Django rather than your own.
You could try changing it to use a relative import, like from ..conf import Settings, which should mean it uses the version in the same package as itself. That works from Python 2.5, which is what Appengine uses.
This didn't work. And I understand that sometimes its being given system's version of Django.. But why? Should not Django import itself rather than system's?
– shmakova Dec 21 '10 at 21:18 Well, it's not always easy to tell where Python is getting something from, especially on appengine, where you don't know exactly how it's being run. It could be looking for modules in sys. Modules, or it might be that the folders in sys.
Path are in the wrong order. – Thomas K Dec 21 '10 at 21:30.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.