iso

I have a model that contains datefield . I'm trying to get query set of that model that contains current week (starts on Monday). So since Django datefield contains simple datetime.date model I assumed to filter by using .isocalendar() . Logically it's exactly what I want without no extra comparisons and calculations by current week day. So what I want to do essentially is force .filter statement to behave in this logic: if model.date.isocalendar()[2] == datetime.date.today().isocalendar()[2] ... Yet how to write it inside filter statement? .filter(model__date__isocalendar=datetime.date.today(

I am currently using Moment js to parse an ISO 8601 string into date and time, but it is not working properly. What am I doing wrong? And I would take any other easier solutions as well. The ISO 8601 I would like to parse: "2011-04-11T10:20:30Z" into date in string: "2011-04-11" and time in string: "10:20:30" And tried console.log(moment("2011-04-11T10:20:30Z" ,moment.ISO_8601)) and console.log(moment("2011-04-11T10:20:30Z" , ["YYYY",moment.ISO_8601]) as a test, but it just returns an object with all different kinds of properties. With moment.js var str = '2011-04-11T10:20:30Z'; var date =

Should I use ISO 639-1 (2-letter abbreviation) or ISO 639-2 (3 letter abbrv) to store a user's language code? Both are official standards, but which is the de facto standard in the development community? I think ISO 639-1 would be easier to remember, and is probably more popular for that reason, but thats just a guess. The site I'm building will have a separate site for the US, Brazil, Russia, China, & the UK. http://en.wikipedia.org/wiki/ISO_639 sorin You should use IETF language tags because they are already used for HTTP/HTML/XML and many other technologies. They are based on several

The ISO C Standard (ISO/IEC 9899) and the ISO C++ Standard (ISO/IEC 14882) are not published online; instead, one must purchase the PDF for each of those standards. I am wondering what the rationale is behind this... is it not detrimental to both the C and C++ programming languages that the authoritative specification for these languages is not made freely available and searchable online? Doesn't this encourage the use of possibly inaccurate, non-authoritative sources for information regarding these languages? While I understand that much time and effort has gone into developing the C and C++

This question already has an answer here: Recommended gcc warning options for C [closed] 15 answers What GCC options should be set to have GCC as strict as possible? (and I do mean as strict as possible) I'm writing in C89 and want my code to be ANSI/ISO compliant. Jonathan Leffler I'd recommend using: -Wall -Wextra -std=c89 -pedantic -Wmissing-prototypes -Wstrict-prototypes \ -Wold-style-definition You should compile with -O as well as -g as some warnings are only available when the optimizer is used (actually, I usually use -O3 for spotting the problems). You might prefer -std=gnu89 as that