(I basically agree with everyone in this thread, but I collected some data in the thread @zanieb pointed me from to here, so I am shamelessly reposting my comment from there here:)

For reference,

In Python, default file names vary a bit with the domain, and hence one's expectations might be shaped in various ways. app.py is indeed common, with currently about 721.000 app.py files on GitHub.
Still, main.py is an even more common name. At the time of writing, there are 2.2 million main.py files on GitHub. Interestingly, this is exactly because 'main' is a commonly used name in the Python world, like main(), __main__, or __main__.py. To adhere to this pythonic naming scheme and avoid surprises, main.py should in my opinion be default in uv init.
I do not feel like there is one, universally accepted best practice for naming your first file. I think we would therefore need a command line argument for naming the default file. The command line option should also include a way to disable creating a default file altogether. Currently, one needs to advise uv init && rm hello.py, which seems unnecessarily convoluted and is not portable to PowerShell, so portable instructions require duplication. m(
The default file is handy if one starts from scratch, but cumbersome if there is an existing codebase. With an existing code base, the use case is to introduce uv to it, not build something new. In projects with preexisting code, uv would ideally detect the presence of a codebase and not create a default file. This should be equivalent to using the deactivation functionality mentioned in 4.

Avoid creating main.py in existing projects #6750

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Avoid creating `main.py` in existing projects #6750