#django

luminous: Also paste the url you're using please.

Y3K: almost: https://bitbucket.org/ubernostrum/django-regist...

Y3K: the url pattern?

luminous: Yes.

Yay! Django 1.5!!! ummm, what happened to django.views.generic.simple.direct_to_template?

Derailed: it's been deprecated for quite some time now

Derailed: use django.shortcuts.render instead

Y3K: url(r'^new_user/$', new_user_landing_page, name='new_user_landing_page'),

luminous: There you go! You aren't accepting any arguments in your urls

I never saw notification that it was deprecated, and I can't find it in the backwards-incompatible changes in the 1.5 release notes.

Derailed: ALL of the old function-based generic views were deprecated when CBVs landed... now, two versions later, they've been yanked

FunkyBob: Hello mate :)

Y3K: !

Y3K: that's why i asked about 23:26 < luminous> is it possible to use redirect() without issueing a 30x? eg.. call the view directly, as if it were just another view in the processing chain?

hey question about django 1.4

they were deprecated in 1.3

reduxdj: mmm?

luminous: that's not a redirect

In django 1.5, if I set AUTH_USER_MODEL, would I still import the model by django.contrib.auth.models.User?

luminous: you can return the response from another view, if you like...

i am getting server errors, and I have the cookie from my error log

Y3K: what should the url be? why doesn't redirect just cll the view directly..

FunkyBob, god damnit. that's a whole section of the documentation that I hadn't noticed because I thought the release notes would cover it

luminous: because redirect is a HTTP REDIRECT

how can I try to find the session, want to see who was trying to buy something and got "undefined" from javascript

grr, ARGH

Derailed: they did.... WHEN IT WAS DEPRECATED

FunkyBob: i understand, but it would seem sensible that there are three types of redirects, 301/302 and then one view to another

to me at least

luminous: Try r'^new_user/(?<arg>[\w]+)/$'

luminous: when a view calls another view... that's NOT a redirect

you do not need to get so worked up

luminous: well, I need to try _something_ to get the message through

i get your message

and I'm not contending it :)

FunkyBob, so this file: https://docs.djangoproject.com/en/1.5/internals... Do I just need to go through that list and make sure we're not using any of it before migrating to 1.5?

FunkyBob: thank you for clarifying

Y3K: thank you for working through that with me :)

luminous: well, here's the crux-- when one view returns the result of another view.. do not call it a 'redirect'

FunkyBob: How should it be called then?

luminous: You're welcome.

Derailed: probably best to go through all of the release notes for the last couple of versions, to be sure

Y3K: 'returning the result of another view'

FunkyBob: Hahaha, got it mate. Thanks

'redirect' has a fairly solidly established meaning in the context of web

It's indeed, just wonder if there was some "convennion" about the other thing.

Y3K: what do you call it when your function returns the result of another function?

sometimes we refer to such views as 'wrappers'.... a practice more common with function based generic views

yo funky bob, anyway to pull the session id from a cookie in my log?

FunkyBob: Don't know... Everytime I've used nested functions were only with utils / decorators, not "redirecting to another view".

Haha actually FunkyBob, I might just be using 'direct_to_template' in just one place -- it just made 75 tests fail :-)

I've failed with it but... Is there a way to override the "parent class" model's fields? I know it isn't possible re-declaring the field but maybe in the __init__method? Also, I don't want to override the entire field, just append a validator (at model leve).

*level

Derailed: heh... well, render() is a near drop-in replacement

So I'm upgrading my site to use django 1.5 - if I set DEBUG to False, i get Server Error (500) with no output to the console :( however it works fine when debug is true

I'm not even sure how to start looking for the problem.

Zer000: Do you have a 404 and 500 templates

??

just 404

Zer000: Create the another one.

Django 1.5 doesn't require those anymore.

man. if its crapping out silently because it was missing 500.html - thats gotta be a bug right?

When DEBUG is False, the place to find error information is your error log.

mattmcc: I didn't knew that... Good to know though :P

Zer000: I don't know, when I deployed apps to Heroku if I didn't create the 404 and 500 templates it just crashed :P

one of these days I'm going to remember who it was in .jp was going to help with with order/invoice system design... :/

well, good, because i created a 500 template, and it gives me the same error, but now with my fancy template

guess I should just corder my friend with a Masters in accounting

Right, in the past it'd look for 404.html when a 404 was raised. Failing to find one, that would cause a TemplateDoesNotExist (an exception, so a 500 response)

mattmcc, but i have a 400 and 500 template now, its giving me 500 but nothing in console.

wat do?

mattmcc: Check in your settings for if DEFAULT: estatements :)

Zer000: Sorry, the last message was for you :P

oh

Y3K, I don't understand

check for waht?

Zer000: if you disable DEBUG then nothing will be printed to the console

Zer000: Check if you have "if DEBUG" (sorry) statements in your project, maybe one of those is breaking it.

Y3K, I don't for a fact

kklimonda, well how can I debug then?

sounds silly, but like I said there are no problems when debug is on

Zer000: change the logging behaviour in settings

ah ok

for many to many mappings, can there be meta data associated with the keys in the table?

pzuraq: Hmm... Maybe the through option can help you.

I want to have a "relationship type" for each mapping

hmm, through

Could it be this "DeprecationWarning: django.conf.urls.defaults is deprecated"?

Zer000: AFAIK a deprecation warning shouldn't take down a non-DEBUG site :P

Y3K: perfect, exactly what I need, thanks :)