I commented on the issue, but this is the intended behavior. The order of execution is fixed (though you can determine that fixed order with proper naming of files and folders) -- response.models_to_run is only intended for specification of *which* files get executed, not in which order. Do you have a use case where you need to dynamically change the order of model execution?
I think what you call a "workaround" (i.e., putting the model file that is common to two controllers in its own folder) is actually the cleaner design -- that model file doesn't belong to only one controller or the other, so it doesn't belong in a folder associated with only one of the controllers. Anthony On Friday, October 4, 2013 12:38:10 AM UTC-4, Tim Richardson wrote: > > https://code.google.com/p/web2py/issues/detail?id=1702 > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
