#django

Ruzzy: Almost certainly. Have you looked into using a Makefile, or some other automation tool? Fabric is a good one.

schinckel: is it worth using an automation tool if the script is overly simple?

it is basically make some directories if they aren't their, chown them and chmod them, then npm install and collectstatic

I think...

there*

Maybe, maybe not. You'll probably find that you'll have other tasks that need to be executed, so having a place to store them is useful.

how do i configure the transport layer for celery from the django settings module

schinckel: I found makefile incomprehensible for C++ a long time ago

im using the config from obj func

schinckel: is the pain similar for a python project?

schinckel: and also what makes fabric stand out

I used to use fabric, but moved to a Makefile some time ago.

schinckel: why the change

I needed some way of defining dependencies. And most of the fabric commands were calling shell commands, so it turned out to be simpler to move them to a Makefile.

Do you guys have any thoughts on where I should put helper functions in django?

I have a bunch in my models.py, but they don't -belong- to any model in it. I think it's time to give them a better home

How about helpers.py?

mattmcc: sounds good

at least one very highly voted SO answer says utils.py

querying the abstract User class returns an empty queryset in tests, but works fine from the Python console... why?

pfcodes: tests do not use data from your main database

jessamynsm: thats right, thanks!

Ruzzy mattmcc whatever you want to call it that is description, I guess

sorry I meant descriptive

at different times I've had helpers.py and utils.py

I've had both in the same project. :(

schinckel: I think I have too

hey guys, i've been stuck for hours now on an issue with the django rest framework auth serializer, i have a custom login that checks the serializer wether is valid or not and it always returns false

i never get past this : https://dpaste.de/hw9y#L31

line 31

and on django 1.10 it works , but on 2.1 fails

i seriously been banging my head against the wall with this one

dezmaeth: which version of drf?

jessamynsmith: 3.8.2

djangorestframework >= 3.8.2

django-rest-auth >= 0.9.Y3

0.9.3

rest-auth

so you are on the latest drf

yea

tried older version , same result

that's useful info

credentials are fine

did you debug to see where precisely it's failing?

in other words, why it thinks it isn't valid?

in theory your libs should work with django 2 :/

jessamynsmith: it fails on the rest_auth/serializer.py @ line 28 # authenticate(email=email, password=password)

I wonder if there is a missing setting

like if it needs an authentication backend that isn't enabled, or something

then it fails on : user = backend.authenticate(request, **credentials)

or if username/email are getting crossed somewhere

returns user = None

let me see what backend is set

'allauth.account.auth_backends.AuthenticationBackend',

AUTHENTICATION_BACKENDS = [

'django.contrib.auth.backends.ModelBackend',

'allauth.account.auth_backends.AuthenticationBackend',

]

dezmaeth: DO NOT PASTE IN HERE

FunkyBob: sorry

read the topic.... use dpaste.de

FunkyBob: will do

jessamynsmith: https://dpaste.de/88cf

dezmaeth: my best suggestions are to read over release notes, see if there is any new setup required

jessamynsmith: ok, thanks, u mean on rest-auth newest versions?

I was thinking rest-auth and rest-framework, yeah

also maybe try debugging into that method, see if values match what you expect, and if it's using the right backend

random stupid question of the hour... what replaced removetags?

You mean striptags?