Re: models and python circular import

2008-01-11 Thread Grindizer
On 8 jan, 14:54, Alex Koshelev <[EMAIL PROTECTED]> wrote: > Its very strange that so "hard linked" applications can produce clean > and logic architecture:) g ! :-) You were rigth, finally i review my project's logic, and then put ModelsA3 where it shoud be, i.e in app B, and now it's more

Re: models and python circular import

2008-01-08 Thread Medardo Rodriguez
On Jan 8, 2008 8:24 AM, Grindizer <[EMAIL PROTECTED]> wrote: > Hello. > I have a project with at least 2 applications > A, which define ModelA1, ModelA2, ModelA3 (and other). > B, which define ModelB1, ModelB2. > > And I have these dependencies: > In A: > - ModelsA1 need as a foreign key ModelB1

Re: models and python circular import

2008-01-08 Thread Alex Koshelev
Its very strange that so "hard linked" applications can produce clean and logic architecture:) 1. Try to split your A's models.py into 2 files. A1, A2 in first file. A3 in second file. In first models file import second with wildcard(*). In B models.py import only second A file. It's only suggest

models and python circular import

2008-01-08 Thread Grindizer
Hello. I have a project with at least 2 applications A, which define ModelA1, ModelA2, ModelA3 (and other). B, which define ModelB1, ModelB2. And I have these dependencies: In A: - ModelsA1 need as a foreign key ModelB1 - ModelsA2 need ModelB2 (ManyToManyField) In B: - ModelB2 need ModelA3 (F