-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Markus,
On 10/12/2011 10:30 AM, Markus Gattol wrote: > django-admin.py startproject would create site_root and project_root > put as this patch intends, one could always easily rename site_root to > whatever he wants. example.com is entirely decoupled anyway and can be > named anything. > > Maybe it is not bad having project_root as a fix name at this location > in the filesystem tree as it makes it easy to reference things -- not > just for people but also scripts and such. I am generally against to > much rules/conventions but in this case I think having some fixed name > at a fixed location would make things easier (even if it is just for > new people to grasp things). Since "project_root" is the actual importable Python package name, I don't think it's a good idea to have it be a fixed name; it should be an appropriately-chosen package name for each individual project. I guess we could consider always using the same name for the outer directory, but I think it's better to reuse the package name for that directory. It means you can run startproject twice from within the same directory without overwriting things, and I think it just makes intuitive sense that the output of startproject is a directory with the same name you just gave it. Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6VxIwACgkQ8W4rlRKtE2f9ggCeOgOpcbsGHw4h/zuUs9o5J8eV xA0AnisROi6OlHIRG2UR9MkWw7fWXDRs =f6cP -----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 [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.
