> Does anyone have ideas for what to name this function/method? I
> haven't been able to come up with anything I've been happy with.
Joseph,
I'm not flush with naming ideas at the moment, but thought I would
try to brain storm a little.
List of my bad names:
- FilterPerms
- PermFilte
I have been having issues with Akismet as well. I have submitted a
ticket(http://code.djangoproject.com/ticket/2801), so hopefully someone
will have a chance to look at this issue. Akismet has been blocking my
Wiki updates, but allowed me to submit a ticked without any issues. I
have tried it w
Linicks wrote:
> I have been waiting for the pop/gen_auth merge, but it looks like that
> may not happen as soon as I would like, so I will start working with
> the current gen_auth branch in a couple of days.
This should have read:
I have been waiting for the pop/gen_auth merge, but
Jay Parlar wrote:
> Are any other people doing much testing with the branch? It'd be nice
> to see it get moved to the trunk, but I know that won't happen without
> more testers.
>
> Jay P.
I have been waiting for the pop/gen_auth merge, but it looks like that
may not happen as soon as I would l
Chris Long wrote:
> Already had a few people point out some bugs and some features they
> want. Community involvement is key to get this moving ahead as quickly
> as possible.
I'm planning to move my development work to the pop/gen_auth branch
once they are merged. Hopefully I will be able to gi
Once (gen-auth/pop) are merged, what are the major barriers in getting
that branch merged into trunk?
Thanks!
--Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
Now that the "Summer Of Code" projects are complete, is there a
plan/policy/timeline for integrating these branches with Trunk?
Thanks!
--Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gro
Take a look at the js option
(http://www.djangoproject.com/documentation/model_api/).
--Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-de
I have wanted this as a built in "Type" for some time. I usually just
do some manual SQL to alter the columbs that I need to be "Big
Integers", but it would be nice to have them built in, especially for
the default row id created for each table. Hopefully this will make
its way into the trunck
Malcolm Tredinnick wrote:
> On Wed, 2006-08-09 at 19:25 -0700, Linicks wrote:
> [...]
> > AJAX integration is a nice touch, but I think that the use of YUI goes
> > against the established use of Dojo with Django.
>
> Where are we using Dojo at the moment?
>
> Malcol
> Hopefully that answers some of your concerns. I'm curious as to the
> communities take on it, if in general the opinion is to remove it then
> I will. I personally think the admin interface would work well with
> some AJAX built into it, but I know that isn't the case with everyone.
> Comments?
Chris,
Thanks for keeping us in the loop! Row Level Permissions and Generic
Authorization are probably the most important new features in Django
for me at the moment so its nice to know that things are going well.
I'm really looking forward to using it on my current project. Many
thanks to all
Simon Willison wrote:
> On 20 Jun 2006, at 16:25, James Bennett wrote:
>
> > Security by annoyance is security that people learn to hate and turn
> > off as soon as they can, so in the end it doesn't really make them any
> > more secure than they were before.
>
> Agreed - which is why I want to tr
All,
The first thing that you read on the Django project website is this
statement:
"The web framework for perfectionists with deadlines."
I would like to build on the last word in that statement
"deadlines". Every significant project has a some sort of
deadline, it's about the o
All,
Validation aware models have seen allot of attention so far with a
number of proposals out there. This proposal, like the others, has
it's strengths and weaknesses. This method of validating models is a
good start, and will surely evolve or be replaced over time. I believe
that we need t
"""RequestUserMiddleware is a horribly ugly name, and in the
latest diff
attatched to http://code.djangoproject.com/ticket/1428 I've renamed it
to MultiAuthMiddleware. I'm wondering if people think it would be
worthwhile to add something else called AuthMiddleware that would do
more or less what d
"This is great!" Schema evolution is something that I have wanted
since I started using Django. As a safety precaution you could add a
warning when you are running the migration/evolution.
ex. "Warning This May Destroy Your Data, And Render Your
Application Inoperable. Would you like to ba
That looks great! I would like to see it in Django.
Nice work!
--Nick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups
I'm not sure that this is 100% relevant to this discussion, but wanted
to share it in the context of this thread.
A Python type checking module:
http://www.ilowe.net/software/typecheck/
--Nick
--~--~-~--~~~---~--~~
You received this message be
"""c.crime_date = datetime.date(2006, 1, 2)
c.crime_date = '2006-1-2'
In the second example, c.crime_date would immediately be converted to
a datetime.date object. What are the pitfalls to this approach? """
Providing this type of "Magic" is a bad idea because it's not explicit
in f
Here are my two cents,
Clearly some work will need to be done to the current authentication
system to make it more modular for those that have LDAP, OpenID, etc,
as "requirements" for there projects. Having an easy to define
authentication mechanism as Brian proposed is also very attractive. M
21 matches
Mail list logo
