ffi: fix names of _Base datetime structs

This commit is contained in:
David Hewitt 2022-06-02 09:27:19 +01:00
parent a388901fc6
commit 6741104762
2 changed files with 5 additions and 4 deletions

View File

@ -36,6 +36,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fix "raw-ident" structs (e.g. `#[pyclass] struct r#RawName`) incorrectly having `r#` at the start of the class name created in Python. [#2395](https://github.com/PyO3/pyo3/pull/2395) - Fix "raw-ident" structs (e.g. `#[pyclass] struct r#RawName`) incorrectly having `r#` at the start of the class name created in Python. [#2395](https://github.com/PyO3/pyo3/pull/2395)
- Fix case where `ValueError` without message could be raised by the `#[derive(FromPyObject)]` generated implementation for a tuple struct. [#2414](https://github.com/PyO3/pyo3/pull/2414) - Fix case where `ValueError` without message could be raised by the `#[derive(FromPyObject)]` generated implementation for a tuple struct. [#2414](https://github.com/PyO3/pyo3/pull/2414)
- Fix compile failure when using `#[pyo3(from_py_with = "pouf")]` in on a field in a `#[derive(FromPyObject)]` struct. [#2414](https://github.com/PyO3/pyo3/pull/2414) - Fix compile failure when using `#[pyo3(from_py_with = "pouf")]` in on a field in a `#[derive(FromPyObject)]` struct. [#2414](https://github.com/PyO3/pyo3/pull/2414)
- Fix FFI definitions `_PyDateTime_BaseTime` lacking leading underscores in their names. [#2421](https://github.com/PyO3/pyo3/pull/2421)
## [0.16.5] - 2022-05-15 ## [0.16.5] - 2022-05-15

View File

@ -42,7 +42,7 @@ pub struct PyDateTime_Delta {
#[repr(C)] #[repr(C)]
#[derive(Debug, Copy, Clone)] #[derive(Debug, Copy, Clone)]
/// Structure representing a `datetime.time` without a `tzinfo` member. /// Structure representing a `datetime.time` without a `tzinfo` member.
pub struct PyDateTime_BaseTime { pub struct _PyDateTime_BaseTime {
pub ob_base: PyObject, pub ob_base: PyObject,
#[cfg(not(PyPy))] #[cfg(not(PyPy))]
pub hashcode: Py_hash_t, pub hashcode: Py_hash_t,
@ -60,7 +60,7 @@ pub struct PyDateTime_BaseTime {
/// # Safety /// # Safety
/// ///
/// Care should be taken when reading the `tzinfo` field of this type. If the time does not have a /// Care should be taken when reading the `tzinfo` field of this type. If the time does not have a
/// tzinfo then the Python interpreter is free to allocate it as a [PyDateTime_BaseTime]. /// tzinfo then the Python interpreter is free to allocate it as a [_PyDateTime_BaseTime].
pub struct PyDateTime_Time { pub struct PyDateTime_Time {
pub ob_base: PyObject, pub ob_base: PyObject,
#[cfg(not(PyPy))] #[cfg(not(PyPy))]
@ -87,7 +87,7 @@ pub struct PyDateTime_Date {
#[repr(C)] #[repr(C)]
#[derive(Debug, Copy, Clone)] #[derive(Debug, Copy, Clone)]
/// Structure representing a `datetime.datetime` without a `tzinfo` member. /// Structure representing a `datetime.datetime` without a `tzinfo` member.
pub struct PyDateTime_BaseDateTime { pub struct _PyDateTime_BaseDateTime {
pub ob_base: PyObject, pub ob_base: PyObject,
#[cfg(not(PyPy))] #[cfg(not(PyPy))]
pub hashcode: Py_hash_t, pub hashcode: Py_hash_t,
@ -105,7 +105,7 @@ pub struct PyDateTime_BaseDateTime {
/// # Safety /// # Safety
/// ///
/// Care should be taken when reading the `tzinfo` field of this type. If the datetime does not have a /// Care should be taken when reading the `tzinfo` field of this type. If the datetime does not have a
/// tzinfo then the Python interpreter is free to allocate it as a [PyDateTime_BaseDateTime]. /// tzinfo then the Python interpreter is free to allocate it as a [_PyDateTime_BaseDateTime].
pub struct PyDateTime_DateTime { pub struct PyDateTime_DateTime {
pub ob_base: PyObject, pub ob_base: PyObject,
#[cfg(not(PyPy))] #[cfg(not(PyPy))]