Django startapp Directory Creation Enhancement

Based on the Django documentation for the startapp command, your proposed enhancement makes sense and addresses a common friction point.

Current Behavior

Currently, when using the startapp command with a destination directory that doesn't exist, Django returns an error:

PLAINTEXTCopied
CommandError: Destination directory '/Users/bruno/.../apps/myapp' does not exist, please create it first.

The documentation states:

If the optional destination is provided, Django will use that existing directory rather than creating a new one.

This requires users to manually create the directory structure first (mkdir apps/myapp) before running the command.

Proposed Enhancement

Your pull request to automatically create the destination directory if it doesn't exist would improve the developer experience by:

1. Eliminating the need for a separate mkdir command
2. Streamlining the app creation workflow
3. Maintaining consistency with other tools that typically create directories as needed

Considerations

This change seems desirable because:

1. It reduces friction in the development workflow
2. It's an intuitive behavior that users would expect
3. It doesn't break existing functionality (directories that already exist will still work)
4. It aligns with the principle of making common tasks easier

The change appears to be a reasonable enhancement to both the startapp and startproject commands that would improve the developer experience without introducing significant complexity or changing the core functionality.