Merge remote-tracking branch 'origin/main' into exp-backoff

Doc/library/datetime.rst

@@ -1079,6 +1079,24 @@ Other constructors, all class methods:
  time tuple. See also :ref:`strftime-strptime-behavior` and
  :meth:`datetime.fromisoformat`.
 
+ .. versionchanged:: 3.13
+
+ If *format* specifies a day of month without a year a
+ :exc:`DeprecationWarning` is now emitted. This is to avoid a quadrennial
+ leap year bug in code seeking to parse only a month and day as the
+ default year used in absence of one in the format is not a leap year.
+ Such *format* values may raise an error as of Python 3.15. The
+ workaround is to always include a year in your *format*. If parsing
+ *date_string* values that do not have a year, explicitly add a year that
+ is a leap year before parsing:
+
+ .. doctest::
+
+ >>> from datetime import datetime
+ >>> date_string = "02/29"
+ >>> when = datetime.strptime(f"{date_string};1984", "%m/%d;%Y") # Avoids leap year bug.
+ >>> when.strftime("%B %d") # doctest: +SKIP
+ 'February 29'
 
 
 Class attributes:
@@ -2657,6 +2675,25 @@ Notes:
  for formats ``%d``, ``%m``, ``%H``, ``%I``, ``%M``, ``%S``, ``%j``, ``%U``,
  ``%W``, and ``%V``. Format ``%y`` does require a leading zero.
 
+(10)
+ When parsing a month and day using :meth:`~.datetime.strptime`, always
+ include a year in the format. If the value you need to parse lacks a year,
+ append an explicit dummy leap year. Otherwise your code will raise an
+ exception when it encounters leap day because the default year used by the
+ parser is not a leap year. Users run into this bug every four years...
+
+ .. doctest::
+
+ >>> month_day = "02/29"
+ >>> datetime.strptime(f"{month_day};1984", "%m/%d;%Y") # No leap year bug.
+ datetime.datetime(1984, 2, 29, 0, 0)
+
+ .. deprecated-removed:: 3.13 3.15
+ :meth:`~.datetime.strptime` calls using a format string containing
+ a day of month without a year now emit a
+ :exc:`DeprecationWarning`. In 3.15 or later we may change this into
+ an error or change the default year to a leap year. See :gh:`70647`.
+
 .. rubric:: Footnotes
 
 .. [#] If, that is, we ignore the effects of Relativity

Doc/library/unittest.rst

@@ -1880,8 +1880,8 @@ Loading and running tests
  Python identifiers) will be loaded.
 
  All test modules must be importable from the top level of the project. If
- the start directory is not the top level directory then the top level
- directory must be specified separately.
+ the start directory is not the top level directory then *top_level_dir*
+ must be specified separately.
 
  If importing a module fails, for example due to a syntax error, then
  this will be recorded as a single error and discovery will continue. If
@@ -1901,9 +1901,11 @@ Loading and running tests
  package.
 
  The pattern is deliberately not stored as a loader attribute so that
- packages can continue discovery themselves. *top_level_dir* is stored so
- ``load_tests`` does not need to pass this argument in to
- ``loader.discover()``.
+ packages can continue discovery themselves.
+
+ *top_level_dir* is stored internally, and used as a default to any
+ nested calls to ``discover()``. That is, if a package's ``load_tests``
+ calls ``loader.discover()``, it does not need to pass this argument.
 
  *start_dir* can be a dotted module name as well as a directory.
 
@@ -1930,6 +1932,9 @@ Loading and running tests
  *start_dir* can not be a :term:`namespace packages <namespace package>`.
  It has been broken since Python 3.7 and Python 3.11 officially remove it.
 
+ .. versionchanged:: 3.13
+ *top_level_dir* is only stored for the duration of *discover* call.
+
 
  The following attributes of a :class:`TestLoader` can be configured either by
  subclassing or assignment on an instance:

Include/internal/pycore_bytes_methods.h

@@ -32,8 +32,12 @@ extern PyObject *_Py_bytes_rfind(const char *str, Py_ssize_t len, PyObject *args
 extern PyObject *_Py_bytes_rindex(const char *str, Py_ssize_t len, PyObject *args);
 extern PyObject *_Py_bytes_count(const char *str, Py_ssize_t len, PyObject *args);
 extern int _Py_bytes_contains(const char *str, Py_ssize_t len, PyObject *arg);
-extern PyObject *_Py_bytes_startswith(const char *str, Py_ssize_t len, PyObject *args);
-extern PyObject *_Py_bytes_endswith(const char *str, Py_ssize_t len, PyObject *args);
+extern PyObject *_Py_bytes_startswith(const char *str, Py_ssize_t len,
+ PyObject *subobj, Py_ssize_t start,
+ Py_ssize_t end);
+extern PyObject *_Py_bytes_endswith(const char *str, Py_ssize_t len,
+ PyObject *subobj, Py_ssize_t start,
+ Py_ssize_t end);
 
 /* The maketrans() static method. */
 extern PyObject* _Py_bytes_maketrans(Py_buffer *frm, Py_buffer *to);

Include/internal/pycore_pylifecycle.h

@@ -116,6 +116,22 @@ PyAPI_FUNC(char*) _Py_SetLocaleFromEnv(int category);
 // Export for special main.c string compiling with source tracebacks
 int _PyRun_SimpleStringFlagsWithName(const char *command, const char* name, PyCompilerFlags *flags);
 
+
+/* interpreter config */
+
+// Export for _testinternalcapi shared extension
+PyAPI_FUNC(int) _PyInterpreterConfig_InitFromState(
+ PyInterpreterConfig *,
+ PyInterpreterState *);
+PyAPI_FUNC(PyObject *) _PyInterpreterConfig_AsDict(PyInterpreterConfig *);
+PyAPI_FUNC(int) _PyInterpreterConfig_InitFromDict(
+ PyInterpreterConfig *,
+ PyObject *);
+PyAPI_FUNC(int) _PyInterpreterConfig_UpdateFromDict(
+ PyInterpreterConfig *,
+ PyObject *);
+
+
 #ifdef __cplusplus
 }
 #endif