#django

hey, in the templating language, is there a way to do a one line block w/o doing it with an open and close block?

the way i dont want to do it is `{% block title %} SomeTitle {% endblock %}

can anyone help with class based views and how to deal with form validation correctly when you have two forms on a template, so far I have https://dpaste.de/pvtD

o/

briian, I don't think so... can't just use a variable?

GinFuyou: i can use a variable, but thats not what im asking

you mean put a variable in the base template?

yes, with |default if needed. For what you asked I told above: if it's not in docs you most likely can't

I'm not quite sure if it make sense actually, surely I don't mind shorter syntax but I'm not sure it would be actually contribute to readability

asej, I don't think your PeoductDisplay is a good idea

it might not because of how the {% system works in django

in blade (php) itd be @section('section_name') @endsection, or @section('section_name', 'some value')

which was nice for titles and stuff

It's how programming works: some approaches have own pros and cons

asej, for your post() part, have you looked at http://ccbv.co.uk/projects/Django/2.0/django.vi... ?

basically you just need to fill in with POST two forms

You can hack it in together quickly, or go deeper and build customized 2-forms view\mixin with special methods

thanks im enlightened now

Generally I advice against messing with concrete view's get() and post() methods, if you don't have a very good reason to (there are such reasons, but not hat common)

briian, C.O. always at your service =^_^=

where do global project modules get stored? i have a script that is gonna be used by multiple apps

hmmm. who's responsible for doing 'date-string'::timestamp in queries, the ORM or the underlying psycopg2 lark, doe sanyone know?

should i just create a modules folder in /modules/

s/in/as

yes, just somewhere in your project folder.

hi, how can I serialize a list of objects Foo.objects.all() to JSON but for example modify one of the fieldnames so that e.g. "created_at" becomes "start"?

setre: http://www.django-rest-framework.org/api-guide/...

do I need the rest framework to do it then?

oh sorry

I though I was on the django rest framework channel. You should be able to do without it

no problem. I can't find it on the googles though

there is a number of ways to do it, model objects are not serializable on their own anyway

json.dumps(tuple(Foo.objects.annotate(start=F('created_at')).values('fields', 'i', 'want', 'start')) probably, assuming the other fields are normally serializable by json.

(nb: totally untested :p))

kezabelle: interesting, thanks

yeah, was thinking something like that too

foo_json = serializers.serialize("json", Foo.objects.all())

that doesn't do renaming though (which is the point). And I dunno wtf it does if you throw a .values() at it.

okay how about transforming the data in Foo created_at from datetime to date before serializing it?

I mean a 2nd problem

json.dump would do though you'd probably want to add an encoder/decoder for datetimes

ah thanks

at the point where you start transforming things though ... use something properly, like rest-framework, or marshmallow, or nap, or serpy

don't try to do it all at once. just make your query, modify the result, then send it as json (JsonResponse)

great, thanks

in a template, is it possible to both use {{ form.as_p }} and in the same form also define other intries? i ofcourse want to grab stuff from the field in my view but simply calling https://dpaste.de/ihkO#L8,9 does not put email into db with user; note that the user is created but without email

forms only know about the fields they declare

so if your form doesn't *declare* an email field, it'll just be summarily ignored by the form and the cleaning (ie: it won't be in cleaned_data, even if it was in data)

hmm

this is my template: https://dpaste.de/jaKL

what would be the point in having cleaned data if it just accepted any old thing? :)

but i get what you say, so my thing will not work

your template is wholly irrelevant

well

yeah

you can submit a field called "flibbity" if you want. If the form doesn't expect it, it won't care about it

but my problem is that the Form is declared within the django-framework itself

so? subclass it

subclass i dot know about

dont*

you've defined the extra fields in UserCreationForm ?

nop

i dont know where or how to do that

how do i "extend" the default user form?

well, you include the file

same way you extended Models

if you've ever *used* a model, or a form, or the modeladmins and especially if you've written one yourself, you've subclassed

subclasses are *everywhere*

ah, you mean you use some Forms from some package (probably allauth or similar), right?

(see also, class based views, etc)

i know how to use normal forms and models, but i dont know exactly how to extend things

MyForm(UserCreationForm)

You just don't realize you know )

so i import the django-framwork form into my forms.py right?

and then do lxer's thing

i think i get how it works

but when you say "subclass" its like another word for "extending" right?

we usually don't invent "other words" just for the fun of it

it's the same thing, possibly more correct given the different ways extension could happen.

"extending" is more of a concept, "subclassing" a technique

if you like, it's also specialisation through inheritance :o)

i just havent really realised subclassing before i guess :3

I am trying to get events into fullcalendar from django and it accepts the first line and creates the event but not the second line for some reason http://dpaste.com/28KZEKA

if I manually create json (1st line) it loads okay but the output from json.dumps() doesn't work although it is valid json

it's not valid JSON. it's a string.

okay thanks

(well, technically that could also be valid JSON, when parsed via JSON.parse or json.loads() if the string were flat, but that's not the point at hand)

this is what made it: http://dpaste.com/3VJBETH

how can I make it not be a string?

JSON _is_ a string