#django

Happy New Year!

Happy new year eraldo

I am looking forward to many new Django projects this year.

someone has used django class based views to receive file uploads via PUT ?

instead POST

anyone in SF in here?

chronos: you need to subclass and allow for that verb

chronos: you can also just use POST

(obviously)

I'll but just thinking why put not works ... it not fill self.request.FILES

it should work, prob doing something else

try to use put just to eliminate that being the issue

i mean POST

not working with put... I'm doing XHR file uploads with Jquery File Uploader and, with PUT, request.FILES isnt filed

using 1.5b of last week, will update heeh

uhm files is usually binary

so you need a special library that supports that

check the xhr request if the files are there at all…

yes, they are.

if I use POST, works fine

what do you mean by it doesn't work are youg eating a traceback in the ajax request

fission6: file isnt in self.request.FILES with put ajax requests.

and they should be

any traceback

and sadly I dont have time to investigate more now

(cuz I'm working on vacation lol)

chronos: check request.body and see if it's there

if not jquery fails before already

The method of the HTTP request used to send the file(s) to the server. Can be POST (multipart/formdata file upload) or PUT (streaming file upload). Accepts a String or a function returning a String.

k apollo13

hm, PUT will not accept multipart than

I upgrading, check all that soon

apollo13: where you based out of curiosity

austria

oh word

apollo13, file is in request.body, but not in request.FILES

ipdb> (len(self.request.body), self.request.META['CONTENT_TYPE'], self.request.method, self.request.REQUEST, self.request.FILES)

(2027935, 'image/jpeg', 'PUT', MergeDict(<QueryDict: {}>, <QueryDict: {}>), <MultiValueDict: {}>)

this is a debug line in put method.

ahn, I dont know how 'streaming file upload' should work exactly, but for size of body file was fully uploaded, but just not recognized.

in the default LOGGING configuration, when running Django not from the runserver but lighttpd using manage.py runfcgi, what counts as the console that logging messages get sent to?

well, that is in docs: https://docs.djangoproject.com/en/dev/ref/reque... 'Note that FILES will only contain data if the request method was POST and the <form> that posted to the request had enctype="multipart/form-data". Otherwise, FILES will be a blank dictionary-like object.'

chronos: my rec is to move on and just use POST

I will fission6 :), but was really curious.

thx guys

curiosity is good, so is productivity

indeed, but a bit of curiosity sometimes lead us to improvement, other times, we just loose time

wont argue that

do rendered objects have a url b default? like <a href="{{ blog.blog.url }}" >

*by

cramm: well, if curious, look how django parses request.FILES ;)

Happy New Year all

apollo13: a commit a day for 2013!

superdmp: haha

you think I'm joking!

chronos: but if you look at _load_post_and_files in django.http.request it only loads files for POST requests

superdmp: nono, but I already have more than one today ;)

in the default LOGGING configuration, when running Django not from the runserver but lighttpd using manage.py runfcgi, what counts as the console that logging messages get sent to? I thought it would be the error.log of lighttpd, but it seems not

apollo13: yes I saw

apollo13: hehe, I'll when have time, promisse :).

superdmp: console is always stdout of the manage.py process I guess

still, that's my new year's resolution, if I can do it for the docs

superdmp: hell that would be great

superdmp: http://docs.python.org/2/library/logging.handle... the console logger is just a stream handler, so whatever manage.py has as stderr is where the log will end up

apollo13: ok, so if I can tell manage.py where stderr is, then I should be able to direct the messages in that direction

thank you

I think so yes

eh superdmp

superdmp: you managed to solve your memory issue ?