Hi all,
So, I've been working on a Django branch [1] to implement the approach
to pluggable user models that was decided upon earlier this year [2]
[1] https://github.com/freakboy3742/django/tree/t3011
[2] https://code.djangoproject.com/wiki/ContribAuthImprovements
The user-swapping code itself
On 25 août 2012, at 10:15, Russell Keith-Magee wrote:
> We *could* just mark the affected tests that require auth.User as
> "skipUnless(user model == auth.User)", but that would mean some
> projects would run the tests, and some wouldn't. That seems like an
> odd inconsistency to me -- the tests e
First time contributing to Django, but I've used it for a few years now.
I'd like to enhance to the dev runserver to persist a socket through
autoreloads. I've submitted a ticket and a pull request on Github is
linked in the ticket.
If someone wouldn't mind reviewing the code and giving me so
On 25 elo, 19:10, Dan LaMotte wrote:
> First time contributing to Django, but I've used it for a few years now.
> I'd like to enhance to the dev runserver to persist a socket through
> autoreloads. I've submitted a ticket and a pull request on Github is
> linked in the ticket.
>
> If someone wou
I have done some more ORM refactoring work. I thought it would be a
good idea to post a summary of what is going on.
First, I haven't committed the utils.tree refactoring patch I was
planning to commit [https://github.com/akaariai/django/commits/
refactor_utils_tree]. The reason is that I now feel
On Sat, Aug 25, 2012 at 12:35 PM, Anssi Kääriäinen
wrote:
> I have done some more ORM refactoring work. I thought it would be a
> good idea to post a summary of what is going on.
>
> First, I haven't committed the utils.tree refactoring patch I was
> planning to commit [https://github.com/akaariai
Hi Tai,
Thanks for your work and sorry for the late answer. I just had the time to
review the discussion.
In my opinion, option 2 is reasonable. I'm -0 on a stream_content keyword
argument for HttpResponse. I +1 on adding a separate HttpStreamingResponse
class, because it better reflects the
On 25 elo, 23:22, Aymeric Augustin
wrote:
> In my opinion, option 2 is reasonable. I'm -0 on a stream_content keyword
> argument for HttpResponse. I +1 on adding a separate HttpStreamingResponse
> class, because it better reflects the difference in behavior, and because it
> makes it possible t
On Sat, Aug 25, 2012 at 4:24 PM, Aymeric Augustin
wrote:
> On 25 août 2012, at 10:15, Russell Keith-Magee wrote:
>
>> We *could* just mark the affected tests that require auth.User as
>> "skipUnless(user model == auth.User)", but that would mean some
>> projects would run the tests, and some would
On Aug 25, 2012, at 1:15 AM, Russell Keith-Magee wrote:
> Hi all,
>
> So, I've been working on a Django branch [1] to implement the approach
> to pluggable user models that was decided upon earlier this year [2]
>
> [1] https://github.com/freakboy3742/django/tree/t3011
> [2] https://code.django
Once #17365 (as per https://github.com/jezdez/django-discover-runner) is
implemented it will be a lot cleaner, since that splits out 1 & 2 from 3.
Lets call them Django, Django api compatible, and Django project api
Three things hammered home for me that Carl's approach is the correct way
to do
11 matches
Mail list logo
