That's a solution :-) Thanks!
I personally create my projects/apps via a script with customized templates.
But for new comers, they will suffer from adding "_app" to their main app.
I know i did at one point.:-)
All the best.
On Tue, Mar 15, 2016 at 2:26 AM, Curtis Maloney
Well, you could use:
mkdir my_client_name
django-admin startproject project my_client_name/
So it will create my_client_name/project/settings.py, and leave the
namespace clear for you to create my_client_name/my_client_name/ as your
app...
--
Curtis
On 15/03/16 10:51, Ramez Ashraf wrote:
That sounds pretty fair, particularly since the new default settings
provide a great ootb experience.
Thanks for your feedback, keep up the great work !
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To
FMPOV, the default template from Django influences:
- the use of settings in .py files over the environment variables;
- the use of manage.py over django-admin command;
- the merge of the "core application" and the project (settings/wsgi...)
in one django app;
This is very personal and based
On Saturday, March 12, 2016 at 5:29:55 PM UTC+1, is_null wrote:
>
> I know it's too opinionated to add that to django, but I'd like to
> open a discussion here and perhaps there's something we might find
> worth changing in django's default project template.
>
Imo it should stay as minimal as
