Pin .python-version in uv init (#6869)

## Summary

I'm not convinced that the behavior is correct as-implemented. When the
user passes a `--python >=3.8` or we discover a `requires-python` from
the workspace, we're currently writing that request out to
`.python-version`. I would probably rather that we write the resolved
patch version?

Closes #6821.

crates/uv-cli/src/lib.rs

@@ -2184,6 +2184,14 @@ pub struct InitArgs {
     #[arg(long)]
     pub no_readme: bool,
 
+    /// Do not create a `.python-version` file for the project.
+    ///
+    /// By default, uv will create a `.python-version` file containing the minor version of
+    /// the discovered Python interpreter, which will cause subsequent uv commands to use that
+    /// version.
+    #[arg(long)]
+    pub no_pin_python: bool,
+
     /// Avoid discovering a workspace and create a standalone project.
     ///
     /// By default, uv searches for workspaces in the current directory or any

crates/uv-python/src/version_files.rs

@@ -94,7 +94,7 @@ impl PythonVersionFile {
 
     /// Create a new representation of a version file at the given path.
     ///
-    /// The file will not any versions; see [`PythonVersionFile::with_versions`].
+    /// The file will not any include versions; see [`PythonVersionFile::with_versions`].
     /// The file will not be created; see [`PythonVersionFile::write`].
     pub fn new(path: PathBuf) -> Self {
         Self {