#django

I am sorry to hear that, pdehaye2017

jnerula: https://dpaste.de/k2Dk these are the serializers

I think it is because I have location as a m2m relationship

jnerula: https://dpaste.de/eSbO#L7,9,15,17,27,29,35,37 these are the offending lines, it shouldnt encapsulate it in [] nor add that extra "point"

hello everybody

I'm trying to test a POST request, but I don't know how to pass the 'Authorization' header

use the same content as an authorized browser's cookie

I did something like this snippet ...

... https://dpaste.de/O1os

but I always get 401 http status code in the response

What could be wrong?

myclient.post('/logout/', HTTP_AUTHORIZATION="Token 7753b87a72832dd8c35a7550e5a498cc365a5443"} )

I'll try....

FunkyBob: you gave me the right hint! Actually the line would be like this: myclient.post('/logout/', {}, HTTP_AUTHORIZATION='Token 7753b87a72832dd8c35a7550e5a498cc365a5443')

thank you!

I read the Django test client docs, but I misunderstood the given example

Is it Ok to assume that http headers are always sent in uppercase and starting with 'HTTP_' ??

at least to assume it when using django test client ?

yes, it's ok... because we still haven't shrugged off the shackles of CGI :(

bsically, you pass that stuff in the same format as it will appear in request.META

ookk!

thanks a lot FunkyBob! Now I can end my end with a small victory :)

* end my day

huzzah!

we just went through a trial approval process for our MVP

I've already fixed all the bugs uncovered

before the meeting even finished :P

Neat FunkyBob :D

did I mention I realy like how django-nap has turned out? :)

you committed some token example yesterday iirc?

Funky going HARD

sphrak: ok, nap-token-auth ? not sur why I called that nap :P

it's in no way restricted to django-nap

we used it to deal with CORS stupidity in IE

FunkyBob: yes :)

could not get the magic recipe to make it post cookies... so we sent an Auth bearer token instead

gah why does this code produce an extra point block? https://dpaste.de/CKuH#L38

FunkyBob talk to me about this MVP

Anyone have any guidance on how to handle storing recurring scheduled tasks? Espeically with regard to daylight savings and not getting an hour ahead/behind when that happens. I realize that this may be a quite involved topic so a link may be the best answer... i haven't been able to find anything particulary useful on my own

wedgie: I'm not quite sure I know what you mean. I use cron to schedule tasks.

wedgie - anything that is UTC timezone aware will automatically update the timestamp so you should be fine

jessamynsmith: well, these would be events that a user schedules. For example, send a reminder every day at 8am. I don't want to convert to UTC and store that way becuase when a daylight savings transition occurs, it'll be an hour off

wedgie - based on that, you can set recurring tasks with celery that follow a schedule based on the systime, which should be timezone aware

mcspud: well, it doesn't matter what the system's local time is, it will matter what the user's local time is.

literally the entire point of timezone aware to make time consistent across changes like daylight sayings

so it kinda feels like it should be stored in the user's local time... but that sounds like it has it's own issues

saving*

I'm pretty sure you want to save it in UTC and also save what the user's timezone is

mcspud: quite new to django so maybe i'm overthinking things. Is there some magic built in that just handles this stuff?

yes, UTC timezones

^_^

what do i need to google to read up on that?

How are you going to schedule your tasks?

heh, that's what I'm trying to decide. In the very early planning phase so i'm VERY open to suggestions :)

celery is the most commonly used django task runner

I'd recommend that

you can't just rely on utc and timezones, especially for user local time scheduled tasks

you have to store the users local timezone, and the time in that local timezone that you want to execute

wut

why

scheduled tasks in local time are about the only case where utc + timezone does not work

If a user registers a task for `08:00:0000+11`, and the users timezone goes to +12... oh I see

But doesn't that mean you need to store their locale?

offsets are not timezones :P

yeah

I dun goofed

also, timezone definitions can change between the time you stored the event, and the time the event occurs

that's the really tricky bit to handle

the best way I can think of is..

every X (minute, hour?) .. check if any tasks, converted to current UTC match current UTC.. execute if so