On Fri, May 22, 2009 at 12:51 PM, Abhishoka wrote:
>
> Hi:
>
> We are a non-profit charity organization having 25+ websites and want
> to maintain a centralized database for the various events happening at
> different places. The database (MySql) has been implemented and we use
> the django frame
Hi:
We are a non-profit charity organization having 25+ websites and want
to maintain a centralized database for the various events happening at
different places. The database (MySql) has been implemented and we use
the django framework admin module to communicate with the database.
Our different
I have submitted a patch for ticket 10834,
http://code.djangoproject.com/ticket/10834
Nicolas and Malcolm both checked it out and approved it. That should
fulfill the requirement for the interim ticket.
For the project timeline/marching orders, here is what I know so far.
05/23 - 05/27 - I take
Yes, he really works with me.
Well, I supose I have some advance last day. The majority of the admin
application we created that do not appear on the index view for non-
superusers was the ones that we changed the app_name.
We maked this to put verbose names in the title on 'fieldsets' of any
ap
Ok, that makes sense that copy.deepcopy calls each object's
__deepcopy__ method. But we have a loop:
ModelChoiceField->widget->ModelChoiceIterator->ModelChoiceField
Do we want the copying of the widget to make a copy of the
ModelChoiceIterator? Regardless of whether we make a copy of the
Mode
On Thu, May 21, 2009 at 9:09 AM, Margie wrote:
>
> I don't think we are calling Widget.__deepcopy__() at this point. I
> think we are just calling the plain old python copy.deepcopy().
> That's what I see in pdb. I don't think we really want to be
> recursively copying all of the data structure
I don't think we are calling Widget.__deepcopy__() at this point. I
think we are just calling the plain old python copy.deepcopy().
That's what I see in pdb. I don't think we really want to be
recursively copying all of the data structures. We start out with a
ModelChoiceField pointing to a wid
On Thu, May 21, 2009 at 12:35 AM, Margie wrote:
>
> In the process of doing some debugging into the django source, I've
> come across something in the source that maybe someone can explain.
> I think this may be a subtle source bug, or at least something that
> may cause problems with advanced u
In the process of doing some debugging into the django source, I've
come across something in the source that maybe someone can explain.
I think this may be a subtle source bug, or at least something that
may cause problems with advanced usage (as described below) - not
positive though.
In class
