Right, thanks for the clarification! I see now that it has been added
to the tutorial as well, which is good:
"In this tutorial, we'll create our poll app in the mysite directory,
for simplicity. As a consequence, the app will be coupled to the
project - that is, Python code within the poll app w
On 4/13/07, Anders Olsson <[EMAIL PROTECTED]> wrote:
> portable and decoupled from the project where it is used. But doesn't
> the project being the top level python package make it almost
> impossible to move an app from a project to another without modifying
> the import statements?
If you insi
This is something I've found confusing ever since my first contact
with django, reading the tutorial - all this emphasis on apps being
portable and decoupled from the project where it is used. But doesn't
the project being the top level python package make it almost
impossible to move an app from
hi,
as i read that pep, relative imports are not deprecated at all, they
just will require a new syntax in 2.8.
i advocate the use of relative imports, in cases like newforms as well
as in "user-space" apps, due to the possibility of name changes: sooner
or later, newforms will just be called for
