Don't create .python-version in workspace subprojects

[bluss]

I suggest that .python-version should not be created in subprojects in a workspace. The workspace root should contain this file already, and subprojects should not have them. The current version of uv creates this file when initing a new workspace member, and the user can/should delete the file afterwards - if I understand correctly.

uv 0.4.17

[charliermarsh]

This makes sense to me.

[dimitrivinet]

First time contributor here, didn't think it would send a message here 😅
Realized I don't have the correct format for the commit message, but how does this look ?

[konstin]

We don't have a particular format for commit messages, just try to write a short description of what got fixed or what got changed.

(Note that this issue is implemented by #7815)

[zanieb]

And this already overlaps with some other in-flight work.

I'm actually not entirely sure about this, since a subproject can have different Python requirements it might make sense to be able to run it on another version? If we moved this metadata into the pyproject.toml would we still ban this?

[bluss]

I think that uv init should not create this file because it's very redundant in subfolders of workspaces in my projects. To permit having it/using it - another issue?

[zanieb]

Ah I see why I agreed on first read — yes I don't think uv init should create the redundant file. I think uv python pin in a subdirectory is "another question".