I'd suggest to use git bisect to find the Django commit where the behavior
changed:
https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression
On Wednesday, April 5, 2017 at 5:57:03 PM UTC-4, Maximiliano Robaina wrote:
>
> Hi,
>
>
> I'm the maintener of django-firebird database backend.
>
> I've an strange behavior (a different result) when reading a value from a
> DecimalField between Django 1.7 and Django 1.8 and I'm trying to figured
> out where is my mistake.
>
> I've a django project which I update from 1.7 to 1.8.
> In this project I've a model with a DecimalField. (by example, price
> = DecimalField(max_digits=18, decimal_places=2)
>
> Then, in django 1.7
>
> >> obj = ModelWithDecimalField.objects.first()
> >> obj.price
> >> Decimal("1990.00")
>
> In django 1.8
>
> >> obj = ModelWithDecimalField.objects.first()
> >> obj.price
> >> Decimal("1990")
>
>
> So, I don't know where look to found this change. What change between 1.7
> and 1.8
> Maybe I forget to implement something in django-firebird 1.8
>
>
> Thanks in advance
> Maxi
>
>
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/538ec818-854f-475b-be7c-5078f240073d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
