Re: Making ".only()" a bit smarter

2013-07-23 Thread Pablo Recio
Yeah, you might be right. It just feels weird that if I'm trying to fetch *only* a FK, it needs to do a second lookup. But explicit is better than implicit indeed. On 19 July 2013 21:48, Michal Petrucha wrote: > On Fri, Jul 19, 2013 at 01:02:34PM +0100, Pablo Recio

Re: Confusion around generic views queryset cloning.

2013-07-23 Thread Hanne Moa
On 22 July 2013 10:37, Loic Bistuer wrote: > I updated the PR to do away with the public `clone()` method. > > As long as we have a long-term goal for a `QuerySet.clone()` method, I'm > happy. > > If we plan on changing the cloning behavior, now is effectively a bad

Re: Custom Chainable QuerySets (#20625)

2013-07-23 Thread Loic Bistuer
I thought of a third option that I think strikes the right balance between convenience and flexibility. Please see the following comment: https://github.com/django/django/pull/1328#issuecomment-21400832 -- Loic -- You received this message because you are subscribed to the Google Groups

Re: Deprecate FCGI support in Django 1.7

2013-07-23 Thread Tim Graham
Here's a ticket and pull request for the deprecation. On Tuesday, July 23, 2013 1:19:28 AM UTC-4, Some Developer wrote: > > On 23/07/13 02:07, Curtis Maloney wrote: > > Well, having started looking over

Multi-tenancy with different databases

2013-07-23 Thread Fellipe Henrique
Hi all, I just have problem to use multi-tenancy, with different databases... I have one database, with contains all my users... for each user, I have a different database to use... How can I do this? I can't use schemas, because I'm using a legacy database (firebird) with no support to

Re: Multi-tenancy with different databases

2013-07-23 Thread Andre Terra
Hi Fellipe, I'm sorry but you've e-mailed the wrong Google group. Questions about the use of Django should be directed to django-users, while django-developers is dedicated solely for the development of Django itself. Cheers, AT On Tue, Jul 23, 2013 at 3:23 PM, Fellipe Henrique

Re: Multi-tenancy with different databases

2013-07-23 Thread Fellipe Henrique
sorry, my bad... :( On Tuesday, July 23, 2013 3:31:08 PM UTC-3, Andre Terra wrote: > > Hi Fellipe, > > I'm sorry but you've e-mailed the wrong Google group. > > Questions about the use of Django should be directed to django-users, > while django-developers is dedicated solely for the development

Re: [GSoC] Revamping validation framework and merging django-secure once again

2013-07-23 Thread Christopher Medrela
Progress: I've implemented registering entry points. Now there is `django.core.checks.register(callable)` function. There is no `run_in_development` and `run_in_production` arguments. I've also rewritten mechanism of triggering checking framework -- `BaseCommand.validate` calls

manage.py and pyc's

2013-07-23 Thread Jan Vilhuber
In our project, we typically deploy our django app without py's, except for a few select ones (manage,py for example). I recently added a few management/commands to a few of the apps in my project, and discovered that manage.py does not find them, as it looks only for .py files (ignoring

Re: manage.py and pyc's

2013-07-23 Thread Chris Church
It looks like this issue has been marked as wontfix in https://code.djangoproject.com/ticket/14952 However, I've used the following in manage.py to support running management commands when distributing only .pyc files: https://gist.github.com/cchurch/6067733 On Tue, Jul 23, 2013 at 6:29 PM,

Re: [GSoC] Revamping validation framework and merging django-secure once again

2013-07-23 Thread Russell Keith-Magee
On Wed, Jul 24, 2013 at 4:17 AM, Christopher Medrela < chris.medr...@gmail.com> wrote: > Progress: I've implemented registering entry points. Now there is > `django.core.checks.register(callable)` function. There is no > `run_in_development` and `run_in_production` arguments. I've also rewritten

Re: Deprecate FCGI support in Django 1.7

2013-07-23 Thread Joe Tennies
Is there a specific reason to call this "django-fastcgi"? I think it should most likely be a generic wsgi to fastcgi binding, right? Or is this project mainly the django management commands? On Jul 22, 2013 8:07 PM, "Curtis Maloney" wrote: > Well, having started

Re: Deprecate FCGI support in Django 1.7

2013-07-23 Thread Curtis Maloney
Well, mostly to indicate it's primary focus is on providing a FastCGI server for Django. I'm quite happy to keep it app agnostic, and be a general FastCGI->WSGI publisher... On 24 July 2013 15:04, Joe Tennies wrote: > Is there a specific reason to call this