Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
money_manager wrapper attempt fails for managers associated on "objects" #2
Django 1.2 introduced multiple DB connections. And Django 1.4 removes the compatibility layer. Update our prototypes so we work with Django 1.2+ or later.
It is already indicated later on but is easily missible.
…n more. And we'll just put in references to where to get the source code for interested parties.
At least this way the tests run. Even though they do not pass yet.
Monkey patch the Django admin so that we can display django-money fields read-only. In order to do this, we simply catch the exception that results from trying to convert a money object (e.g. '10 USD') into a floating field. And then we call just ask for the string representation of the field.
When serializing the field, we were outputing the displayed value. This would not work, because we would (sometime) attempt to unserialize non-UTF8 data. Instead, just output the actual amount when serializing, since we also have the currency to go with the amount everything Just Works (tm).
Hey mate, the amount of work done here is awesome, and I suppose we need to figure out if it's possible to merge this back together, or what to do. It looks like you're maintaining a branch that is significantly more up to date - maybe I can give you commit rights to this repo (or add a link to your fork), and you can take over maintaining it?
Either way, the amount of commits here is way too much for me to merge safely, it will need to be done in some other way, for instance by merging the current state of this repo over to you and then deprecating this repo, if you want to take over maintaining it.
Closing this PR, but let me know what you think about taking over the project :)