#django

FunkyBob: but if I do cd /; python /path/to/project/app/wsgi.py I get the same ImportError

ok

ImportError: No module named proj_site.settings

now do "PYTHONPATH=/path/to/project/ python /path/to/project/app/wsgi.py"

afk... sprint retrospective meeting

FunkyBob: dont get it, should there be some semicolons there?

JZA: Probably not: the first part sets an environment variable (but only for the current command).

The next token is the interpreter, the last one is the argument to the interpreter.

schinckel: my python is on the 'bin/python'

path to the virtualenv might not be enough I think.

I just get a No such file or directory.

You should be able to pass the full path to the interpreter instead of "bin/python".

right but the project is not the full path to theinterpreter.

is virtualenv/bin/python

sorry I am confused.

Well, that's not the full path anyway, that's a relative path.

oh god

.../virtualenv/bin/python

where ... IS the full path

/Users/jza/foo/bar/baz is a full path.

Or whatever. A full (absolute) path starts with a /

I KNOW that assume is on the ...

my point is that the string was aiming at the virtual enviroment instead of the virtuale enviroment PLUS bin/python

Could someone explain how I disable the check outlined in this post? https://code.djangoproject.com/ticket/22690

I have a proxy model with fields

Evidlo: then it's not really a proxy model, is it?

FunkyBob: I want to extend Group with an attribute, instead of amethod

can you dpaste the model to demonstrate?

FunkyBob: http://ix.io/l37

It's a bit more than just 'an attribute'

I used to have a one-to-one relation to group from Organization, but accessing the Group makes things cluttered conceptually

Evidlo: but... that model still has a bunch of extra fields

so it's NOT a proxy model

you could do it as a multi-table inheritance... but it's not a proxy model

the purpose of a proxy model is to provide a separate class for the same fields... adding extra methods, etc

your model clearly has 5 extra DB fields...

FunkyBob: My motivation for doing this is that I want auth to use Organization instead of Group

If there was an AUTH_GROUP_MODEL setting, that would be perfect

FunkyBob, Is there any way I can replace Group entirely?

FunkyBob: any idea why wsgi wont work for me?

Evidlo: why can't you just add your own Organization model, nd use it?

JZA: nope... but it's been [literally] years since I used mod_Wsgi

JZA: did you look into setting WSGIPythonHome ?

this might be a hopeless question, but: i'm upgrading a large code base from 1.4 to 1.8 (I know!), and I have an abstract model with a foreign key to User. Something that tries to list all the fields on User is finding these foreign keys, but then the model doesn't have those fields. Is this ringing any bells?

FunkyBob: yeah I did, althought is that different from declaring a python-path on WSGIDaemon

how many times should I point where my virtualenv is?

I meant to do that instead of adding it to python-path

django-guardian only operates on Users and Groups, not Users and Organizations

Evidlo: I don't recall where in this discussion you mentioned guardian was in use

I can add users to my Organization directly, but permissions applied to Organization won't get inherited

how does your organisation differ fro ma group?

FunkyBob: ok I will try that route

Those 5 attributes and all those member functions

Evidlo: why can't you just extend group?

I pasted it

using MTI

I can, but that doesn't mean guardian will use my model

no, it will use group... from which you can access your model

it's almost starting to sound like guardian is the problem here

Isn't guardian an extension of auth?

it's one way to do it, yes

it's an implementation of row-level permissions...

contrib.auth specifically doesn't implement one, because there isn't one that fits generally

But it uses auths Users and Groups, which is why I didn't bring up I was using guardian

...

yes, but then you specified your reason for not just adding Organization model as "guardian doesn't support it"

Why does author let me replace the User model but not Group?

I could argue that django doesn't support it

auth*

I'm not really interested in arguing though. Just ideas for a solution

well, as I said... my path would be to add an Organization model

but I don't know how much of guardian you're actually using, and how much you're just acquiescing to

The feature I'm missing when I use Organization instead of Group is Group->User permission inheritance

so add that into a custom auth backend

would need to know more details about your actual needs to advise better