First of all thanks for all responses.
I've still one more question which is connected to that one particular
issue. What if classes are importing each other.
models/
__init__.py
one.py
two.py
== __init__.py ===
from one import ModelOne
from two import ModelTwo
=== one.py
On Sun, 2009-05-03 at 10:01 -0700, Rick Wagner wrote:
> > > Thank you for the explanation. I think this trick is not in the
> > > Documentation yet
> >
> > That's because it's pretty basic Python knowledge. I'm sure I've read
> > on this list that basic Python knowledge isn't supposed to be
>
> > Thank you for the explanation. I think this trick is not in the
> > Documentation yet
>
> That's because it's pretty basic Python knowledge. I'm sure I've read
> on this list that basic Python knowledge isn't supposed to be
> documented in Django as it's already part of the official Python
On 3 May 2009, at 13:54 , johan.uhIe wrote:
> Thank you for the explanation. I think this trick is not in the
> Documentation yet
That's because it's pretty basic Python knowledge. I'm sure I've read
on this list that basic Python knowledge isn't supposed to be
documented in Django as it's al
Thank you for the explanation. I think this trick is not in the
Documentation yet, I've opened a ticket for it ...
http://code.djangoproject.com/ticket/10985
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django use
On Apr 20, 2:57 am, x_O wrote:
> Hi
>
> I'm looking for some general solution how to split models.py. Right
> now my models.py reached 1000 lines and that argues some how with good
> programing behaviour that I used use.
>
> I'm thinking about:
> myproject/
> settings.py
> myapp/
>
Hi
I'm looking for some general solution how to split models.py. Right
now my models.py reached 1000 lines and that argues some how with good
programing behaviour that I used use.
I'm thinking about:
myproject/
settings.py
myapp/
models/
file.py
directory.py
instea
7 matches
Mail list logo
