Feedback on Django Command-Line Interface Proposals

Based on the Django 5.1 documentation, I can provide some context about the current command-line utilities in Django, which might help inform the discussion around your proposals.

Currently, Django offers two main command-line interfaces:

• django-admin: The primary command-line utility for administrative tasks
• manage.py: A project-specific script that sets the DJANGO_SETTINGS_MODULE environment variable

The documentation also mentions that python -m django can be used as an alternative to both of these options.

Regarding Your Proposals

Your proposals aim to streamline Django's command-line interface by:

1. Adding a django command as an alias for django-admin
2. Supporting configuration in pyproject.toml for settings modules
3. Updating documentation to prefer django over django-admin
4. Suggesting configured django instead of python manage.py
5. Potentially removing manage.py from project templates

These changes would align Django with modern Python packaging practices and potentially simplify the developer experience, especially when working with tools like pipx and uvx.

The current documentation emphasizes that manage.py is generally easier to use for single-project work, while django-admin with environment variables or the --settings option is better for multi-project scenarios. Your proposal would potentially unify these approaches through configuration.

While I can't provide direct community feedback on these proposals, they do address some of the complexity in Django's current command-line interface structure, which requires developers to choose between different command options depending on their context.

For further discussion, you might want to consider how these changes would impact backward compatibility and the learning curve for new Django developers who are accustomed to the manage.py pattern from tutorials and existing documentation.