On 23/05/2018 12:31 PM, Simon McConnell wrote:
I'm in a similar boat at the moment. There
is https://github.com/vimeo/py-money too.
I looked at that but it probably won't ever support exchange rates. Not
sure yet if that is a show stopper because maybe forex is a separate
thing anyway. I do need exchange rates in another project and I'd like
choose a MoneyField which works in all projects.
Note that django-money uses py-moneyed which does not yet use Babel,
so rendering of the correct symbol is limited to a few hardcoded
currencies.
Interesting. I don't use Babel yet. But it is on the horizon.
I'm beginning to see why Django doesn't (yet?) have a built-in
MoneyField and I'm still interested in experience with differences
between them.
Mike
https://github.com/python-babel/babel
On Tuesday, 22 May 2018 11:25:04 UTC+10, Mike Dewhirst wrote:
I have just read ...
* Martin Fowler's Money base pattern (P488 to 495)
https://martinfowler.com/eaaCatalog/money.html
<https://martinfowler.com/eaaCatalog/money.html>
* https://github.com/poswald/python-money
<https://github.com/poswald/python-money>
* https://github.com/django-money/django-money
<https://github.com/django-money/django-money>
* https://github.com/limist/py-moneyed
<https://github.com/limist/py-moneyed>
... and I am spoiled for choice. I was going to just use a
DecimalField
and CharField for currency and do my own thing when I decided to pull
Martin Fowler off my shelf and saw how careful I was going to need
to be.
My question: Is Django planning to adopt one or other of the above
implementations?
I'm just trying to short-circuit more detailed analysis of these
packages and perhaps others I haven't yet found. If one is on the
horizon for Django I'll just go with that.
Thanks
Mike
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/762af31e-56fd-4976-bef2-f627c5673f38%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/762af31e-56fd-4976-bef2-f627c5673f38%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/2caf1fc9-c286-a81f-3ed0-aede1dc9c130%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.
