#django

carljm: The tutorial first shows a rather clumsy way of doing it and afterwards the shortcut.

The tutorial demonstrates the individual steps (create a context, render a template, return the response) so that you know how what the process is.

Rather than only showing you the shortcut without you ever learning what the shortcut actually does.

mattmcc: It seems just neater syntax.

empedokles78: It is neater syntax. But it's useful to know the individual steps and components, because sometimes you need to do something different (e.g. render a template and don't place the resulting string into an HTTP response).

Using a calculator is easier than doing long division. That's not a reason to skip teaching long division in schools.

In this case, knowing how render() works is important, it's part of understanding the whole HTTP request/response cycle.

carljm: It's not that this steps are tought in an understandable way for that sake.

"render a template and don't place the resulting string into an HTTP response" - Do you mean for a PDF or something?

can I add a through field to a many-to-many field that already exists?

would a migration pick it up properly

Why is "request" used? Is there an instance where request isn't part of the cycle?

Context processors require a request object as an argument.

And render() uses RequestContext by default to run context processors.

mattmcc: An the second question?

If you aren't handling a request, then you wouldn't be using render() anyway.

Hm. Then the render method could be made cleaner.

The shortcut? It's two lines of code.

The render method. It could only take the template and a context as arguments.

As in bottle: "return template('<b>Hello {{name}}</b>!', name=name)"

It needs the request for context processors. If you don't want to use context processors, there's render_to_response.

Cleaner code..

Eh, that's debatable.

2 instead of 3 arguments.

return render_to_response('foo.html', context)

Already exists. In fact it predates render().

Okay, shorter code. :) Does the tutorial explain what a context processors is?

No, but the template guide which the tutorial links directly to does.

in 1.7 it should be allowed to squash migrations that are needed by other squashed migrations, right? i squashed app1 migrations which had a dependency on app2 migrations… when i try to squash app2 migrations i get KeyError app1.0001_squashed… dependencies reference nonexistent parent node (app2, …) ?

Uh what? ImportError: No module named hmac.urls

What's the template engine with the least verbosity?

Python's format strings are pretty terse. :P

DarkSector: Do you happen to have an hmac module in your code that's blocking you from the stdlib package?

nope

What's hmac.__file__ say in a shell?

there isn't an mac file

*hmac

django-registration==1.0 doesn't have hmac module

and that is the stable one

Maybe I should be using django-registration-redux?

mattmcc: Something like http://bottlepy.org/docs/dev/stpl.html :)

empedokles78: Django as of 1.8 supports writing support for third party template engines, so you're welcome to write an adapter to use that engine with Django.

mattmcc: Way over my head.

But maybe there is something in the same vain already?

DarkSector: Ah, yeah, registration 1.0 certainly wouldn't support current Django versions. So redux would work. Although workon django-registration proper has resumed recently. http://www.b-list.org/weblog/2015/aug/13/django...

empedokles78: You can look around, but I wouldn't bet on it. Between the native engine and Jinja, it seems most people go with one or the other.

mattmcc I have a very small app with restricted user creation. Isn't there a way to get a simple user password set using password reset?

https://www.djangopackages.com/grids/g/template... might be a good starting point.

DarkSector: There is a UserCreationForm that you can use in your view..

I was kinda hoping for a signal that sends out an email that allows a user to set his password

so post_save on User

Sure, you could do that. Although you probably wouldn't want to send that email for every possible way that a user object gets created..

Like, in a shell. >>> User.objects.create(...)

good point

Thanks, mattmcc.

so maybe just via view

Hello, I'm getting NoReverseMatch error, even though I think I match the name fine: http://pastebin.com/xS2wkXmE. Any help appreciated

d3ngar: Your kwarg values don't match the regular expressions.

uidb64 of MQ does not match [0-9A-Fa-f]+

I think you have the arguments the wrong way around in your context.

I'm going to switch uidb64 and tiken in the uRL

What does your view look like? It's likely to be there that the problem exists.

I'm trying to use the default view

From django.contrib.auth.views.password_reset_confirm

when I paste the values in the URL the page renders fine

Instead of the {% url %} stuff, can you try:

Someone knows of a Swiss Django-Freelancer?

uid: {{ uid }} / token: {{ token }}

d3ngar: And see what that does?