Re: Displaying (some) M2M fields with through models specified

2014-05-25 Thread Russell Keith-Magee
Hi Alex, Short version - Broadly speaking, this is a feature we've discussed many times over many years, and we've accepted as a good idea in principle. It's logged as ticket #9475 [1]. There is some additional discussion on the original ticket that introduced m2m through models (#6095 [2]). The

Displaying (some) M2M fields with through models specified

2014-05-25 Thread Alexander Hill
Hi all, Currently, only M2M fields without custom intermediary models can use the normal Django M2M form machinery. If you define your own intermediary models, you need to use inlines instead. I would like to allow fields with custom through models to use the regular M2M field/widget automaticall

Re: [GSOC] Weekly update

2014-05-25 Thread Daniel Pyrathon
Hi All, Just to make you know, I have put up the current _meta API documentation here: http://162.219.6.191:8000/ref/models/meta.html?highlight=_meta As always, feel free to ask questions. Daniel On Monday, May 26, 2014 1:26:27 AM UTC+2, Daniel Pyrathon wrote: > > Hi Josh, > > The meta API spec

Re: [GSOC] Weekly update

2014-05-25 Thread Daniel Pyrathon
Hi Josh, The meta API specified in the docs (https://github.com/PirosB3/django/blob/meta_documentation/docs/ref/models/meta.txt) is the current API. I have documented this in order to understand more of the current implementation and it will be good to show a comparison when a new meta API wi

Re: [GSOC] Weekly update

2014-05-25 Thread Daniel Pyrathon
Hi Chris, Oh sorry about that! big typo over there. Modifying the gist. Thanks, Daniel Pyrathon On Saturday, May 24, 2014 7:44:15 AM UTC+2, Chris Beaven wrote: > > Hi Daniel, > > The proposal looks interesting - I've only skimmed it so far but one > question: you mention User.get_model() severa

Re: Why not Single Table Inheritance?

2014-05-25 Thread Craig de Stigter
> If you ignore STI, I think it is quite straightforward to solve this with a parent model class which adds a type field, and manager methods to add the select_related calls and "interpret" the type field properly; so I don't see an immediate need for inclusion in core. Well, you don't need

Re: [cx-oracle-users] cx_Oracle 5.1.3

2014-05-25 Thread Josh Smeaton
Thanks for pointing this out - I was just about to start a new project with oracle 12c and python 3.4, both of which are only now supported. Great timing! On Sunday, 25 May 2014 16:20:21 UTC+10, Shai Berger wrote: > > Hi all, > > This release of cx_Oracle includes fixes the segfaults encountere