Re: Invalid deleted forms in formsets break form data access

The worst in this situation is that we have 2012 3Q in the yard but the issue still open :( Четвер, 12 серпня 2010 р. 10:32:32 UTC+3 користувач Tomi Pieviläinen написав: > > I first approached the users-list to find out if I was simply doing > something wrong, but seems like there's no (obvious

Moving forward with Serialization.

Hi all, During Piotr's GSOC addressing customizable serialization I've been continued to work on my own implementation. I've now got what feels to me to be a natural conclusion of the design, which is the 'forms' branch of the 'django-serializers'

Re: M2M with to_fields (ticket #18823)

The wrong rows being deleted is a possibility. Here's an example: class Through(models.Model): two = models.ForeignKey('Model2', to_field='spot') one = models.ForeignKey('Model1') class Model1(models.Model): name = models.CharField(max_length=100) class Model2(models.Model): spot

Tabular inline improvement

Hello all, I have a suggestion for improving the tabular inline view of the admin site (contained in /contrib/admin/templates/admin/edit_inline/tabular.html). I recently overloaded this template for my own purposes, and am wondering if the Django community would find my changes useful. If so, I

Auto-import support for models and other objects in shell

'Ello. I'm gauging support for a tiny new feature, or at least a refactoring of an internal API that will allow the feature to be developed without code duplication. I'd like to stop typing import statements for all of my models and other common stuff into my django shell. In fact, I'd love for

Re: Auto-import support for models and other objects in shell

On Tue, Aug 28, 2012 at 2:40 PM, Phill Tornroth wrote: > 'Ello. > > I'm gauging support for a tiny new feature, or at least a refactoring of > an internal API that will allow the feature to be developed without code > duplication. I'd like to stop typing import statements for all of my models > an

Re: Auto-import support for models and other objects in shell

Totally fair, couple of things: 1. For backward compatibility and the confusion you mentioned, I'd suggest this be not enabled by default. Let people who want the feature (the people who download shell_plus for instance) enable it. My pull request leaves it totally off by default, retaining cur

Re: Auto-import support for models and other objects in shell

Hi Phill, On 08/28/2012 03:51 PM, Phill Tornroth wrote: > 2. Are you also -1 on making it easier for projects like shell_plus to > add locals to the shell? What's happening right now is pretty > unfortunate. I can only see upside in an adjustment to the internal API > that doesn't make this kind o

Re: M2M with to_fields (ticket #18823)

Hi Peter, Thanks for that; I've just marked the ticket as a release blocker, so at the very worst, this should be corrected for the 1.5 release. Yours, Russ Magee %-) On Tue, Aug 28, 2012 at 11:56 PM, peter wrote: > The wrong rows being deleted is a possibility. Here's an example: > > class Thr

Re: Auto-import support for models and other objects in shell

I'm in complete agreement with Alex. -1 from me. Explicit is better than implicit, and to my mind, hiding imports just complicates the learning curve associated with Django's package tree. If you *really* want this, there are hooks into ipython et al that can do this; I don't see it as something a

Re: Moving forward with Serialization.

Do you know Colander? https://github.com/Pylons/colander - D 2012/8/28 Tom Christie > Hi all, > > During Piotr's GSOC addressing customizable serialization I've been > continued to work on my own implementation. > I've now got what feels to me to be a natural conclusion of the design, > whi

Re: Auto-import support for models and other objects in shell

Thanks all. This has been a helpful and enlightening glimpse into the values and priorities the Django project is stewarded with. I appreciate the time and attention. -Phill On Tuesday, August 28, 2012 4:53:26 PM UTC-7, Russell Keith-Magee wrote: > > I'm in complete agreement with Alex. -1 from

Re: Moving forward with Serialization.

Hi Tom, I've knocked around ideas of my own (internally, and on #django) related to serialisation: it's something I've had lots to think about, since until recently, most of my django work was in JSON apis. I personally think that Forms are already the place that should handle (de)serialisatio

Re: Moving forward with Serialization.

Not sure that I phrased the last bit right: I think my repose framework is a step in the right direction, but even so I think it probably doesn't do things the right way. Matt. On Wednesday, August 29, 2012 2:57:35 PM UTC+9:30, schinckel wrote: > > Hi Tom, > > I've knocked around ideas of my o

Re: Yak shaving the test framework on the way to pluggable user models (#3011)

On Saturday, August 25, 2012 5:32:08 PM UTC-7, Russell Keith-Magee wrote: > > 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(use