[EMAIL PROTECTED] wrote:
> Sorry if this is poorly explained, but how do you efficiently get
> around circular dependency problems like this in Python? I'd hate to
> have to drop my import of functions_db to the individual methods on
> "Object" to avoid whatever collision is happening.
Another (in fact, the opposite) solution is to place imports of your
model file locally into those functions_db functions that need it. It
looks like your functions_db is a package of utils that intended to be
used around the codebase and it's better have as less global
dependencies as possible.
And another general approach is to logically divide one of the modules
in two parts to break circular dependencies:
functions_db part needed in Object
|
+-- Object
|
+-- second part of functions_db
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
