#django

I've got a question about signals. I've got a Django project (call this project B) installed via pip and then included into my main project's (project A) INSTALLED_APPS. If I'm emitting a signal from project B and I have a receiver in project A connecting to that signal (via from projectA.signals import signal123; @receiver(signal123)...), will that receiver be able to receive signals emitting from project B? I've confirmed it works i

project A but it doesn't seem to receive signals emitted from project B.

chuckoy, that sounds like an odd arrangement. are you certain there are no other options?

chuckoy: A and B are apps, not projects

signals are not isolated between apps and it should work

@jonez, it's because project B is being used across 3 different projects. We sort of centralised the models and services among other things there so we didn't have to update across 3 different projects whenever a change was made

ah

my first concern was if the different apps have a diff pid, and from what Koterpillar said, they do not

chuckoy: app B

jonez: pids are irrelevant to all this, as are UNIX signals

@Koterpillar, is it really an app? My understanding is that apps are the different folders inside a single project, right?

so the signaling going on is not posix?

my fault

chuckoy: apps are whatever is in INSTALLED_APPS

jonez: no, search "django signals"

ok

oh ok I see now

cool

@Koterpillar I see. I think my misunderstanding stemmed from project B having an app with the same name as project B's name. So there are two separate objects project B and app B. I installed project B via pip and listed app B as an INSTALLED_APP in project A, si that correct?

you install *Python packages* via pip

an app is a module (from a Python standpoint)

@Koterpillar, yes we uploaded project B as a python package via a custom PyPi repo

one package can have multiple apps (e.g. Django has auth, admin, etc.)

so we list projectB as a requirement in our requirements.txt file

package B

package B which contains a Django project B or is that wrong?

which contains a Django app B

which you put into INSTALLED_APPS

I see. So Django projects don't play into that scenario?

a Django project is whatever has a settings.py

therefore, projects have apps installed in them

I see... this package B has two apps (?) app B and app C which has a settings file. Am I correct in syaing that app C is a Django project on top of being an app?

the correct thing to say would be that the package B has an app B and a Django project C

Okay

So if I'm adding app B from package B into the list of INSTALLED_APPS in project A, the signals being emitted from app B's code *should* be received by receivers in project A/app A's code connecting to that signal, right?

the signals ignore all this stuff about projects and apps and just work

if they don't appear to work for you, verify that you are actually sending them, and then trace through

Okay. Thanks for the help! When I'm emitting the signal from somewhere in app A's code it went into the callback function when I was debugging but not when it was from app B so that's why I had those initial assumptions. I'll try and put some more debugging code later.

Can't do it right now, got to go to a meeting :(

Thank you Koterpillar

What's the most straightforward way to convert a urllib3 response to a django response?

jivan: copy the headers over, attach a FileResponse to the resposne stream ...?

Hey guys, I am looking to check to see if a user is in a certain group before accessing a specific page. https://paste.pound-python.org/show/rdTMA93duVr...

Is there anything missing in this that could bite me: https://dpaste.de/pTAs?

Is there anything in particular I might be missing?

It seems to be returning False for the user, currently.

Zequal: typically that's considered a poor way to use django's auth system... you should be testing for permissions instead

also, login_required and user_passes_test there are redundant... the latter will imply the former

and what are you hoping to tst by using "if user"?

FunkyBob: Ah I didn't know that. I've seen a lot of other examples implement both. I'm just trying to validate that the user in LDAP is a member of either one of two specific groups.

login_required is made from user_passes_test

FunkyBob: So would I be using @login_required and @permission_required once I make a permissions object?

no

you can't have permissions if you're not a logged in user... so being logged is is implied by having perms

(unless you have some custom auth backend)

FunkyBob: What exactly would be ideal to use to accomplish what I am looking to do?

what I gave you is fine

FunkyBob: There's multiple ways to skin a cat, I can import User and Group from contrib.auth - but there are so many other mechanisms in place, I figured there's a cleaner, better way to do what I am trying to do.

Oh

it's not the right way to use groups/perms... and there are hazards [like magic names] ... but it works, and many of us do it :)

gah.. mid-day meeting.. better get an early lunch

mornin' Bob

o/

\o