Django - how should I implement generic apps that have dependencies on other generic apps?
- by MikeRand
Hi all,
I'm using Marty Alchin's Django app that creates historical records (add, change, delete) based on models found in other Django apps (found in chapter 11 of Pro Django).
Question: how do I implement this historical_records app into my other generic Django apps while still maintaining loose coupling?
For example, I have a generic app (forecast) that manages a Forecast (of any other model). For one project, I'd like to use historical_records so that I can track changes to a Forecast instance. But I don't want to require all future projects that might want to use forecast to also use historical_records.
Any guidance would be greatly appreciated.
Thanks,
Mike
