Thadeus, this is an improvement for code organization and less use of memory, I dont think it breaks compatibility. because there are no place in actual documentation where you can find info about using subfolders. Massimo said sometime ago that subfolders was "reserved" for future implementation. This future is now!
I think code organization with memory usage improvement is better than simply subfolders with models that will be always executed, even if they are not needed. May be we can have some king of compatibility check "run_in_model_compatibility = True" at some place, but. One thing we can always have in mind: Changes in undocumented features or bug fixing cannot be considered break of compatibility this is just the wrong usage, we ran in to this same issue when URL was changed. The way web2py imports all the models to memory is bad to performance, the new style is very good and enough. I am testing it now and I think it will be very productive. How can we manage this kind of interest conflict? -- Bruno Rocha [ About me: http://zerp.ly/rochacbruno ]
