#django

im overriding the User model in a test, would i have to patch calls to get_user_model from outside of the testcase? say that i'm importing a attribute from my app's utils.py who just return the name of the field set on the User model by USERNAME_FIELD, now since i have overriden the User model to one that uses the field name 'email' i try an assertEqual on 'email' and the value imported, the assertion fails and says that it is

also im supposed to be selectively adding a field to a form if this attribute is not 'email' but when i assert that the field is not in form.fields it fails, does the override setting not effect calls to get_user_model outside of the test method?

djapo: Provided that you have correct test config everything should just work.

FunkyBob: not that I can remember, nope. why do you ask?

jtiai: it's not right now im venturing into the world of mock.patch which makes me fear that i might be hidding a problem by doing so

djapo: Then you might be doing something wrong...

jezdez: a project I've recently taken over... a cow-orker added it, and now tests are barfing in, it seems, creating test DB

jtiai: im just doing self.assertNotIn('username_field', test_form.fields) in the method that is supposed to have the user overriden, the test_form is a form that selectively sets a field named username_field if the USERNAME_FIELD is not email ... and the user model that overrides just happens to have that set to 'email' which means that the field should not be there, but it fails

djapo: How do you construct that form?

jtiai: just a regular form with one field in the block of an if statement, if _username_field is not 'email':,

Good morning. I'm having a little problem adapting the polls tutorial to my needs :( Could maybe someone take a look at this: https://gist.github.com/Gixxa/9885946 and tell me how I can write a view so that I can vote? It should be placed into the "lernbaustein" view if possible, or will that not work?

djapo: Have you checked at which point that if-clause is executed?

Gixxa: you're really passing the titles in the URL pattern?

jtiai: _username_field should be getattr of get_user_model USERNAME_FIELD, which since i have overriden in the test i would expect to be 'email' but the fact that my assertion fails tells me that the if statement must be evaluating true, and the if statement should be evaluated after the form is instantiated

FunkyBob: yes

sounds ... hazardous, at best...

what will you do about url unfriendly characters?

you might want to spend some time reading up about Slugs

FunkyBob: It's always the same

the only difference are numbers

Gixxa: urlquote the titles

djapo: Can you show the actual code?

djapo: ?

jtiai: ill try dpaste, gimme a minute

Gixxa: so which part of the process has you stumped?

FunkyBob: the actual casting of the vote

I see ma data and the form but when I press the "Lernbaustein Bewerten" nothing happens since I don't have a vote view

ma = my*

jtiai: http://dpaste.com/1765605/ here it is

djapo: well does "User" point to correct model in your test?

djapo: Ah. It doesn't. :)

djapo: problem is that your form is imported _before_ swapped usermodel takes in place.

djapo: I bet your .utils does pick things on first import as well.

jtiai: should i imported inside the test method, would you like to see utils?

djapo: Yes please share utils as well.

jtiai: here it is http://dpaste.com/1765617/

Though I guess that doing import inside test method would get around the problem. And apparently answer is "yes", your _username_field is resolved only on initial import. So dynamic swap what you do in your test just doesn't work.

djapo: It could work if you would do runtime get_user_model().

absolutely deplorable noob question:

i come from php

there every site was automatically displayed under the server root

and i could define an index

jtiai: i figure it would work at runtie but why isin't it working in my tests, why django?

how do i achieve that 127.0.0.1/foo.html will match my foo.html template?

_Cody: Bascially you don't.

_Cody: All urls in Django are resolved to views. Which in turn may use templates to render something.

_Cody: I suppose you did tutorial?

yep, with views

_Cody: jtiai what about a sitemap

yet didnt get the transition to the template engine

i know a simple static/template setup from flask

djapo: Because you're resolving usermode one that is in effect when you import .utils file very very first time.

_Cody: So you did Django tutorial?

jtiai: is there a lazy way to resolve the user model?

djapo: Only by using function that calls get_user_model() everytime it's called.

will try that

djapo: Same goes for your "User=..." usage in forms file. It will take whatever you had effective in your settings when that file is first time imported.

jtiai: i do the django book

_Cody: What book?

_Cody: don't go near that

it's old, it's very out-dated -- the front page even carries a warning -- and it has some questionable content

_Cody: Do django tutorial from django documentation first.

_Cody: but the idea of request paths mapping directly to templates is very limiting...

this ?? https://docs.djangoproject.com/en/1.4/intro/tut...

_Cody: Of course you should pick one for your version of framework. 1.6 suggested.

_Cody: surely you're not using django 1.4? [oh, let me guess- you're using the version packaged with your OS?]

_Cody: otherwise, yes, that tutorial

hello! I'm trying to run my test suite but it says 'Ran 0 tests'. My app is inside INSTALLED_APP, my app dir does have an __init__.py, a models.py and a tests.py

_Cody: virtualenv and virtualenvwrapper will make your life much easier in the long run. Pays off to learn how to use them.

_Cody: takes about 1 minute to learn how to use virtualenv [bit longer for virtualenvwrapper... I've not bothered yet]