#django

zanderle, I've never really poked at the admin before (this stuff was mostly created by other people) but I'm starting to realise its potential

FunkyBob: sorry to hassle you, I'm still learning django any chance you could show me a snippet of what the view for the domain redirect might look like?

jsaq007, you can use a generic view for that

jsaq007, sorry

jsaq007, misread :)

nevermind

no problem

jsaq007: just a tick

FunkyBob: thanks

FunkyBob: Thanks appreciate that. checking it out

why do i get: Exception Value: Invalid block tag: 'show_menu'

Paradisee: Welcome to #django! Please dpaste any relevant code and __full__ tracebacks to allow us to help.

nvm

:)

Paradisee: did you load your templatetags correctly in your template?

v0r0nwe: define "correctly"

ok, in your template you are not loading your show_menu tag

if this tag located in yourapp/templatetags/my_tags.py

you can load it via {% load my_tags %}

and then use {% show_menu %}

i got this tag in a view

i mean, in the view.py module.

have a look at the required code layout of custom tags: https://docs.djangoproject.com/en/1.8/howto/cus...

ok thanks

custom tags cannot live 'anywhere'

(of course they could if you override the logic how django finds & loads registered tags :) )

maximum recursion depth exceeded while calling a Python object

lovely

don't name it just 'tags' :)

aww

you're calling show_menu from nav_bar.html and show_menu includes nav_bar.html. you're building an infinite nested nav bar

v0r0nwe: same error.

farn: so i should remove the include, and use show_menu instead?

that's what you mean?

{% include "main/nav_bar.html" %}

i got this inside layout.html

ups

sry

\o/

i am inputting a date and want the epoch time range of that day

how to go about it?

if i include show_menu in the layout.html, it is global to all the content, is there a way to only use it inside nav_bar ?

what is an "epoch time range"

do you mean seconds?

see if i enter 21/8/2015

epoch means point of origin

i should get the timestamp from 0000 hrs to 2359

unix time

of that day

FunkyBob: you know what feels like rST's biggest mistake? Not having explicit header level syntax

BeerLover: you're still not making sense :P timestamps and ranges are not the same thing :)

BeerLover: it sounds like what your describing is exactly the steps you need to code up anyway

how to initialize a datetime object manually?

datetime.date(2015, 8, 21) ?

or datetime.datetime(y, m, d, h, m, s)

etc

Paradisee: don't include a template if you render the same in a templatetag you include

Paradisee: so if you're including the menu template in layout.html, remove {% include.. %} and just use your {% show_menu %}

Paradisee: an alternate approach would be to let {% show_menu %} just be an assignement tag, use it like {% show_menu as links %} and after that you can include your nav_bar.html like {% include 'nav_bar.html' with links=links %}

which i find more cleaner in most cases (if an inclusion tag includes a big, complex template e.g.) but it just depends on taste, i think

too many information

im getting crazy already

Does anyone use django rest framework? I have a problem, I have field which is PrimaryRelatedKeyField(many=True) and when I send request in JS as FormData() I got error on that field which states "u'Incorrect type. Expected pk value, received unicode.'

galuszkak: your pk is an int, not a string

galuszkak: see http://www.django-rest-framework.org/api-guide/... for more info ?

shangxiao: that's not a problem

shangxiao: I tried to request.data['that_field'] = ['4','5'] and I still get this error I tried int also

is there an official statement about whether you can use or should not use the same name for two different named url patterns?

and still when I run serializer.is_valid() it fails. Doesn't matter what will be in QueryDict in request.data

hopthrisC: official statement? not sure. but it means you can't reverse lookup urls then.

shangxiao: sure you can

it works at the moment

the docs just don't say 'you have to use unique names'

if you feel there's discrepancies in the docs, submit a ticket

well, it's not a discrepancy, per se

you don't have to use unique names

in fact, some people like to repeat a name

i've deliberately used the same name as an allauth url

for pseudo-polymorphism

so that i can override it

doismellburning: but is it documented?

if you have to ask the question, the documentation is buggy, right doismellburning ? :)

either that or you didn't read it properly ;)

shangxiao: either that, or i'm too stupid to read the docs

which was my whole reason for asking

i'm curious to know what you mean by "it works at the moment" so you can reverse lookup both urls?

shangxiao: ;)

hopthrisC: good question

shangxiao: yes.

shangxiao: ('^foo/$', name='foo'), ('^foo/(?P<id>\d+)/$', name='foo') => both {% url 'foo' %} and {% url 'foo' 123 %} work

ah well that's different

different to what?

i'm guessing this is the pseudo-polymorphism that doismellburning was talking about?

shangxiao: as i understand it

this seems reasonable

exactly

sorry, multitasking

i thought you meant ('^foo/$', name='foo'), ('^bar/$', name='foo')

i've used that to override allauth urls before

shangxiao: right, that would be silly

well, like i said, it has its uses even if it is hacky