#django

Is there any conceivable way to get the widget of a field in the Django admin to change depending on the content?

e.g. A checkbox if the content is either "True" or "False", and a textarea otherwise?

FunkyBob: heh, ok, good luck with your timezone situation :)

For a specific column of a specific table, of course.

lulzplzkthx: there's callbacks in admin to choose the field

is django able to do things like running tasks in the background

chris_99: it's all just Python

so, sure...

FunkyBob: So perhaps formfield_for_dbfield, check the db_file.name, then check the value and change the widget that way?

but you're probably best using a purpose built tool for the job, like ztask or celery

lulzplzkthx: sounds like a plan

I wonder why formfield_for_dbfield isn't listed in the docs anyway.

cheers FunkyBob :)

lulzplzkthx: because too many people use Admin instead of writing their own management app

FunkyBob: it's a part of Admin :S

and what's wrong with using Admin?

Admin is very inflexible... and doesn't implement your business rules

It does look like it may end up not working for me based on how much customization I'd have to do.

Yeah.

I guess I should just treat it as a nice scaffolding agent.

eventually the limitations of Admin start influencing your app/schema design... which is BAD

The limitations are mostly a pain in the ass.

As in, I'm basically going to end up rewriting Admin.

exactly

It would probably be easier to go my own route.

I have, amongst 1e6+1 other backlogged tasks, a plan to build a more finely layered Admin/Management Console framework

basically, a framework upon which yu could easily rebuild admin... but also more flexible custom management console

The unfortunate part is it makes the Sites management a little big uglier to go to my own route.

Hello everyone!

As you won't be able to manage multiple sites at once that way.

Err, I guess you could.

morning, BertrandBordage

Alright, well I'm AFK for a bit.

is this normal if we can't include two patterns using the same namespace?

BertrandBordage: you mean url patterns?

yes

BertrandBordage: what makes you say that?

if I do this : url('', include(something, namespace='myapp')),

and the line after :

url('', include(something_else, namespace='myapp')),

what's in something_else is ignored

this may be a design decision

can't say without seeing the patterns it should be hitting

let's say you have 3 urls.py, 1 for your project, and 2 for a single application

in the project urls.py, doing:

patterns('', url('path1', include(myapp.urls1, namespace='myapp'), url('path2', include(myapp.urls2, namespace='myapp')

leads to myapp.urls2 being ignored…

having never used the namespace keyword, I feel I'm unable to help

ok

bradleyayers would possibly be a better person to ask

I think using the same namespace is probably not a good idea.

but as he lives in a state that's currently flooded... he may not have net access

BertrandBordage: perhaps create a wrapper patterns list, and namespace that?

FunkyBob: ok, thanks

FunkyBob: of course, but it would be ugly

it's for this project: https://github.com/BertrandBordage/django-viewsets

only as ugly as two includes having the same namespace is illogical

the idea is that urls are automatically builded to avoid having to define the same kind of urls and views every time

(I was about to say "there was something about this on django-dev", but I think that was you)

I wanted to build the namespace from the model app_label

yes, that was me :o)

so what I said wasn't quite accurate

in fact, the application urls.py is like this:

urlpatterns = patterns(b'',

url(br'', include(ExampleViewSet().urls)),

url(br'', include(TweetViewSet().urls)),

)

Maybe using a callable or object for the patterns might work. A bit like how the admin works.

Yes, but I guess the admin is building all its patterns at the same time

Yeah, if you construct pattern names like <app_label>_<model_name>_add/list/detail then you don't need to worry about namespaces.

so, I guess I have to drop the idea of automatically specifying a namespace

(if I want to keep this architecture)

mattmcc: yes, but it's better for understanding to keep the same syntax as the admin (admin:model_create)

Eh, I disagree.

The purpose of URL namespaces is to allow multiple instances of one app to coexist.

I may have misunderstood how namespace should be used :\

And that's not the problem you're addressing here.

yes

I understand now

thanks FunkyBob, schinckel and mattmcc − I'm getting back to work :)

Someone can help me with this traceback? http://dpaste.org/i1qHc/ I'm trying to do tests and I'm getting AttributeError: type object 'Create' has no attribute 'objects'

CRF_H0M3R: and which line of the paste is line 45 of test_vciews_create ? because what's there doesn't match the test_save in your paste

the line is written below: it's line 11 in this snippet

FunkyBob: line 11

oh, I noticed the difference ;)

CreateForm != Create

exactly

CRF_H0M3R: the code in the error doesn't match the code in your paste

so either you pasted the wrong file/lines... or your error is using old code?