Authenticating against Django's user database from Lighttpd
Will something like this ever be available for use with lighttpd and fastcgi? http://www.djangoproject.com/documentation/apache_auth/ --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Reversal Lookup TODO Needed
I know this is a big/difficult TODO, but the Reversal Lookup needs to handle nested parentheses. I'm talking about (urlresolver.py): # TODO: Handle nested parenthesis in the following regex. result = re.sub(r'\(([^)]+)\)', MatchChecker(args, kwargs), self.regex.pattern) (r'^foo/(?P(/d+)*)/$', ...) will cause it to freak out --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Reversal Lookup TODO Needed
And another problem. I can't seem to get it to reverse on a url that's in an app urls.py (referenced by the main urls.py, of course). bradford wrote: > I know this is a big/difficult TODO, but the Reversal Lookup needs to > handle nested parentheses. > > I'm talking about (urlresolver.py): > # TODO: Handle nested parenthesis in the following regex. > result = re.sub(r'\(([^)]+)\)', MatchChecker(args, kwargs), > self.regex.pattern) > > (r'^foo/(?P(/d+)*)/$', ...) will cause it to freak out --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: A bug in reverse url lookup? (and a possible patch)
I created a ticket for this: http://code.djangoproject.com/ticket/2025 --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Reversal Lookup TODO Needed
I created a ticket for this http://code.djangoproject.com/ticket/2025 --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
wontfix
There are many tickets out there marked as wontfix. It would be nice to see an explaination of why the ticket was marked as wontfix on all tickets marked as wontfix. Just a brief description would do. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: #2217 - Filtering using objects rather than IDs
I never understood why you filter an object with foo=foo.id and you create an object with foo=foo. Consistency is nice! --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: wontfix
Not off the top of my head. The reason I made this comment is because I like going through the timeline and having been noticing a lot of tickets (which I thought were good features/fixes), but were marked as wontfix by adrian with no explaination and no dialoging before hand either. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Too Much Custom SQL
Hi, it seems like I'm constantly writing custom SQL code for everything because the django ORM cannot handle a lot of my requirements (which is perfectly understandable). Would it be such a bad idea to add an api to the django orm that's similar to SQLAlchemy? I don't like having to create cursors all of the time. I also don't like the fact that there are so many ways to access/manipulate information in the database: I create the model via django's orm. Then, to access the database I can either use the ORM, sql from within my django app, or within the database (via stored procedure). So, when I need to find or change the way I retrieve/manipulate data from the db... it can be in any of those places or forms. Something doesn't seem right about this. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Too Much Custom SQL
Yes, GROUP BY and aggregate functions were at the top of that list. Others include complex joins, UPDATE FROM, temporary tables (not that often), sequences, and more (but those are the most common), especially stuff that is specific for just postgresql (the database that I happen to be using). Another question: Can django do and UPDATE without selecting all objects first? I didn't know about those tickets, so thanks; that should help some. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Broken Filters in Template Conditional
when i try the following:
{% ifequal bar foo.id|stringformat:"d" %}
I get an error saying that:
VariableDoesNotExist at /foobars/
Failed lookup for key [id|stringformat:"d"] in foo
it's as if it strips anything that's before the '.'
please correct me if this is not a bug.
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---
results_per_page does not work properly
I have added a few extra_lookup_kwargs to my generic object_list and
when in {{ results_per_page }} in my template it always displays what I
paginate_by. I'm using 0.91.
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---
Re: results_per_page does not work properly
i want the number of objects returned for that particular page. i guess what i want is results_on_page. when i go to page 2 (of my results), which only has 1 object listed it says that results_per_page is 2, i would like it to say 1. what would be even better is if there was a displaying_results_from and displaying_results_to. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: results_per_page does not work properly
thanks. that seemed to do the trick. it would be nice to see the displaying_results_from/displaying_result_to feature implemented. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
exception error running syncdb
Go an error running the following: $ python manage.py syncdb Creating table auth_message Creating table auth_group Creating table auth_user Creating table auth_permission Creating many-to-many tables for Group model Creating many-to-many tables for User model Creating table django_content_type Creating table django_session Creating table django_site You just installed Django's auth system, which means you don't have any superusers defined. Would you like to create one now? (yes/no): yes Username (Leave blank to use 'newpers'): E-mail address: [EMAIL PROTECTED] Password: Password (again): Superuser created successfully. Adding permission 'Group | Can add Group' Adding permission 'Group | Can change Group' Adding permission 'Group | Can delete Group' Adding permission 'User | Can add User' Adding permission 'User | Can change User' Adding permission 'User | Can delete User' Creating example.com Site object Adding permission 'site | Can add site' Adding permission 'site | Can change site' Adding permission 'site | Can delete site' Exception exceptions.AttributeError: "'NoneType' object has no attribute 'print_exc'" in ignored --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
