Stephen J. Turnbull wrote:
Hi Alan, It occurred to me that Django template widgets are very flexible. It may be possible to customize the template to accomplish this task. In that case, the customized template would be kept in a place that doesn't get overwritten in an upgrade, reducing the maintenance cost (unless either Postorius or Django changes the template in a way that seems unlikely to me). I'll try to take a look at that over the holiday break -- that has the advantage that I just document how we did it for you, and tell any future requests to RTFM and DIY. ;-)
Many thanks for your effort especially during the long holiday. Really appreciate.
I agree, you need to be disciplined about what changes you are willing to develop and maintain. This one seemed to me to be over that bar, especially since you can put it in and not suffer too greatly if it gets reverted in a upgrade and the maintainers don't notice.
We do not always have full control of what we are willing to do. It is kind of a Pandora's box. Opening it up may lead to other requests which may no longer be patches but changes potentially conflicting with future upgrade. It is ok if people here recognize that we should have our own developers to participate in this kind of changes and also the maintenance but it is not the culture here. Particularly developers here are much more experienced in Win, C#, .NET than Linux, Python.