#django

I found a solution to differentiate. Check is the object is iterable. If True then it is a list if not it is a single object. >>> hasattr(myDjangoSearchQuery, '__iter__')

FunkyBob: Thanks for the hint.

lindylex: don't do that...

Why?

A model instance can define __iter__, too

rats

Also in python generally you don't use hasattr for those kind of things, I'd say it's more pythonic to do try: iter(foo) exept TypeError: # not iterable

That doesn't prevent your function to fail if the model defines __iter__, however. Just do what FunkyBob said and always use a QuerySet

I still don't understand why you need to differentiate? lindylex

lindylex: you're doing it wrong

lindylex: why would you ever not know if you'r passing a list or an instance?

in fact, why would you write a function that accepts both?

basically, the solution is... don't ever put yourself in this position

FunkyBob: I need to be able to handle both that is why.

lindylex: you should probably paste (on dpaste.de) your function and the places where you call it

Then we can tell you how to change it so that you don't need to make that distinction

lindylex: why??

again, tell us more

why woul you call geT() sometimes and not othertimes, for what to pass to this function?

what is thisfunction?

lindylex, there is most certainly a better solution

Those are spec that were sent to me.

...

so when we kept asking for more information... you had it, but just refused to share it?

No that is not what i was doing. I feel disappointed you would experience that.

does the spec explicitly say you have to write a function that either expects a QuerySet or a Model instance?

lindylex: I'm not sure how much clearer you want us to make this

explain more about what you're doing

share with us details of your functions

and the actual constraints you have

Hi all

Hi

but as I said before.... writing a function that either takes an instance or a queryset in the same argument... is BAD DESIGN

In model meta doc, there is a typo

is that really?

My function accepts a QuerySet. And I dump that as a JSON object to a file.

staranjeet: where?

lindylex: so ... what's the 1 stuff all about, then?

lindylex: querysets are always iterable, so no need to check for that :)

the closing parenthesis after reverse

lindylex: a queryset of 1 object is iterable, too

*relations

Hi, sice I've updated to django 1.9.2 from 1.9.1 I have problem with errors "ield specifies a many-to-many relation through model SOMETHING, which has not been installed." it pops here https://github.com/wilima/Semantic-CMS/blob/dev... because I am using this app https://github.com/wilima/django-dag/blob/maste... (especialy functions down causing the errors) where can be a problem? Thanks!

and after and, that "semicolon" also

lindylex; I asked you ages ago why you need to tell, why not just always pass a queryset

lindylex: now you say it's always a queryset

Household.objects.get(pk=11) does not return a list only one object.

lindylex: .filter(pk=11) does

lindylex: you said it was always a queryset... that does not return a queryset

make up your mind

or EXPLAIN MORE

lindylex: this is an instance of the famous xy problem :)

FunkyBob, any comments?

staranjeet: does look like a mistake

i can send a pr for that

staranjeet: please do

the correct version should be

API will find "reverse" relations), and:

lindylex: that problem can be rather frustrating for people who are trying to help, which is why FunkyBob may be a little annoyed right now ;)

moldy: that's why I broke out the bash.org quote...

moldy: http://bash.org/?866112

staranjeet: don't forget to make the PR against master and not the 1.8 branch

FunkyBob: ;)

i appreciate all the help. I probably need to think about it some more. Thanks again for the assistance. It was truly appreciated.

sure moritz_s

lindylex: from what you told us so far, all you need to do is replace .get() with .filter() where you get the object

lindylex: alternatively, if you do not want to change the .get() call, you can do this: my_function([myobject])

moldy:Yep I noticed that also.

I see that converts it to a list

lindylex, and don't hesitate to ask if you need more help

people here are very willing to help

you just need to be willing to provide the necessary information in return

lindylex: but please... explain the _whole_ problem

(which you would think goes without saying... but doesn't)

I noticed and this is the best resource. I truly appreciate your offering everyone. Especially you Funkybob. Time and time again you have been extremely responsive.

bumping my problem :) anyone please?

So, I am trying to run this tutorial: https://docs.djangoproject.com/en/1.9/intro/tut... but I am stuck with trying to wire an index view into the URLconf. When I start the server I get a 404 and the error message http://pastebin.com/BJJcWaX4

jonalv: don't use pastebin, please, use dpaste.de instead

FunkyBob, moritz_s : submitted a PR for this, please review

https://dpaste.de/M1Xi <—new paste

moldy: your suggestion solved my problem. "alternatively, if you do not want to change the .get() call, you can do this: my_function([myobject])"

Hi, I want to include a library into my app and use it within the application. I created a lib folder in my project directory and tried to import from it but it doesn't get recognized. Could someone tell me how to do this?

lindylex: :)

carpediembaby: which library? is it packaged properly? available on pypi?

wili: it seems that the app that contains the Relationship model is not in INSTALLED_APPS

moldy: it is my own. So i just want to include my own functions and use them within the django project. But they don't fit into the models/views category so i want to keep them separate

carpediembaby: python2 or python3? do you have an __init__.py file in the lib directory?

moritz_s but how it is possible that it works well in 1.9.1

staranjeet: so ... https://github.com/django/django/pull/6226

staranjeet: I believe the : is valid there

though maybe a ; is better

yeah ; is better

moritz_s ah there is the thing.. its looking for django_dag.Semantic but Semantic is not in the app but in my project Semantic.Semantic

moldy: its 2.7.6 , ah yes, I was missing the init.py in the lib directory i created. Stupid mistake .. Thanks!

should i update the PR or create another

moritz_s full error semantic.Semantic.children: (fields.E331) Field specifies a many-to-many relation through model 'django_dag.SemanticEdge', which has not been installed.

staranjeet: update

guys I don't figure out how set my settings. I created a dir "settings" inside the project dir, the i created my own settings like "base.py", "local.py", "deploy.py", the I exported DJANGO_SETTINGS_MODULE='project.settings.local'. The server run properly, the shell too, but when i tri ti print for example "BASE_DIR" the interpreter say it doesn't exists

moritz_s so its problem that I will put the name of the model but not the location of it

*then

realnot: print how? exactly what did you run?

moritz_s fixed by class Semantic(node_factory('semantic.SemanticEdge')): vs class Semantic(node_factory('SemanticEdge')):

thanks

realnot: also, you might want to look at django-classy-settings ... helps avoid the pains of multi settings files

FunkyBob, updated