Ok, seems like nothing to do then - please consider publishing a version
that works with Mezzanine at some point though!
On Mon, May 25, 2015 at 9:21 PM, vikraw wrote:
> here is the link -
> https://github.com/payu-india/PayU-Integration-Kit-Django
> But that package didn't work out of the box a
here is the link - https://github.com/payu-india/PayU-Integration-Kit-Django
But that package didn't work out of the box and it needed lots of tweaking.
So that statement must have been introduced then, as their code doesn't has
that. Payu-India support for django is not very extensive and as a s
Well you've resolved it for yourself but surely someone else will hit this.
So which payment processor was it?
On Mon, May 25, 2015 at 9:45 AM, vikraw wrote:
> Looks like it is resolved for now. One of the payment processor libs had
> getcontext().prec = 2. After commenting it out, things looks
Looks like it is resolved for now. One of the payment processor libs had
getcontext().prec = 2. After commenting it out, things looks ok. Once the
flow reached that code, i had issues.
But still not clear why it hasn't happening on dev environment
On Monday, May 25, 2015 at 2:46:19 AM UTC+5:30,
Is it possible that you are running with different versions of python
between the runserver and nginx/gunicorn versions of your website?
I've noticed before in other work that e.g. Python 2.7 has slightly
different precision on floats than Python 2.6...
But yeah, weird problem.
On 25/05/2015 3
The staged server have the locale correctly set ( see at end of my message
the settings).
Steps on my Staged server - Amazon Ec2 - Ubuntu 14
- stopped supervisor and nginx on my staged machine
- switched my staged machine to run using - python manage runserver
0.0.0.0:8000
- put "printf value" s
It looks like you're calculating the correct value being stored in the DB,
and only getting the error on output. Each currency value gets passed
through the "currency" template tag, which is where the problem likely is.
It also deals with machine specific locale settings, which will vary per
machin
Hi
Almost near launching a site. But running into Price rounding issues today
when I fab deployed to AWS ec2 instance. Never had those issues before on
ec2.
My Development environment is working great with no issues.
However on deployed machine -Prices are getting rounded off in various
places
