-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Alec,
On 10/12/2011 06:38 AM, Alec Taylor wrote: > Backwards compatibility is easily solved, include an upgrade.py file > which is called if project rootfolder has settings.py. upgrade.py > would fix the directory structure Thanks for the suggestion! I don't think it's quite that simple, as we can't assume that every upgrading project has maintained exactly the default startproject layout - I think quite a significant percentage don't. And we also don't know which style of import the project is using (with or without project prefix) for various things, and inconsistent imports would be tricky to fix automatically. We need to provide migration help for all projects that currently work, not just for the previous default layout. I think we're better off carefully documenting how the location of things in the new setup determines how they can be imported, and letting projects make the necessary changes themselves, rather than trying to provide an upgrade script that isn't likely to have a real high success rate. Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6VjcUACgkQ8W4rlRKtE2fRqACeOAL+Etvd2n2IqyV/aUVPQ4EY 09wAoJqbQ6NcCH0QD46zE8q/pRCUE1Ad =D0va -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
