Re-target to Python 3.14, optimistically

Author: emmatyping

peps/pep-0784.rst

@@ -4,8 +4,8 @@ Author: Emma Harper Smith <emma@python.org>
 Sponsor: Gregory P. Smith <greg@krypto.org>
 Status: Draft
 Type: Standards Track
-Created: 04-Apr-2025
-Python-Version: 3.15
+Created: 06-Apr-2025
+Python-Version: 3.14
 
 Abstract
 ========
@@ -212,7 +212,7 @@ Backwards Compatibility
 
 The main compatibility concern is usage of existing standard library
 compression APIs with the existing import names. These names will be
-deprecated, and will be removed in 3.25. Given the long deprecation period,
+deprecated, and will be removed in 3.24. Given the long deprecation period,
 most users will likely migrate to the new import names well before then.
 Additionally, a libCST codemod can be provided to automatically rewrite
 imports, easing the migration.
@@ -271,7 +271,7 @@ Should we keep old compression imports?
 
 It would be confusing to indefinitely have ``lzma`` and ``compression.lzma``
 simultaneously. Ideally, ``import lzma`` should emit a deprecation for a future
-Python version (maybe 3.25?). But should that deprecation exist indefinitely?
+Python version (maybe 3.24?). But should that deprecation exist indefinitely?
 Should the old import names (e.g. ``import lzma``) eventually be removed? If
 so, at which version?