Re: TypeError: 'CharField' object is not callable

On Monday 04 January 2010 23:54:13 Marc Aymerich wrote: > ... > take a look at middle_initial of woman class ;) Thank you very much for the fast and accurate response. Now it worked without problem. signature.asc Description: This is a digitally signed message part.

Re: TypeError: 'CharField' object is not callable

.py", > line 74, in load_app >models = import_module('.models', app_name) > File "/usr/lib/python2.6/site-packages/django/utils/importlib.py", > line 35, in import_module >__import__(name) > File "/home/~/../project_name/app_name/models.py", line 12, in > &g

TypeError: 'CharField' object is not callable

ls/importlib.py", line 35, in import_module __import__(name) File "/home/~/../project_name/app_name/models.py", line 12, in class Woman(models.Model): File "/home/~/../project_name/app_name/models.py", line 19, in Woman cell_phone = models.CharField(max_length=20) TypeE

Re: Just upgraded to 1.1, can't start development server, TypeError

.options import ModelAdmin, HORIZONTAL, > > > > > VERTICAL > > > > >  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ > > > > > python2.6/site-packages/django/contrib/admin/options.py", line 5, in > > > > > >

Re: tiny_mce TypeError

47 PM, neridaj <neri...@gmail.com> wrote: > > > I'm just following "Practical Django Projects" and was curious if > > > anyone else was able to fix a TypeError when trying to add tiny_mce to > > > the admin for flatpages, or is this something buried in the &

Re: tiny_mce TypeError

was curious if > > anyone else was able to fix a TypeError when trying to add tiny_mce to > > the admin for flatpages, or is this something buried in the > > tiny_mce.js file? > > Compare to this, which is the canonical version (and which worked > locally for me on 1.1

Re: tiny_mce TypeError

On Tue, Nov 10, 2009 at 9:47 PM, neridaj <neri...@gmail.com> wrote: > I'm just following "Practical Django Projects" and was curious if > anyone else was able to fix a TypeError when trying to add tiny_mce to > the admin for flatpages, or is this something buried

tiny_mce TypeError

Hello, I'm just following "Practical Django Projects" and was curious if anyone else was able to fix a TypeError when trying to add tiny_mce to the admin for flatpages, or is this something buried in the tiny_mce.js file? (r'^tiny_mce/(?P.*)$', 'django.views.static.serve', { 'dc

Re: Just upgraded to 1.1, can't start development server, TypeError

; > > >    from django.contrib.admin.options import ModelAdmin, HORIZONTAL, > > > > VERTICAL > > > >  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ > > > > python2.6/site-packages/django/contrib/admin/options.py", line 5, in > &

Re: Just upgraded to 1.1, can't start development server, TypeError

ry/Frameworks/Python.framework/Versions/2.6/lib/ > > > python2.6/site-packages/django/contrib/admin/options.py", line 5, in > > > > > >    from django.contrib.contenttypes.models import ContentType > > >  File "/Library/Frameworks/Python.framework/Version

Re: Just upgraded to 1.1, can't start development server, TypeError

python2.6/site-packages/django/contrib/contenttypes/models.py", line > > 1, in > >    from django.db import models > >  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ > > python2.6/site-packages/django/db/__init__.py", line 57, in >

Re: Just upgraded to 1.1, can't start development server, TypeError

from django.db import models > File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ > python2.6/site-packages/django/db/__init__.py", line 57, in >'TIME_ZONE': settings.TIME_ZONE, > TypeError: __init__() takes exactly 1 argument (2 given) > >

Just upgraded to 1.1, can't start development server, TypeError

_.py", line 57, in 'TIME_ZONE': settings.TIME_ZONE, TypeError: __init__() takes exactly 1 argument (2 given) Everything worked fine in 1.0.4 before the upgrade. Seems like it may be an obvious upgrade problem/oversight on my part. Any ideas? --~--~-~--~~~---~-

Re: TypeError: save() got an unexpected keyword argument 'profile_callback'

Beautiful! Thanks for this very concise response. It helped greatly. Gloria --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To

Re: TypeError: save() got an unexpected keyword argument 'profile_callback'

in register >new_user = form.save(profile_callback=profile_callback) > > TypeError: save() got an unexpected keyword argument > 'profile_callback' > > I can't find build/bdist.linux-x86_64/egg/registration/views.py on my > system, strangely enough. Is this portion of Django

Re: TypeError: save() got an unexpected keyword argument 'profile_callback'

Some logging debug, placed in /usr/local/lib/python2.6/dist-packages/ django/core/handlers/base.py: import logging import pprint logging.error("Args: %s %s %s %s" % (pprint.pformat (callback),pprint.pformat(callback_args),pprint.pformat

TypeError: save() got an unexpected keyword argument 'profile_callback'

t_response response = callback(request, *callback_args, **callback_kwargs) File "build/bdist.linux-x86_64/egg/registration/views.py", line 148, in register new_user = form.save(profile_callback=profile_callback) TypeError: save() got an unexpected keyword argument 'profile_callback'

Re: TypeError: execute() takes at most 3 arguments (4 given)

WHERE a = %s AND b = %s ", > [string1],[string2]) > > gives me the following error: > > TypeError: execute() takes at most 3 arguments (4 given) > > Where did i go wrong? --~--~-~--~~~---~--~~ You received this message because you are sub

Re: TypeError: execute() takes at most 3 arguments (4 given)

On Aug 22, 9:14 pm, kevin <kevin.sangh...@gmail.com> wrote: > cursor.execute("SELECT a,b,c FROM Table_Name WHERE a = %s AND b = %s ", > [string1],[string2]) > > gives me the following error: > > TypeError: execute() takes at most 3 arguments (4 given) >

TypeError: execute() takes at most 3 arguments (4 given)

cursor.execute("SELECT a,b,c FROM Table_Name WHERE a = %s AND b = %s ", [string1],[string2]) gives me the following error: TypeError: execute() takes at most 3 arguments (4 given) Where did i go wrong? --~--~-~--~~~---~--~~ You received this message b

Re: TypeError: 'module' object is not callable

uot;/Library/Python/2.5/site-packages/django/core/handlers/ > > > > > wsgi.py", line 228, in __call__ > > > > >self.load_middleware() > > > > > File "/Library/Python/2.5/site-packages/django/core/handlers/ > > > > > base.py&

Re: TypeError: 'module' object is not callable

>    self.load_middleware() > > > >  File "/Library/Python/2.5/site-packages/django/core/handlers/ > > > > base.py", line 47, in load_middleware > > > >    mw_instance = mw_class() > > > > TypeError: 'module' object is not callable > > > >

Re: TypeError: 'module' object is not callable

> > > > > File "/Library/Python/2.5/site-packages/django/core/handlers/ > > > wsgi.py", line 228, in __call__ > > >self.load_middleware() > > > File "/Library/Python/2.5/site-packages/django/core/handlers/ > > > base.py", line

Re: TypeError: 'module' object is not callable

>    self.load_middleware() > >  File "/Library/Python/2.5/site-packages/django/core/handlers/ > > base.py", line 47, in load_middleware > >    mw_instance = mw_class() > > TypeError: 'module' object is not callable > > [19/Jun/2009 14:09:22] "GET / HT

Re: TypeError: 'module' object is not callable

in load_middleware > mw_instance = mw_class() > TypeError: 'module' object is not callable > [19/Jun/2009 14:09:22] "GET / HTTP/1.1" 500 644 But what Middleware do you have installed - whats the settings.py value for middleware? It lo

Re: TypeError: 'module' object is not callable

/django/core/servers/ > basehttp.py", line 635, in __call__ >return self.application(environ, start_response) > File "/Library/Python/2.5/site-packages/django/core/handlers/ > wsgi.py", line 228, in __call__ >self.load_middleware() > File "/Libr

TypeError: 'module' object is not callable

go/core/handlers/ base.py", line 47, in load_middleware mw_instance = mw_class() TypeError: 'module' object is not callable [19/Jun/2009 14:09:22] "GET / HTTP/1.1" 500 644 --~--~-~--~~~---~--~~ You received this message because you are subscribed t

Re: TypeError : expected string or buffer when saving model object

in the data > table, saving another > instance of this object results in the following error: > > TypeError at /ci/userManagement/modify_request/ > > expected string or buffer > > Request Method: POST > Request URL:http://127.0.0.1:8000/ci/userManagement/modify_re

TypeError : expected string or buffer when saving model object

of this object results in the following error: TypeError at /ci/userManagement/modify_request/ expected string or buffer Request Method: POST Request URL:http://127.0.0.1:8000/ci/userManagement/modify_request/ Exception Type: TypeError Exception Value: expected string

Re: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

xt_Num) >>>>>     return slug_with_number >>>>> >>>>> >>>>> >>>>> Traceback: >>>>> >>>>>   File "", line 2, in >>>>>   File >>>>> "/Users/leehinde/D

Re: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

Users/leehinde/Documents/Clients/RecEnrollTNV/RecEnroll/recenrolltnv/../recenrolltnv/recenroll/models.py", >>>> line 314, in save >>>> self.Slug = buildSlug(start) >>>> File >>>> "/Users/leehinde/Documents/Clients/Rec

Re: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

>   File >>> "/Users/leehinde/Documents/Clients/RecEnrollTNV/RecEnroll/recenrolltnv/../recenrolltnv/recenroll/models.py", >>> line 20, in buildSlug >>>     next_Num = get_SequenceNumber(slug) >>>   File "/Library/Python/2.5/site-packages/django/db/tran

Re: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

>   File >> "/Users/leehinde/Documents/Clients/RecEnrollTNV/RecEnroll/recenrolltnv/../recenrolltnv/recenroll/models.py", >> line 20, in buildSlug >>     next_Num = get_SequenceNumber(slug) >>   File "/Library/Python/2.5/site-packages/

Re: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

ages/django/db/transaction.py", > line 223, in _autocommit > return func(*args, **kw) > File > "/Users/leehinde/Documents/Clients/RecEnrollTNV/RecEnroll/recenrolltnv/../recenrolltnv/recenroll/models.py", > line 14, in get_SequenceNumber > sn.Next_Sequence_Number

TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

n/2.5/site-packages/django/db/transaction.py", line 223, in _autocommit return func(*args, **kw) File "/Users/leehinde/Documents/Clients/RecEnrollTNV/RecEnroll/recenrolltnv/../recenrolltnv/recenroll/models.py", line 14, in get_SequenceNumber sn.Next_Sequence_Number

TypeError: coercing to Unicode: need string or buffer, ImageWithThumbnailsFieldFile found

add product and open home page i have this error TypeError: coercing to Unicode: need string or buffer, ImageWithThumbnailsFieldFile found --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" grou

Re: auth.contrib silently catching TypeError. Bug?

enticate will always be called with keyword >> arguments which isn't true. > > If you look at how django.contrib.auth.authenticate is implemented, > you'll see that it will *always* invoke the backend's authenticate() > keyword-style, which means an invalid argument set will *always*

Re: auth.contrib silently catching TypeError. Bug?

you look at how django.contrib.auth.authenticate is implemented, you'll see that it will *always* invoke the backend's authenticate() keyword-style, which means an invalid argument set will *always* raise TypeError. -- "Bureaucrat Conrad, you are technically correct -- the

Re: auth.contrib silently catching TypeError. Bug?

2 string arguments, the same will happen. > > I don't think you're understanding how keyword arguments work in > Python.  Python automatically raises a TypeError if the wrong keyword > arguments are passed to a function; based on argument name, not type. > So if "username" a

Re: auth.contrib silently catching TypeError. Bug?

ent code will call the user/password based authenticator and it > will pass in the token as a username (password will be null). If I > have an authenticator with 2 string arguments, the same will happen. I don't think you're understanding how keyword arguments work in Python. Python automati

Re: auth.contrib silently catching TypeError. Bug?

ones.) The current implementation assumes that TypeError can be raised only by the call to authenticate(**credentials) method (which isn't true) and also that it will always be raised if the wrong credentials are passed in. We already discussed the first assumption, but the second assumption

Re: auth.contrib silently catching TypeError. Bug?

On Mon, Apr 20, 2009 at 4:20 AM, Tamas Szabo <szab...@gmail.com> wrote: > As you can see the code catches and silently ignores all TypeError exceptions: > The problems with this approach are: >    - Why not fail as early as possible if one of the authentication > b

Re: auth.contrib silently catching TypeError. Bug?

gt; 32          """ > 33          If the given credentials are valid, return a User object. > 34          """ > 35          for backend in get_backends(): > 36              try: > 37                  user = backend.authenticate(**credentials) > 38    

auth.contrib silently catching TypeError. Bug?

nds(): 36 try: 37 user = backend.authenticate(**credentials) 38 except TypeError: 39 # This backend doesn't accept these credentials as arguments. Try the next one. 40 continue 41 if user is None: 42 conti

Re: Negative value in forms.Integerfield throws TypeError

On Mon, Feb 16, 2009 at 4:26 AM, coan <a.ne...@gmail.com> wrote: > > I'm validating a form, and use forms.IntegerField(min_value=0,). > > If I submit a -1 value in that field, it throws a TypeError: not all > arguments converted during string formatting. > H

Negative value in forms.Integerfield throws TypeError

I'm validating a form, and use forms.IntegerField(min_value=0,). If I submit a -1 value in that field, it throws a TypeError: not all arguments converted during string formatting. How come it doesn't raise a forms.ValidationError, and how should I catch a negative value in this field

Re: TypeError: 'tuple' object is not callable

> File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py", > line 200, in _get_urlconf_module >self._urlconf_module = __import__(self.urlconf_name, {}, {}, ['']) > > File "c:\projects\iFriends\..\iFriends\urls.py", line 17, in >(r'^admi

Re: TypeError: 'tuple' object is not callable

On Fri, 2009-01-23 at 23:37 +1300, joti chand wrote: > Hi Guys, I was doing to the tutorials from the book: Teach yourself > django in 24 hours and Part1 hour 3 ...to view the admin site it is > giving the following error. That book was published before Django 1.0 was released and, in

Re: TypeError: 'tuple' object is not callable

\Python25\Lib\site-packages\django\core\urlresolvers.py", > line 200, in _get_urlconf_module >self._urlconf_module = __import__(self.urlconf_name, {}, {}, ['']) > > File "c:\projects\iFriends\..\iFriends\urls.py", line 17, in >(r'^admin/', include('django.contr

TypeError: 'tuple' object is not callable

quot;c:\projects\iFriends\..\iFriends\urls.py", line 17, in (r'^admin/', include('django.contribute.admin.urls')), TypeError: 'tuple' object is not callable --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: TypeError: Related Field has invalid lookup: icontains

2009/1/22 Karen Tracey : > Ah, you have in your search_fields for SchedaBilancioGenereOptions > 'impresa', which is a ForeignKey. You need to specify what field within the > related model you want to search, so 'impresa__fieldname'. (If there are > multiple fields you need

Re: TypeError: Related Field has invalid lookup: icontains

On Thu, Jan 22, 2009 at 3:01 AM, Alessandro Ronchi < alessandro.ron...@soasi.com> wrote: > > 2009/1/21 Karen Tracey : > > > Egads, they're huge. Any way you could cut that down to a small failing > > example? Or at least mention which model you are trying the search on? > >

Re: TypeError: Related Field has invalid lookup: icontains

2009/1/21 Karen Tracey : > Egads, they're huge. Any way you could cut that down to a small failing > example? Or at least mention which model you are trying the search on? > Also a traceback instead of just the last error message would probably help, > as it might give some

Re: TypeError: Related Field has invalid lookup: icontains

> >> When one tries to make a search in admin with a model table he gets this > >> error: > >> > >> TypeError: Related Field has invalid lookup: icontains > >> > >> is there anyway to solve it and make it returns nothings instead of 500 > &g

Re: TypeError: Related Field has invalid lookup: icontains

2009/1/21 Karen Tracey <kmtra...@gmail.com>: > On Wed, Jan 21, 2009 at 10:21 AM, Alessandro Ronchi > <alessandro.ron...@soasi.com> wrote: >> >> When one tries to make a search in admin with a model table he gets this >> error: >> >> TypeEr

Re: TypeError: Related Field has invalid lookup: icontains

On Wed, Jan 21, 2009 at 10:21 AM, Alessandro Ronchi < alessandro.ron...@soasi.com> wrote: > > When one tries to make a search in admin with a model table he gets this > error: > > TypeError: Related Field has invalid lookup: icontains > > is there anyway to solve it a

TypeError: Related Field has invalid lookup: icontains

When one tries to make a search in admin with a model table he gets this error: TypeError: Related Field has invalid lookup: icontains is there anyway to solve it and make it returns nothings instead of 500 error? -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI

Re: TypeError when using direct-to_template

Thank you RD! My own stupid mistake, I have to say, I was editing the backup file instead of the live file. I'm sorry I wasted your time. I can view my html now :) Now, I have to read and search more to sort out why my external css is not working :S

Re: TypeError when using direct-to_template

On Jan 2, 10:16 am, SG_Muse wrote: > Thank you very much for your quick answers gentlemen! > > I removed the quotes, but that lead into another problem; > TemplateSyntaxError Could not parse the remainder: ' name' from > 'project name' > I copied the

Re: TypeError when using direct-to_template

Thank you very much for your quick answers gentlemen! I removed the quotes, but that lead into another problem; TemplateSyntaxError Could not parse the remainder: ' name' from 'project name' I copied the traceback: http://dpaste.com/104542/ I hope you can help me once again :)

Re: TypeError when using direct-to_template

include('django.contrib.admindocs.urls')), > ># Uncomment the next line to enable the admin: >(r'^admin/(.*)', admin.site.root), > ) > > ----- > When I try to acces the root (http://127.0.0.1:8000/), then it comes > up with a Ty

TypeError when using direct-to_template

(r'^admin/(.*)', admin.site.root), ) - When I try to acces the root (http://127.0.0.1:8000/), then it comes up with a TypeError, 'str' object is not callable. In the local vars it refers to direct_to_template. I h

Re: in db/models/query.py - TypeError: 'exceptions.IndexError' object is not callable

  File "/usr/local/src/wxcoder/observations/forms.py", line 257, in > ValidateGrossLimit >     e = Element.objects.get(elementID=e_id) > >   File "/usr/lib/python2.5/site-packages/django/db/models/manager.py", > line 93, in get >     return self.get_query_set().ge

in db/models/query.py - TypeError: 'exceptions.IndexError' object is not callable

File "/usr/lib/python2.5/site-packages/django/db/models/query.py", line 309, in get % self.model._meta.object_name) TypeError: 'exceptions.IndexError' object is not callable , POST:, COOKIES:{'__utma': '145837938.4275713312103283000.1230773473.1230773473.1230773473.1', '__ut

Re: i18n/setlang TypeError :(((

Thank you Karen :) My python install had some weird patches. Now everything works absolutely fine :) Thanks again :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send

Re: i18n/setlang TypeError :(((

lobalpath, [to_locale(lang_code)]) is not None: File "/usr/lib/python2.5/gettext.py" in find 437. for nelang in _expand_lang(lang): File "/usr/lib/python2.5/gettext.py" in _expand_lang 132. locale = normalize(locale) File "/usr/lib/python2.5/locale.py" in

Re: i18n/setlang TypeError :(((

Ok, I believe I've found a buggg ;) The problem is locale.translate can't handle utf encoded language code. To avoid doing so I needed to add "lang_code = lang_code.encode ('ascii')" to line 334 of django/utils/translation/trans_real.py. Could someone take a peek if this is right (things started

i18n/setlang TypeError :(((

for nelang in _expand_lang(lang): File "/usr/lib/python2.5/gettext.py" in _expand_lang 132. locale = normalize(locale) File "/usr/lib/python2.5/locale.py" in normalize 307. fullname = localename.translate(_ascii_lower_map) Exception Type: TypeError at /i18n

Re: TypeError at admin: unpack non-sequence

Daniel, you're a hero. I thought I'd tried it before and it hadn't worked, but I'd probably messed something else up in the process. It's working perfectly, thanks. Just got to sort out the /media/ issue now, but I'm fairly confident I can do that on my own! :D Thanks again, and it'd be great

Re: TypeError at admin: unpack non-sequence

On Dec 13, 6:43 pm, benw wrote: > I have the exact same problem with Django 1.0.2 Final on Debian Etch > (Apache 2.2.3-4+etch6 / mod_python 3.2.10-4) -- My settings.py, vhost > and urls.py are nearly exactly the same as above (the relelant parts > anyway.) > > On Dec 12,

Re: TypeError at admin: unpack non-sequence

I have the exact same problem with Django 1.0.2 Final on Debian Etch (Apache 2.2.3-4+etch6 / mod_python 3.2.10-4) -- My settings.py, vhost and urls.py are nearly exactly the same as above (the relelant parts anyway.) On Dec 12, 3:00 am, Bluemilkshake wrote: > Of

Re: TypeError at admin: unpack non-sequence

Of course. urls.py below: Underneath that is the relevant directives from my vhosts.conf file. Many thanks, -M --- urls.py --- from django.conf.urls.defaults import * # Uncomment the next two lines to enable the admin: from django.contrib import admin admin.autodiscover() urlpatterns =

Re: TypeError at admin: unpack non-sequence

On Dec 12, 9:41 am, Bluemilkshake wrote: > You're right DR, apologies. I did think it may be a syntax issue but > it appears not to be. > Would it matter at what position the admin reference appears in > INSTALLED_APPS? > > Below is the settings.py file being used.

Re: TypeError at admin: unpack non-sequence

; > > I've setup my first Django project to test, and when I request the > > root URL I get no problems, however after adding the admin app to my > > INSTALLED_APPS setting and running syncdb, I get the following: > > > TypeError at admin > > unpack non-sequenceRequ

Re: TypeError at admin: unpack non-sequence

> I've setup my first Django project to test, and when I request the > root URL I get no problems, however after adding the admin app to my > INSTALLED_APPS setting and running syncdb, I get the following: > > TypeError at admin > unpack non-sequenc

TypeError at admin: unpack non-sequence

no problems, however after adding the admin app to my INSTALLED_APPS setting and running syncdb, I get the following: TypeError at admin unpack non-sequenceRequest Method: GET Request URL: http://djangotest.bluemilkshake.co.ukadmin Exception Type: TypeError Exception Value: unpack non-sequence Exception

Re: Custom Middleware TypeError exception

o.contrib.auth.middleware.AuthenticationMiddleware') > > Traceback: > File "C:\Python26\Lib\site-packages\django\core\handlers\base.py" in > get_response > 86. response = callback(request, *callback_args, > **callback_kwargs) > > Exception Type: Type

Re: Custom Middleware TypeError exception

On Dec 5, 4:20 pm, Chris Smith <[EMAIL PROTECTED]> wrote: > Any ideas?  Is it something silly I've done? Actually, please ignore this. The exception was firing in user code due to me forgetting to handle a capture group in a URL regex. Back to the coffee machine... Cheers, Chris.

Custom Middleware TypeError exception

ib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware') Traceback: File "C:\Python26\Lib\site-packages\django\core\handlers\base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) Exception

Re: ModelForm fails with TypeError on save

On Oct 20, 12:28 pm, Daniel Roseman <[EMAIL PROTECTED]> wrote: > On Oct 20, 11:12 am, simong <[EMAIL PROTECTED]> wrote: > > > > >         if request.method == 'POST': > >                 orderform = OrderForm(request.POST) > >                 if orderform.is_valid(): > >                        

Re: ModelForm fails with TypeError on save

On Oct 20, 11:12 am, simong <[EMAIL PROTECTED]> wrote: >         if request.method == 'POST': >                 orderform = OrderForm(request.POST) >                 if orderform.is_valid(): >                         preorder = orderform.save(commit=False) >                         orderno  =

ModelForm fails with TypeError on save

I have a model like this: class OrderProfile(models.Model): cartid = models.CharField(max_length=128, null=True, blank=True) orderno = models.CharField(max_length=48, null=True, blank=True) userid = models.CharField(max_length=128, null=True, blank=True)

Re: TypeError: direct_to_template() got multiple values for keyword argument 'template'

Oh whoops, my bad. I forgot about positional arguments; thanks for the reminder. On Sep 15, 2008, at 4:04 PM, Malcolm Tredinnick wrote: > This URL pattern says to capture everything after "success" and that > is > then passed as the first positional argument to the view. That > argument >

Re: TypeError: direct_to_template() got multiple values for keyword argument 'template'

On Mon, 2008-09-15 at 16:02 -0700, Cortland Klein wrote: > Hi. I'm getting a TypeError on my direct_to_template url: > > direct_to_template() got multiple values for keyword argument 'template' > > urls.py: > > from django.conf.urls.defaults import * > >

TypeError: direct_to_template() got multiple values for keyword argument 'template'

Hi. I'm getting a TypeError on my direct_to_template url: direct_to_template() got multiple values for keyword argument 'template' urls.py: > from django.conf.urls.defaults import * > > urlpatterns = patterns('', > (r'^$', 'redacted.redacted.views.sessionform'), >

TypeError: __init__() got an unexpected keyword argument 'debug'

w) File "/home/korayta/public_html/astrolink.net/django/flup/server/ threadedserver.py", line 44, in __init__ self._threadPool = ThreadPool(**kw) TypeError: __init__() got an unexpected keyword argument 'debug' = Any help is appreciated. --~--~-~--~~---

Re: TypeError - unpack non-sequence

Aha, it was httpd.conf Because I am serving this django app from root I thought I could get away with - "PythonOption django.root /" which I realise now is stupid since that is exactly what django removes from the URL for portability. Fixed now. Thanks for all your help guys for pointing me

Re: TypeError - unpack non-sequence

e question but where do I make that adjustment? So to describe what's happening - any url save for the homepage is serving up the TypeError mentioned above. Just noticed something actually.. If I aim for http://www.mysite.co.uk/blog/ the TypeError responds with: Request URL:http://www.mysite.c

Re: TypeError - unpack non-sequence

On Wed, 2008-08-20 at 11:46 -0700, Alfonso wrote: > Interestingly changing /django/core/handlers.py line 77 from: > > request.path_info) > > to: > > request.path) > > Makes everything work again - hmm. No idea why though. So what you're saying is that if you introduce old bugs back into

Re: TypeError - unpack non-sequence

Interestingly changing /django/core/handlers.py line 77 from: request.path_info) to: request.path) Makes everything work again - hmm. No idea why though. Thanks Allan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: TypeError - unpack non-sequence

Hi Christan, Thanks for your reply - last version where everything worked was 8255, to be honest not 100% sure where to track the problem or whether it's 100% related to a svn update but I'm confident that the major change since last worked. Allan On Aug 20, 2:19 pm, Christian Joergensen

Re: TypeError - unpack non-sequence

Alfonso wrote: > Upgraded to latest svn trunk and now getting brand new error on every > page/url path save for homepage. Not entirely sure how to track down > the fault in configuration etc. Anyone help? Thankyou! Please specify the exact svn revision. Also, what revision was the last where

TypeError - unpack non-sequence

ponse 77. request.path_info) Exception Type: TypeError at /beauty-salons/ Exception Value: unpack non-sequence --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post

Re: ugh, TypeError: Cannot resolve keyword err ...

On Jun 20, 12:20 pm, Milan Andric <[EMAIL PROTECTED]> wrote: > This TypeError message always baffles me and is hard to debug. I'm > using SVN 6962 which means I should probably upgrade, but I tried that > a month or so ago around query-set-refactor merge and things were >

ugh, TypeError: Cannot resolve keyword err ...

This TypeError message always baffles me and is hard to debug. I'm using SVN 6962 which means I should probably upgrade, but I tried that a month or so ago around query-set-refactor merge and things were unhappy so decided to wait. TypeError: Cannot resolve keyword 'presentation' into field

Re: IntegerField with choices raising an TypeError

In the meantime I did the following: def save(self): try: self.score = int(self.score) except: pass super(Entry, self).save() --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: IntegerField with choices raising an TypeError

On May 22, 6:29 am, "Scott Moonen" <[EMAIL PROTECTED]> wrote: > I suspect your problem may be due to the fact that your display value for 3 > is a number rather than a string.  Try changing: > >    CHOICES = [(1, '1'), (2, '2'), (3, 3), (4, '4'), (5, '5')] > > to > >    CHOICES = [(1, '1'), (2,

Re: IntegerField with choices raising an TypeError

I suspect your problem may be due to the fact that your display value for 3 is a number rather than a string. Try changing: CHOICES = [(1, '1'), (2, '2'), (3, 3), (4, '4'), (5, '5')] to CHOICES = [(1, '1'), (2, '2'), (3, '3'), (4, '4'), (5, '5')] -- Scott On Wed, May 21, 2008 at

Re: IntegerField with choices raising an TypeError

Jashugan wrote: > Hello I have the following code in my model: > > class SomeMode(models.Model): > > CHOICES = [(1, '1'), (2, '2'), (3, 3), (4, '4'), (5, '5')] > > score = models.IntegerField(choices=CHOICES) > > > When I change the score in the admin interface it throws this error: > >

IntegerField with choices raising an TypeError

Hello I have the following code in my model: class SomeMode(models.Model): CHOICES = [(1, '1'), (2, '2'), (3, 3), (4, '4'), (5, '5')] score = models.IntegerField(choices=CHOICES) When I change the score in the admin interface it throws this error: an integer is required I think

<    1   2   3   4   5   >