Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#16496 closed Bug (needsinfo)

TypeError: float() argument must be a string or a number ON production server

Reported by: zealhua@… Owned by: nobody
Component: Core (Other) Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Hi All,

I'm using Django1.3 with Apache2.2 mod_wsgi3.3 python2.7.1 on Ubuntu . My Django Project is running very well on testing server(means with python manage.py runserver). However, when I move to production server and trying to test one complicated function, it's turn out to "TypeError, float() argument must be a string or a number"

Details error message is:

Django Version:	1.3
Exception Type:	TypeError
Exception Value:	
float() argument must be a string or a number
Exception Location:	/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py in get_response, line 111
Python Executable:	/usr/bin/python
Python Version:	2.7.1

/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py in get_response

                if response is None:
                    try:
                        response = callback(request, *callback_args, **callback_kwargs) #error reporting line

Does anyone knows how to solve it, I guess there is something bug in mod_wsgi3.3 ?

Change History (2)

comment:1 Changed 4 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to needsinfo
  • Status changed from new to closed

Could you post the full traceback? We need it to determine if the error occurs within Django or in your code.

comment:2 Changed 4 years ago by zealhua@…

the only traceback message is:

/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py in get_response

                if response is None:
                    try:
                        response = callback(request, *callback_args, **callback_kwargs) #error reporting line

No more, it's really strange, if there was more traceback information, I can track what's wrong in my project on earth. Unfortunetly, it's not. Only one line listed as above.

However, everything is working well under testing enviroment. Anyway, I will try to dig out it in my side. And report it to you if I got the truth, thank you for your effort!

Note: See TracTickets for help on using tickets.
Back to Top