#django

ok

a swift punch to the throat

ejb: get_success_url() takes self, and from there you should have self.form_class or self.get_form_class()

epicowl: perhaps you should check when you .save() to see if object is even saved.

tbaxter: yeah, but not the constructed form instance

are form values in cleaned_fields

or self.get_form()

ie, to get the cleaned data, you'd have to construct it again (or just pull it out of POST, because hey, it's already been validated ;o)

epicowl: I actually like to do an assertion to see if objects are saved first before doing anything else.

epicowl: if it's not saved, then try creating it using the django shell

atula: yeah I think it can't save because the table doesn't exist

atula: http://dpaste.com/1205394/

epicowl: do you use south for migration scripts?

yes

epicowl: perhaps you're missing a migration script somewhere.

try doing python manage.py migrate --list

or do a schemamigration --auto

must be missing something there

… by the way, are you recreating the… universe?

you're missing an app calls "bang"

or "god" depends on your belief

atula: the thing is that I have this models.py (used for test only) inside app/content/tests/models

lol

thats the structure

er

tests/__init__.py, tests/test_forms.py, tests/models.py

test_forms.py imports the TestRelation model from the models.py to use in the test (I do this because I needed to make a mock model to use in this case)

epicowl: why do you have models used for testing only?

epicowl: oh that is odd. I have never needed to have models in tests

Siecje: because the model used in the project is in another project that is layered on top of the project Im working in

ah I see.

and the base model in the project I'm working in is an abstract model

oh boy. that is tough

you may need to do "migration" manually?

tbaxter: fwiw, here's what I have ended up with (ugh) for tracking the previous iterations: https://gist.github.com/kezabelle/0ea43ad2185ca...

unfortunately, my HTML is still coming out wrecked, so this'll be fun to try and figure out :D

kezabelle: I'm seeing closing LIs, but no opening?

yeah, that is happening outside the scope of that snippet

the tag seems to work correctly, assuming I can jiggle the HTML into the correct order ;)

all this just to avoid recursion :|

That's what I'm saying… you're closing LIs, but not opening them. Browser is probably guessing that you want to open, but missing one.

Course I haven't seen the output, so that's WAG

oh yeah, I'm well aware that it won't work with the output you see there, but the template it's in needs refactoring, and would only have muddied the situation :)

hey guys so I subclassed AbstractUser to add 2 fields - but now when I sync Django doesn't ask me to make an admin user or anything

do I have to redefine these methods? I thought AbstractUser would handle it

tsurantino: it won't prompt you for creation if you don't use the default model, just call create(super)user yourself

I'm really new to django, coming from ruby on rails. I've inherited a fairly large project, and I'm trying to write test for it. I have request = self.factory.get('/rbd/schedule/')

Then self.assertEqual(request.status_code, 200)

which keeps failing because the response is returning a 302

is it normal in django for every url to be a redirect?

of course not

jwa: can you be more specific?

It doesnt appear that way in the server logs when I do it manually in local.

does it require authentication or something?

tsurantino: I suppose you have changed AUTH_USER_MODEL? if so just call manage.py createsuperuser

kezabelle: normally, everything exists behind a login

ahh unrelated

rabbite: so why are you surprised you get redirected to the login? :)

I've found that response = self.client.get('/rbd/settings/', follow=True)

returns 200 though.

ls

bah

wrong window ;)

Think it might be because it's bouncing me to the login?

Indeed, hah.

rabbite: unless your test client is logged in, yes

(and the login is a 200, which is why following the redirect will get the 'correct' status_code, even though it's wrong)

Any resources where I can read up about writing test for systems behind a login?

I see, I suspected as much, but wasn't sure if it was a Django thing.

rabbite: just log the test client in. self.client.login(username, password), iirc

as I recall, factory doesn't authenticate (or have request, by default), which makes TestClient considerably easier to use.

jwa: so I have a foreign key that (apparently) can't be null. is there any way I can modify createsuperuser to give it some arbitrary value?

tsurantino: createsuperuser doesn't support fkeys, no

ok cool, thanks

__love__: Would I need to do that in every test? Or can I handle that in the setup?

rabbite: setUp() is for that, yes

Hm, thanks. I'll give those suggestions a try. Yet another reason I <3 freenode

atula: got it working… had to import the model in my __init__ file

rabbite: well not every channel's as friendly as #django ;)

epicowl: ah I see. good to know then!

def

I believe setupclass is even better.

tbaxter: for login?

I think so

tsurantino: You can override management commands, sure.

jwa: I'm a real newb to django, but it seems there is a rather large, supportive community around it

we try

Just put an app in front of auth that defines a createsuperuser command.