#django

(well, for it to have the intended effect, that is)

karanlyons: thanks for the tip above.

ah, think I may have figured it out

asantos22: Couple things (may not fix your issue)

1) @receiver(post_save, sender=Book)

ah, thankya

karanlyons: I think my issue was a for loop in the wrong if statement

2) def assign_user_points(sender, instance, created, raw, using, update_fields): (I know you've got **kwargs, but these are all the kwargs you'll ever get, and there aren't that many, so I'd prefer to list them)

karanlyons: isn't this the same of post_save.connect(...)?

asantos22: Might be, didn't get very far :D

mstrcnvs: Pretty much, but it's more Django-y.

decorators are black magic

No they're not.

They're functions that take and return functions.

Simple.

And most the time straight forward

Actually, I'd kinda prefer decorators for Django admin registration and the like. Do they exist?

don't get me wrong here, but I was kidding with you

Oh, my bad.

I know what decorators are heh

just like Python is THE BEST LANGUAGE EVER, decorators are black magic!

just kidding :)

If you *really* want black magic, start messing around with stuff like __slots__.

As far as scripting languages go, Python is pretty rad. Also true for languages in general, in cases.

Is xian still maintaining typogrify? There's a pull request a year old.

s/xian/xian\/mintchaos/

tbaxter: I might take some time to build out tests for that update_fields mixin for Django, cause why not. Naming thoughts? Right now it's SaveOnlyChangedFields, which is...fine, but django-saveonlychangedfields is a hell of a thing to have to type.

s/build out tests for/build out tests and properly release/

no opinion. Not sure what you mean, acutally.

Also, typogrify: https://github.com/chrisdrackett/django-typogrify

Oh my god, updated 8 days ago. I'm jumping ship.

Note somewhere along the line load typogrify changed to load typogrify_tags

Also: http://djangosnippets.org/snippets/2985/ (I'm asking you since your names are good.)

It's rather trivial, but someone asked for tests, and if I'm writing tests I better be releasing the thing somewhere.

That is a really outdated titlecase module, though.

SaveTheChange

Damn, that's good.

that journalism degree comes in handy some days.

Haha, I've got a theatre degree, which comes in handy almost never (outside of theatre, obviously).

I'm trying to send data to a form's custom clean() function, and now instead of validating, it just emptys the form... take a look? http://pastebin.com/RJFxqrjc

I have a view which is throwing an error. that part is fine. however, in addition to that error, django.request also throws an error about the request being forbidden due to missing the CSRF cookie. this is strange, because the earlier error proves that the request is not, in fact, forbidden. probably relevant - I have the dispatch method decorated with @method_decorator(csrf_exempt).

Ataxis: I'm not sure, but I don't think clean() is meant to return.

I don't think I'd try thumbnailing in a form.clean() at all.

Ataxis: And you'd want to super().clean(self) at the end.

Most of that should be in your Model.save(), though.

knite: Is the decorator on your receiving view, or your sending view?

(Also, isn't it just `@csrf_exempt`?)

hmm ok.. I prolly don't really understand how the clean() works, I thought it was where you made sure all form fields are valid. the thumbnail is mostly to check if the image is uploaded...

karanlyons: I'm not sure what you mean, I have exactly one view. it inherits from View and braces.views.JSONResponseMixin.

knite: So that's the view receiving the POST request? Try swapping out your decorator for just @csrf_exempt.

from django.views.decorators.csrf import csrf_exempt

karanlyons: that's right, it's the view receiving the post. according to the CBV docs, @method_decorator is the correct way to apply csrf_exempt (or other decorators) to a View.

but I'll try your suggestion now regardless. :-)

Oh, CBVs...

Yeah, that's why there's a dispatch method.

My bad.

(In general, most problems here are of the "seen it before, it's that one line" variety. So I sometimes forget to look around.)

knite: So that's not the problem, I'd think. dpaste your code?

karanlyons: No worries, I do the same thing. Any thoughts on what might be happening here? I'm on Django 1.5. The actual view error is being thrown in my post() method, which is by definition after the CSRF check. So I'm totally stumped as to why Django would throw a CSRF error after executing that method.

I'll get the paste up.

If you can post the code plus error (and traceback if there is one), I'll try to help you out. I've been spending most of my time on this project on the backend, though, so we'll see how much use I can be.

Hi there. I followed https://docs.djangoproject.com/en/1.5/topics/i1... but TypeError: __init__() got an unexpected keyword argument 'localize' was thrown.

I did this: amount = models.DecimalField(verbose_name=_('Amount'), max_digits=12, decimal_places=2, validators=[validate_amount], localize=True)

hello django!

Tjati_: What version of Django are you running?

karanlyons: 151.

Okay, so I've gotten a bit more insight as to what's going on with the post_save. It keeps using data from the previous save for some reason. No idea why though. Wasn't a misplaced for loop after all. cc: karanlyons https://dpaste.de/CXjyt/

And USE_L10N = True is in your settings?

karanlyons: absolutly.

Huh.

I've got an infinite recursion problem that looks to be coming from django.utils.tree

With models set up like http://dpaste.com/1361234/, and using Django, uwsgi, and Tastypie, I get a traceback of http://dpaste.com/1361240/

Anybody here know anything about that module?

Tjati_: Uh...are you doing this in you model, or form? Because localize is for forms.

karanlyons: of course, a model.

karanlyons: https://dpaste.de/mmQov/ . my error log has a traceback for the actual error. that's followed by WARNING django.request - Forbidden (CSRF cookie not set.): /my_url, with no additional trace info.

Tjati_: Pretty sure it's meant for forms.

karanlyons: stupid mistake. thank you.

No problem, took me a bit to see it, too.

karanlyons: you're absolutly right; documentation said it, too.

asantos22: The hell? Taking a look now.

knite: Give me a sec, I'll take a look.

karanlyons: thanks you and I beg your pardon that i disturbed you.