On 06/10/10 16:02, Russell Keith-Magee wrote:
Yes - questions of usage and requests for design guidance should be
directed to Django-users.
Unless you have a specific suggestion for how to move ticket #1946
forward, this isn't a topic for django-developers.
Sorry, I should have been more clear.
What I'm trying to do is solicit suggestions from django developers as
to how I *can* move ticket #1946 forward. I can find a way to work
around it in my own project, but it would be ideal to solve it on the
Django side, for everybody.
I mentioned there were three possible suggestions in the ticket
discussion as to how to solve the problem. If a Django developer can
give me some guidance as to what approach seems to be the best long-term
solution, I'm happy to try my hand at writing a patch that can hopefully
be incorporated into the codebase.
Cheers,
Tom
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
