On 1/16/07 4:05 AM, Russell Keith-Magee wrote:
Given the current push towards 1.0, it seems likely that this
particular merge will not get the attention of the core developers in
the immediate future (at least until 1.0 is out the door). However, if
you want to volunteer, and you don't feel you
On 1/16/07, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote:
What should be the proper output of the testing results if there are
no errors found?
I've never tried this branch, so I have no idea what constitues
correct output for these tests.
We already use the per-object-permission branch for
What should be the proper output of the testing results if there are
no errors found? We already use the per-object-permission branch for
development of different django projects for a few months and there is
no error found related to the branch. Should somebody create test
cases or something lik
On 1/15/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
The Row-Level-Permissions branch was (is) an attempt to implement this
sort of functionality. I don't know the current state of this branch
(i.e., is it merge ready, fundamentally broken, or somewhere in
between?), but at the very least,
On 1/15/07, Ramdas S <[EMAIL PROTECTED]> wrote:
Hi,
I read in the docs that if I cannot provide permissions at object instance
level using the Meta Permissions.
What is the best way to set permissions rights for indvidual objects, says
articles, where on indvidual article I can set
ba
Hi,
I read in the docs that if I cannot provide permissions at object instance
level using the Meta Permissions.
What is the best way to set permissions rights for indvidual objects, says
articles, where on indvidual article I can set
based on choices -- can be edited by all, cannot be edited
6 matches
Mail list logo
