DjangoBot: #django

you are not able to help me, definitiely.

I wish you could explain

things properly

instead of

mashing the

enter button

and

ranting

its annoying

hard to follow

etc.

slooper:

slooper: anything you surround by parentheses is going to be passed.

subsume: yes, in this case you are completely right. however, it still doesn't resolve don't working test client.

DarwinSurvivor, ModelChoiceField takes a queryset, not a model

slooper: you can even get really creative and use a non-matching group to limit to options 'cat','dog',etc. but. I would not do this

slooper: instead, what I would do, is pass in your arg directlry

url('asdfasdf/cat/add','views.view',{'type': 'cat'})

igors: so use "MyModel.objects.all()"?

bluszcz: What is this business of something working in FF. What works in FF, and when?

subsume: I was hoping to avoid building a url for every model

slooper: you can use do animals/([^/]+)/add then

but keep in mind anyone can type anything in to animals/asdfasdfasdf

DarwinSurvivor, not possible, to avoid circular imports maybe you could pass None to queryset parameter, and set the real queryset in __init__ of your form, and just import your model there

subsume: gotcha - how do I get the dog, cat argument from the regex?

igors: ok I can do that, but is my queryset example correct?

slooper: I just showed you

subsume: it works with any browser, even if you run netcat, telnet with putting GET /show / HTTP/1.1... the problem is in the django.test.Client

DarwinSurvivor, yes, but you must pass the queryset itself, not a string

slooper: as you surely learned while reading the docs, parentheses capture and pass as args.

subsume: so many docs, so little time ;)

=).

so, anyone is using django.test.Client and checking a response.context or response.template in his tests?

bluszcz: stick a pdb in and start debugging

igors: no problem. thank you for clarifying the queryset problem (the docs don't actually show an example of using ModelChoiceField, so it gets a little confusing)

again bluszcz yes i am

subsume: thanks for your help, I'll run with it

andym: yeah, i set_trace, i wanted to avoid this ;)

slooper: you probably want to google 'non capturing groups regexp'

slooper: to limit choices /explicitly/

* is foolish.

andym: can you share with me some piece of working recipe?

a working recipe of what?

andym: response=client.get(...);resposne.context

beyond whats in the docs, no

uh

y'all might be able to help with this: http://octui.com:8000/accounts/login/

where did my side column go?

my little app is working like in the docs, actually i cannot find anybody who used it ;)

subsume: so I re-read the docs on URLs and the URL dispatcher, and I'm still having trouble passing a model name to the generic views

I have "r'^(?P<model>\w+)/create/', 'create_object'"

trying to pass the name of the model to the create_object view

looks like it's upset because I'm passing it a string and not the actual model class

http://test.site.com:8000/admin/ornette/product... ... all the junk between :8000/ and site_media isn't necessary but is prepended to the link in the edit admin screen... so how do i keep it from doing that?

nevermind

i'm an idiot

You forgot a slash.

yup

i wish that was better explained in the docs

Doesn't it say that right in the file?

which file?

The settings file.

no

it mentions the trailing slash

is there a python function that will take a list and return multiple lists of lists breaking up the original list by a integer?

but in this case it was the starting slash that was missing

seanbrant_: No.

But look in itertools.

[1, 2, 3, 4, 5, 6, 7, 8, 6, 10] break by 2 return [[1, 2, 3, 4, 5], [6, 7, 8, 9, 10]]?

bluszcz: if you check out recipe_01 of cleardjango, it works just fine, adding in print response.context in the test works just great - http://code.google.com/p/cleardjango/source/bro...

ivazquez|laptop: thanks that was my next option

andym: looking

andym: http://code.google.com/p/cleardjango/source/bro... this? there is response.content, not context

yes add in response.context and it works just fine (which is what i said)

lets try :)