[INFO] fetching crate cpython 0.7.1...
[INFO] testing cpython-0.7.1 against master#1871252fc8bb672d40787e67404e6eaae7059369 for pr-125151
[INFO] extracting crate cpython 0.7.1 into /workspace/builds/worker-5-tc1/source
[INFO] validating manifest of crates.io crate cpython 0.7.1 on toolchain 1871252fc8bb672d40787e67404e6eaae7059369
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate cpython 0.7.1
[INFO] finished tweaking crates.io crate cpython 0.7.1
[INFO] tweaked toml for crates.io crate cpython 0.7.1 written to /workspace/builds/worker-5-tc1/source/Cargo.toml
[INFO] crate crates.io crate cpython 0.7.1 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded serde_bytes v0.11.5
[INFO] [stderr]   Downloaded rustversion v1.0.5
[INFO] [stderr]   Downloaded python27-sys v0.7.0
[INFO] [stderr]   Downloaded python3-sys v0.7.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 78ea91180b42e1bb47e70fd8a18aca2b48570d9ba9677c9be4961b552f0f2ba5
[INFO] running `Command { std: "docker" "start" "-a" "78ea91180b42e1bb47e70fd8a18aca2b48570d9ba9677c9be4961b552f0f2ba5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "78ea91180b42e1bb47e70fd8a18aca2b48570d9ba9677c9be4961b552f0f2ba5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "78ea91180b42e1bb47e70fd8a18aca2b48570d9ba9677c9be4961b552f0f2ba5", kill_on_drop: false }`
[INFO] [stdout] 78ea91180b42e1bb47e70fd8a18aca2b48570d9ba9677c9be4961b552f0f2ba5
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 99f7e094089ba997afd5fea193924cd8e8095624252c7d4fdf153042431423dd
[INFO] running `Command { std: "docker" "start" "-a" "99f7e094089ba997afd5fea193924cd8e8095624252c7d4fdf153042431423dd", kill_on_drop: false }`
[INFO] [stderr]    Compiling memchr v2.4.1
[INFO] [stderr]    Compiling regex-syntax v0.6.27
[INFO] [stderr]    Compiling libc v0.2.103
[INFO] [stderr]    Compiling cpython v0.7.1 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling paste v1.0.5
[INFO] [stderr]    Compiling num-traits v0.2.14
[INFO] [stderr]    Compiling aho-corasick v0.7.18
[INFO] [stderr]    Compiling regex v1.6.0
[INFO] [stderr]    Compiling python3-sys v0.7.1
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/boolobject.rs:10:1
[INFO] [stdout]     |
[INFO] [stdout] 10  | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: `#[warn(static_mut_refs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBool_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/capsule.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type);
[INFO] [stdout]     | ------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyCapsule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/dict.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyDict_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/list.rs:28:1
[INFO] [stdout]     |
[INFO] [stdout] 28  | pyobject_newtype!(PyList, PyList_Check, PyList_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyList_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/module.rs:33:1
[INFO] [stdout]     |
[INFO] [stdout] 33  | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type);
[INFO] [stdout]     | ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyModule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:56:1
[INFO] [stdout]     |
[INFO] [stdout] 56  | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyLong_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:65:1
[INFO] [stdout]     |
[INFO] [stdout] 65  | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyFloat_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/object.rs:113:44
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) }
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, addr_of_mut!(ffi::PyBaseObject_Type)) }
[INFO] [stdout]     |                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/set.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PySet, PySet_Check, PySet_Type);
[INFO] [stdout]     | ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PySet_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:36:1
[INFO] [stdout]     |
[INFO] [stdout] 36  | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type);
[INFO] [stdout]     | ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyUnicode_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:42:1
[INFO] [stdout]     |
[INFO] [stdout] 42  | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBytes_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/tuple.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyTuple_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/typeobject.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyType, PyType_Check, PyType_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyType_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 13 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.65s
[INFO] running `Command { std: "docker" "inspect" "99f7e094089ba997afd5fea193924cd8e8095624252c7d4fdf153042431423dd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "99f7e094089ba997afd5fea193924cd8e8095624252c7d4fdf153042431423dd", kill_on_drop: false }`
[INFO] [stdout] 99f7e094089ba997afd5fea193924cd8e8095624252c7d4fdf153042431423dd
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] f0798b6d7b37b199f5fc1270798f7c538c6a4da5f8304ecb75e1cfa79ed4c4ad
[INFO] running `Command { std: "docker" "start" "-a" "f0798b6d7b37b199f5fc1270798f7c538c6a4da5f8304ecb75e1cfa79ed4c4ad", kill_on_drop: false }`
[INFO] [stderr]    Compiling serde v1.0.130
[INFO] [stderr]    Compiling rustversion v1.0.5
[INFO] [stderr]    Compiling half v1.7.1
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/boolobject.rs:10:1
[INFO] [stdout]     |
[INFO] [stdout] 10  | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: `#[warn(static_mut_refs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBool_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/capsule.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type);
[INFO] [stdout]     | ------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyCapsule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/dict.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyDict_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/list.rs:28:1
[INFO] [stdout]     |
[INFO] [stdout] 28  | pyobject_newtype!(PyList, PyList_Check, PyList_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyList_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/module.rs:33:1
[INFO] [stdout]     |
[INFO] [stdout] 33  | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type);
[INFO] [stdout]     | ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyModule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:56:1
[INFO] [stdout]     |
[INFO] [stdout] 56  | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyLong_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:65:1
[INFO] [stdout]     |
[INFO] [stdout] 65  | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyFloat_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/object.rs:113:44
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) }
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, addr_of_mut!(ffi::PyBaseObject_Type)) }
[INFO] [stdout]     |                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/set.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PySet, PySet_Check, PySet_Type);
[INFO] [stdout]     | ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PySet_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:36:1
[INFO] [stdout]     |
[INFO] [stdout] 36  | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type);
[INFO] [stdout]     | ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyUnicode_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:42:1
[INFO] [stdout]     |
[INFO] [stdout] 42  | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBytes_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/tuple.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyTuple_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/typeobject.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyType, PyType_Check, PyType_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyType_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 13 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling serde_cbor v0.11.2
[INFO] [stderr]    Compiling serde_bytes v0.11.5
[INFO] [stderr]    Compiling cpython v0.7.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]  --> tests/test_sharedref.rs:3:1
[INFO] [stdout]   |
[INFO] [stdout] 3 | / py_class!(class Owner |py| {
[INFO] [stdout] 4 | |     @shared data string: String;
[INFO] [stdout] 5 | | });
[INFO] [stdout]   | |__^
[INFO] [stdout]   |
[INFO] [stdout]   = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]   = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]   = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]   = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]   = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]  --> tests/test_sharedref.rs:3:1
[INFO] [stdout]   |
[INFO] [stdout] 3 | / py_class!(class Owner |py| {
[INFO] [stdout] 4 | |     @shared data string: String;
[INFO] [stdout] 5 | | });
[INFO] [stdout]   | |__^
[INFO] [stdout]   |
[INFO] [stdout]   = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]   = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]   = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]   = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]   = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: calls to `std::mem::drop` with a value that implements `Copy` does nothing
[INFO] [stdout]    --> tests/test_function.rs:114:9
[INFO] [stdout]     |
[INFO] [stdout] 114 |         drop(py); // avoid unused variable warning
[INFO] [stdout]     |         ^^^^^--^
[INFO] [stdout]     |              |
[INFO] [stdout]     |              argument has type `Python<'_>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: use `let _ = ...` to ignore the expression or result
[INFO] [stdout]     = note: `#[warn(dropping_copy_types)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: calls to `std::mem::drop` with a value that implements `Copy` does nothing
[INFO] [stdout]    --> tests/test_function.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         drop(py);
[INFO] [stdout]     |         ^^^^^--^
[INFO] [stdout]     |              |
[INFO] [stdout]     |              argument has type `Python<'_>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: use `let _ = ...` to ignore the expression or result
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 2 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/boolobject.rs:10:1
[INFO] [stdout]     |
[INFO] [stdout] 10  | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: `#[warn(static_mut_refs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBool_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/capsule.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type);
[INFO] [stdout]     | ------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyCapsule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/dict.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyDict_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/list.rs:28:1
[INFO] [stdout]     |
[INFO] [stdout] 28  | pyobject_newtype!(PyList, PyList_Check, PyList_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyList_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/module.rs:33:1
[INFO] [stdout]     |
[INFO] [stdout] 33  | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type);
[INFO] [stdout]     | ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyModule_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 2 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:56:1
[INFO] [stdout]     |
[INFO] [stdout] 56  | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyLong_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/num.rs:65:1
[INFO] [stdout]     |
[INFO] [stdout] 65  | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyFloat_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/object.rs:113:44
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) }
[INFO] [stdout]     |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 113 |         unsafe { PyType::from_type_ptr(py, addr_of_mut!(ffi::PyBaseObject_Type)) }
[INFO] [stdout]     |                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/set.rs:30:1
[INFO] [stdout]     |
[INFO] [stdout] 30  | pyobject_newtype!(PySet, PySet_Check, PySet_Type);
[INFO] [stdout]     | ------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PySet_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:36:1
[INFO] [stdout]     |
[INFO] [stdout] 36  | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type);
[INFO] [stdout]     | ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyUnicode_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/string.rs:42:1
[INFO] [stdout]     |
[INFO] [stdout] 42  | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBytes_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/tuple.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type);
[INFO] [stdout]     | ------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyTuple_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stdout]    --> src/objects/mod.rs:119:80
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stdout]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/objects/typeobject.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | pyobject_newtype!(PyType, PyType_Check, PyType_Type);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: this will be a hard error in the 2024 edition
[INFO] [stdout]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stdout]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stdout]     |
[INFO] [stdout] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyType_Type)) }
[INFO] [stdout]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | py_class!(class EmptyClass |py| { });
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | py_class!(class EmptyClass |py| { });
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:49:1
[INFO] [stdout]    |
[INFO] [stdout] 49 | py_class!(class EmptyClassInModule |py| { });
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:49:1
[INFO] [stdout]    |
[INFO] [stdout] 49 | py_class!(class EmptyClassInModule |py| { });
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:75:1
[INFO] [stdout]    |
[INFO] [stdout] 75 | / py_class!(class EmptyClassWithNew |py| {
[INFO] [stdout] 76 | |     def __new__(_cls) -> PyResult<EmptyClassWithNew> {
[INFO] [stdout] 77 | |         EmptyClassWithNew::create_instance(py)
[INFO] [stdout] 78 | |     }
[INFO] [stdout] 79 | | });
[INFO] [stdout]    | |__^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:75:1
[INFO] [stdout]    |
[INFO] [stdout] 75 | / py_class!(class EmptyClassWithNew |py| {
[INFO] [stdout] 76 | |     def __new__(_cls) -> PyResult<EmptyClassWithNew> {
[INFO] [stdout] 77 | |         EmptyClassWithNew::create_instance(py)
[INFO] [stdout] 78 | |     }
[INFO] [stdout] 79 | | });
[INFO] [stdout]    | |__^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:93:1
[INFO] [stdout]    |
[INFO] [stdout] 93 | / py_class!(class NewWithOneArg |py| {
[INFO] [stdout] 94 | |     data _data: i32;
[INFO] [stdout] 95 | |     def __new__(_cls, arg: i32) -> PyResult<NewWithOneArg> {
[INFO] [stdout] 96 | |         NewWithOneArg::create_instance(py, arg)
[INFO] [stdout] 97 | |     }
[INFO] [stdout] 98 | | });
[INFO] [stdout]    | |__^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]   --> tests/test_class.rs:93:1
[INFO] [stdout]    |
[INFO] [stdout] 93 | / py_class!(class NewWithOneArg |py| {
[INFO] [stdout] 94 | |     data _data: i32;
[INFO] [stdout] 95 | |     def __new__(_cls, arg: i32) -> PyResult<NewWithOneArg> {
[INFO] [stdout] 96 | |         NewWithOneArg::create_instance(py, arg)
[INFO] [stdout] 97 | |     }
[INFO] [stdout] 98 | | });
[INFO] [stdout]    | |__^
[INFO] [stdout]    |
[INFO] [stdout]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:113:1
[INFO] [stdout]     |
[INFO] [stdout] 113 | / py_class!(class NewWithTwoArgs |py| {
[INFO] [stdout] 114 | |     data _data1: i32;
[INFO] [stdout] 115 | |     data _data2: i32;
[INFO] [stdout] 116 | |     def __new__(_cls, arg1: i32, arg2: i32) -> PyResult<NewWithTwoArgs> {
[INFO] [stdout] 117 | |         NewWithTwoArgs::create_instance(py, arg1, arg2)
[INFO] [stdout] 118 | |     }
[INFO] [stdout] 119 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:113:1
[INFO] [stdout]     |
[INFO] [stdout] 113 | / py_class!(class NewWithTwoArgs |py| {
[INFO] [stdout] 114 | |     data _data1: i32;
[INFO] [stdout] 115 | |     data _data2: i32;
[INFO] [stdout] 116 | |     def __new__(_cls, arg1: i32, arg2: i32) -> PyResult<NewWithTwoArgs> {
[INFO] [stdout] 117 | |         NewWithTwoArgs::create_instance(py, arg1, arg2)
[INFO] [stdout] 118 | |     }
[INFO] [stdout] 119 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:144:1
[INFO] [stdout]     |
[INFO] [stdout] 144 | / py_class!(class DataIsDropped |py| {
[INFO] [stdout] 145 | |     data member1: TestDropCall;
[INFO] [stdout] 146 | |     data member2: TestDropCall;
[INFO] [stdout] 147 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:144:1
[INFO] [stdout]     |
[INFO] [stdout] 144 | / py_class!(class DataIsDropped |py| {
[INFO] [stdout] 145 | |     data member1: TestDropCall;
[INFO] [stdout] 146 | |     data member2: TestDropCall;
[INFO] [stdout] 147 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:172:1
[INFO] [stdout]     |
[INFO] [stdout] 172 | / py_class!(class InstanceMethod |py| {
[INFO] [stdout] 173 | |     data member: i32;
[INFO] [stdout] 174 | |
[INFO] [stdout] 175 | |     def method(&self) -> PyResult<i32> {
[INFO] [stdout] 176 | |         Ok(*self.member(py))
[INFO] [stdout] 177 | |     }
[INFO] [stdout] 178 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:172:1
[INFO] [stdout]     |
[INFO] [stdout] 172 | / py_class!(class InstanceMethod |py| {
[INFO] [stdout] 173 | |     data member: i32;
[INFO] [stdout] 174 | |
[INFO] [stdout] 175 | |     def method(&self) -> PyResult<i32> {
[INFO] [stdout] 176 | |         Ok(*self.member(py))
[INFO] [stdout] 177 | |     }
[INFO] [stdout] 178 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:192:1
[INFO] [stdout]     |
[INFO] [stdout] 192 | / py_class!(class InstanceMethodReturnsNone |py| {
[INFO] [stdout] 193 | |     data member: AtomicUsize;
[INFO] [stdout] 194 | |
[INFO] [stdout] 195 | |     def value(&self) -> PyResult<usize> {
[INFO] [stdout] ...   |
[INFO] [stdout] 202 | |     }
[INFO] [stdout] 203 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:192:1
[INFO] [stdout]     |
[INFO] [stdout] 192 | / py_class!(class InstanceMethodReturnsNone |py| {
[INFO] [stdout] 193 | |     data member: AtomicUsize;
[INFO] [stdout] 194 | |
[INFO] [stdout] 195 | |     def value(&self) -> PyResult<usize> {
[INFO] [stdout] ...   |
[INFO] [stdout] 202 | |     }
[INFO] [stdout] 203 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:220:1
[INFO] [stdout]     |
[INFO] [stdout] 220 | / py_class!(class InstanceMethodWithArgs |py| {
[INFO] [stdout] 221 | |     data member: i32;
[INFO] [stdout] 222 | |
[INFO] [stdout] 223 | |     def method(&self, multiplier: i32) -> PyResult<i32> {
[INFO] [stdout] ...   |
[INFO] [stdout] 229 | |     }
[INFO] [stdout] 230 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:220:1
[INFO] [stdout]     |
[INFO] [stdout] 220 | / py_class!(class InstanceMethodWithArgs |py| {
[INFO] [stdout] 221 | |     data member: i32;
[INFO] [stdout] 222 | |
[INFO] [stdout] 223 | |     def method(&self, multiplier: i32) -> PyResult<i32> {
[INFO] [stdout] ...   |
[INFO] [stdout] 229 | |     }
[INFO] [stdout] 230 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:249:1
[INFO] [stdout]     |
[INFO] [stdout] 249 | / py_class!(class ClassMethod |py| {
[INFO] [stdout] 250 | |     def __new__(cls) -> PyResult<ClassMethod> {
[INFO] [stdout] 251 | |         ClassMethod::create_instance(py)
[INFO] [stdout] 252 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 257 | |     }
[INFO] [stdout] 258 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:249:1
[INFO] [stdout]     |
[INFO] [stdout] 249 | / py_class!(class ClassMethod |py| {
[INFO] [stdout] 250 | |     def __new__(cls) -> PyResult<ClassMethod> {
[INFO] [stdout] 251 | |         ClassMethod::create_instance(py)
[INFO] [stdout] 252 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 257 | |     }
[INFO] [stdout] 258 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:281:1
[INFO] [stdout]     |
[INFO] [stdout] 281 | / py_class!(class ClassMethodWithArgs |py| {
[INFO] [stdout] 282 | |     @classmethod
[INFO] [stdout] 283 | |     def method(cls, input: &str) -> PyResult<String> {
[INFO] [stdout] 284 | |         Ok(format!("{}.method({})", cls.name(py), input))
[INFO] [stdout] 285 | |     }
[INFO] [stdout] 286 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:281:1
[INFO] [stdout]     |
[INFO] [stdout] 281 | / py_class!(class ClassMethodWithArgs |py| {
[INFO] [stdout] 282 | |     @classmethod
[INFO] [stdout] 283 | |     def method(cls, input: &str) -> PyResult<String> {
[INFO] [stdout] 284 | |         Ok(format!("{}.method({})", cls.name(py), input))
[INFO] [stdout] 285 | |     }
[INFO] [stdout] 286 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:304:1
[INFO] [stdout]     |
[INFO] [stdout] 304 | / py_class!(class StaticMethod |py| {
[INFO] [stdout] 305 | |     def __new__(cls) -> PyResult<StaticMethod> {
[INFO] [stdout] 306 | |         StaticMethod::create_instance(py)
[INFO] [stdout] 307 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 312 | |     }
[INFO] [stdout] 313 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:304:1
[INFO] [stdout]     |
[INFO] [stdout] 304 | / py_class!(class StaticMethod |py| {
[INFO] [stdout] 305 | |     def __new__(cls) -> PyResult<StaticMethod> {
[INFO] [stdout] 306 | |         StaticMethod::create_instance(py)
[INFO] [stdout] 307 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 312 | |     }
[INFO] [stdout] 313 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:337:1
[INFO] [stdout]     |
[INFO] [stdout] 337 | / py_class!(class StaticMethodWithArgs |py| {
[INFO] [stdout] 338 | |     @staticmethod
[INFO] [stdout] 339 | |     def method(input: i32) -> PyResult<String> {
[INFO] [stdout] 340 | |         Ok(format!("0x{:x}", input))
[INFO] [stdout] 341 | |     }
[INFO] [stdout] 342 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:337:1
[INFO] [stdout]     |
[INFO] [stdout] 337 | / py_class!(class StaticMethodWithArgs |py| {
[INFO] [stdout] 338 | |     @staticmethod
[INFO] [stdout] 339 | |     def method(input: i32) -> PyResult<String> {
[INFO] [stdout] 340 | |         Ok(format!("0x{:x}", input))
[INFO] [stdout] 341 | |     }
[INFO] [stdout] 342 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:357:1
[INFO] [stdout]     |
[INFO] [stdout] 357 | / py_class!(class StaticData |py| {
[INFO] [stdout] 358 | |     static VAL1 = 123;
[INFO] [stdout] 359 | |     static VAL2 = py.None();
[INFO] [stdout] 360 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:357:1
[INFO] [stdout]     |
[INFO] [stdout] 357 | / py_class!(class StaticData |py| {
[INFO] [stdout] 358 | |     static VAL1 = 123;
[INFO] [stdout] 359 | |     static VAL2 = py.None();
[INFO] [stdout] 360 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:374:1
[INFO] [stdout]     |
[INFO] [stdout] 374 | / py_class!(class GCIntegration |py| {
[INFO] [stdout] 375 | |     data self_ref: RefCell<PyObject>;
[INFO] [stdout] 376 | |     data dropped: TestDropCall;
[INFO] [stdout] ...   |
[INFO] [stdout] 386 | |     }
[INFO] [stdout] 387 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:374:1
[INFO] [stdout]     |
[INFO] [stdout] 374 | / py_class!(class GCIntegration |py| {
[INFO] [stdout] 375 | |     data self_ref: RefCell<PyObject>;
[INFO] [stdout] 376 | |     data dropped: TestDropCall;
[INFO] [stdout] ...   |
[INFO] [stdout] 386 | |     }
[INFO] [stdout] 387 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:410:1
[INFO] [stdout]     |
[INFO] [stdout] 410 | / py_class!(class Len |py| {
[INFO] [stdout] 411 | |     data l: usize;
[INFO] [stdout] 412 | |
[INFO] [stdout] 413 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stdout] 414 | |         Ok(*self.l(py))
[INFO] [stdout] 415 | |     }
[INFO] [stdout] 416 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:410:1
[INFO] [stdout]     |
[INFO] [stdout] 410 | / py_class!(class Len |py| {
[INFO] [stdout] 411 | |     data l: usize;
[INFO] [stdout] 412 | |
[INFO] [stdout] 413 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stdout] 414 | |         Ok(*self.l(py))
[INFO] [stdout] 415 | |     }
[INFO] [stdout] 416 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:434:1
[INFO] [stdout]     |
[INFO] [stdout] 434 | / py_class!(class Iterator |py| {
[INFO] [stdout] 435 | |     data iter: RefCell<Box<dyn iter::Iterator<Item=i32> + Send>>;
[INFO] [stdout] 436 | |
[INFO] [stdout] 437 | |     def __iter__(&self) -> PyResult<Iterator> {
[INFO] [stdout] ...   |
[INFO] [stdout] 443 | |     }
[INFO] [stdout] 444 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:434:1
[INFO] [stdout]     |
[INFO] [stdout] 434 | / py_class!(class Iterator |py| {
[INFO] [stdout] 435 | |     data iter: RefCell<Box<dyn iter::Iterator<Item=i32> + Send>>;
[INFO] [stdout] 436 | |
[INFO] [stdout] 437 | |     def __iter__(&self) -> PyResult<Iterator> {
[INFO] [stdout] ...   |
[INFO] [stdout] 443 | |     }
[INFO] [stdout] 444 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:456:1
[INFO] [stdout]     |
[INFO] [stdout] 456 | / py_class!(class StringMethods |py| {
[INFO] [stdout] 457 | |     def __str__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 458 | |         Ok("str")
[INFO] [stdout] 459 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 475 | |     }
[INFO] [stdout] 476 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:456:1
[INFO] [stdout]     |
[INFO] [stdout] 456 | / py_class!(class StringMethods |py| {
[INFO] [stdout] 457 | |     def __str__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 458 | |         Ok("str")
[INFO] [stdout] 459 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 475 | |     }
[INFO] [stdout] 476 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:509:1
[INFO] [stdout]     |
[INFO] [stdout] 509 | / py_class!(class Comparisons |py| {
[INFO] [stdout] 510 | |     data val: i32;
[INFO] [stdout] 511 | |
[INFO] [stdout] 512 | |     def __hash__(&self) -> PyResult<i32> {
[INFO] [stdout] ...   |
[INFO] [stdout] 518 | |     }
[INFO] [stdout] 519 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:509:1
[INFO] [stdout]     |
[INFO] [stdout] 509 | / py_class!(class Comparisons |py| {
[INFO] [stdout] 510 | |     data val: i32;
[INFO] [stdout] 511 | |
[INFO] [stdout] 512 | |     def __hash__(&self) -> PyResult<i32> {
[INFO] [stdout] ...   |
[INFO] [stdout] 518 | |     }
[INFO] [stdout] 519 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:538:1
[INFO] [stdout]     |
[INFO] [stdout] 538 | / py_class!(class Sequence |py| {
[INFO] [stdout] 539 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stdout] 540 | |         Ok(5)
[INFO] [stdout] 541 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 550 | |     }
[INFO] [stdout] 551 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:538:1
[INFO] [stdout]     |
[INFO] [stdout] 538 | / py_class!(class Sequence |py| {
[INFO] [stdout] 539 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stdout] 540 | |         Ok(5)
[INFO] [stdout] 541 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 550 | |     }
[INFO] [stdout] 551 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:563:1
[INFO] [stdout]     |
[INFO] [stdout] 563 | / py_class!(class SequenceRef |py| {
[INFO] [stdout] 564 | |     def __getitem__(&self, key: &str) -> PyResult<String> {
[INFO] [stdout] 565 | |         if key.is_empty() {
[INFO] [stdout] 566 | |             return Err(PyErr::new::<exc::IndexError, NoArgs>(py, NoArgs));
[INFO] [stdout] ...   |
[INFO] [stdout] 576 | |     }
[INFO] [stdout] 577 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:563:1
[INFO] [stdout]     |
[INFO] [stdout] 563 | / py_class!(class SequenceRef |py| {
[INFO] [stdout] 564 | |     def __getitem__(&self, key: &str) -> PyResult<String> {
[INFO] [stdout] 565 | |         if key.is_empty() {
[INFO] [stdout] 566 | |             return Err(PyErr::new::<exc::IndexError, NoArgs>(py, NoArgs));
[INFO] [stdout] ...   |
[INFO] [stdout] 576 | |     }
[INFO] [stdout] 577 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:592:1
[INFO] [stdout]     |
[INFO] [stdout] 592 | / py_class!(class Callable |py| {
[INFO] [stdout] 593 | |     def __call__(&self, arg: i32) -> PyResult<i32> {
[INFO] [stdout] 594 | |         Ok(arg * 6)
[INFO] [stdout] 595 | |     }
[INFO] [stdout] 596 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:592:1
[INFO] [stdout]     |
[INFO] [stdout] 592 | / py_class!(class Callable |py| {
[INFO] [stdout] 593 | |     def __call__(&self, arg: i32) -> PyResult<i32> {
[INFO] [stdout] 594 | |         Ok(arg * 6)
[INFO] [stdout] 595 | |     }
[INFO] [stdout] 596 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:611:1
[INFO] [stdout]     |
[INFO] [stdout] 611 | / py_class!(class SetItem |py| {
[INFO] [stdout] 612 | |     data key: Cell<i32>;
[INFO] [stdout] 613 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 619 | |     }
[INFO] [stdout] 620 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:611:1
[INFO] [stdout]     |
[INFO] [stdout] 611 | / py_class!(class SetItem |py| {
[INFO] [stdout] 612 | |     data key: Cell<i32>;
[INFO] [stdout] 613 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 619 | |     }
[INFO] [stdout] 620 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:634:1
[INFO] [stdout]     |
[INFO] [stdout] 634 | / py_class!(class SetItemRef |py| {
[INFO] [stdout] 635 | |     data key: RefCell<String>;
[INFO] [stdout] 636 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 642 | |     }
[INFO] [stdout] 643 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:634:1
[INFO] [stdout]     |
[INFO] [stdout] 634 | / py_class!(class SetItemRef |py| {
[INFO] [stdout] 635 | |     data key: RefCell<String>;
[INFO] [stdout] 636 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 642 | |     }
[INFO] [stdout] 643 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:657:1
[INFO] [stdout]     |
[INFO] [stdout] 657 | / py_class!(class SetItemOptRef |py| {
[INFO] [stdout] 658 | |     data key: RefCell<String>;
[INFO] [stdout] 659 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 669 | |     }
[INFO] [stdout] 670 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:657:1
[INFO] [stdout]     |
[INFO] [stdout] 657 | / py_class!(class SetItemOptRef |py| {
[INFO] [stdout] 658 | |     data key: RefCell<String>;
[INFO] [stdout] 659 | |     data val: Cell<i32>;
[INFO] [stdout] ...   |
[INFO] [stdout] 669 | |     }
[INFO] [stdout] 670 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:684:1
[INFO] [stdout]     |
[INFO] [stdout] 684 | / py_class!(class DelItem |py| {
[INFO] [stdout] 685 | |     data key: Cell<i32>;
[INFO] [stdout] 686 | |
[INFO] [stdout] 687 | |     def __delitem__(&self, key: i32) -> PyResult<()> {
[INFO] [stdout] ...   |
[INFO] [stdout] 690 | |     }
[INFO] [stdout] 691 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:684:1
[INFO] [stdout]     |
[INFO] [stdout] 684 | / py_class!(class DelItem |py| {
[INFO] [stdout] 685 | |     data key: Cell<i32>;
[INFO] [stdout] 686 | |
[INFO] [stdout] 687 | |     def __delitem__(&self, key: i32) -> PyResult<()> {
[INFO] [stdout] ...   |
[INFO] [stdout] 690 | |     }
[INFO] [stdout] 691 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:704:1
[INFO] [stdout]     |
[INFO] [stdout] 704 | / py_class!(class SetDelItem |py| {
[INFO] [stdout] 705 | |     data val: Cell<Option<i32>>;
[INFO] [stdout] 706 | |
[INFO] [stdout] 707 | |     def __setitem__(&self, key: i32, val: i32) -> PyResult<()> {
[INFO] [stdout] ...   |
[INFO] [stdout] 715 | |     }
[INFO] [stdout] 716 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:704:1
[INFO] [stdout]     |
[INFO] [stdout] 704 | / py_class!(class SetDelItem |py| {
[INFO] [stdout] 705 | |     data val: Cell<Option<i32>>;
[INFO] [stdout] 706 | |
[INFO] [stdout] 707 | |     def __setitem__(&self, key: i32, val: i32) -> PyResult<()> {
[INFO] [stdout] ...   |
[INFO] [stdout] 715 | |     }
[INFO] [stdout] 716 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:730:1
[INFO] [stdout]     |
[INFO] [stdout] 730 | / py_class!(class Reversed |py| {
[INFO] [stdout] 731 | |     def __reversed__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 732 | |         Ok("I am reversed")
[INFO] [stdout] 733 | |     }
[INFO] [stdout] 734 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:730:1
[INFO] [stdout]     |
[INFO] [stdout] 730 | / py_class!(class Reversed |py| {
[INFO] [stdout] 731 | |     def __reversed__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 732 | |         Ok("I am reversed")
[INFO] [stdout] 733 | |     }
[INFO] [stdout] 734 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:745:1
[INFO] [stdout]     |
[INFO] [stdout] 745 | / py_class!(class Contains |py| {
[INFO] [stdout] 746 | |     def __contains__(&self, item: i32) -> PyResult<bool> {
[INFO] [stdout] 747 | |         Ok(item >= 0)
[INFO] [stdout] 748 | |     }
[INFO] [stdout] 749 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:745:1
[INFO] [stdout]     |
[INFO] [stdout] 745 | / py_class!(class Contains |py| {
[INFO] [stdout] 746 | |     def __contains__(&self, item: i32) -> PyResult<bool> {
[INFO] [stdout] 747 | |         Ok(item >= 0)
[INFO] [stdout] 748 | |     }
[INFO] [stdout] 749 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:762:1
[INFO] [stdout]     |
[INFO] [stdout] 762 | / py_class!(class ContainsRef |py| {
[INFO] [stdout] 763 | |     def __contains__(&self, item: &str) -> PyResult<bool> {
[INFO] [stdout] 764 | |         Ok(item.is_empty())
[INFO] [stdout] 765 | |     }
[INFO] [stdout] 766 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:762:1
[INFO] [stdout]     |
[INFO] [stdout] 762 | / py_class!(class ContainsRef |py| {
[INFO] [stdout] 763 | |     def __contains__(&self, item: &str) -> PyResult<bool> {
[INFO] [stdout] 764 | |         Ok(item.is_empty())
[INFO] [stdout] 765 | |     }
[INFO] [stdout] 766 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:779:1
[INFO] [stdout]     |
[INFO] [stdout] 779 | / py_class!(class ContainsOptRef |py| {
[INFO] [stdout] 780 | |     def __contains__(&self, item: Option<&str>) -> PyResult<bool> {
[INFO] [stdout] 781 | |         Ok(item.map_or(false, str::is_empty))
[INFO] [stdout] 782 | |     }
[INFO] [stdout] 783 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:779:1
[INFO] [stdout]     |
[INFO] [stdout] 779 | / py_class!(class ContainsOptRef |py| {
[INFO] [stdout] 780 | |     def __contains__(&self, item: Option<&str>) -> PyResult<bool> {
[INFO] [stdout] 781 | |         Ok(item.map_or(false, str::is_empty))
[INFO] [stdout] 782 | |     }
[INFO] [stdout] 783 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:797:1
[INFO] [stdout]     |
[INFO] [stdout] 797 | / py_class!(class UnaryArithmetic |py| {
[INFO] [stdout] 798 | |     def __neg__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 799 | |         Ok("neg")
[INFO] [stdout] 800 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 812 | |     }
[INFO] [stdout] 813 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:797:1
[INFO] [stdout]     |
[INFO] [stdout] 797 | / py_class!(class UnaryArithmetic |py| {
[INFO] [stdout] 798 | |     def __neg__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 799 | |         Ok("neg")
[INFO] [stdout] 800 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 812 | |     }
[INFO] [stdout] 813 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:827:1
[INFO] [stdout]     |
[INFO] [stdout] 827 | / py_class!(class BinaryArithmetic |py| {
[INFO] [stdout] 828 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 829 | |         Ok("BA")
[INFO] [stdout] 830 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 862 | |     }
[INFO] [stdout] 863 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:827:1
[INFO] [stdout]     |
[INFO] [stdout] 827 | / py_class!(class BinaryArithmetic |py| {
[INFO] [stdout] 828 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 829 | |         Ok("BA")
[INFO] [stdout] 830 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 862 | |     }
[INFO] [stdout] 863 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:891:1
[INFO] [stdout]     |
[INFO] [stdout] 891 | / py_class!(class RichComparisons |py| {
[INFO] [stdout] 892 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 893 | |         Ok("RC")
[INFO] [stdout] 894 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 905 | |     }
[INFO] [stdout] 906 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:891:1
[INFO] [stdout]     |
[INFO] [stdout] 891 | / py_class!(class RichComparisons |py| {
[INFO] [stdout] 892 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 893 | |         Ok("RC")
[INFO] [stdout] 894 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 905 | |     }
[INFO] [stdout] 906 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:908:1
[INFO] [stdout]     |
[INFO] [stdout] 908 | / py_class!(class RichComparisons2 |py| {
[INFO] [stdout] 909 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 910 | |         Ok("RC2")
[INFO] [stdout] 911 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 919 | |     }
[INFO] [stdout] 920 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:908:1
[INFO] [stdout]     |
[INFO] [stdout] 908 | / py_class!(class RichComparisons2 |py| {
[INFO] [stdout] 909 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 910 | |         Ok("RC2")
[INFO] [stdout] 911 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 919 | |     }
[INFO] [stdout] 920 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:975:1
[INFO] [stdout]     |
[INFO] [stdout] 975 | / py_class!(class RichComparisonsRef |py| {
[INFO] [stdout] 976 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 977 | |         Ok("RCR")
[INFO] [stdout] 978 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 989 | |     }
[INFO] [stdout] 990 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> tests/test_class.rs:975:1
[INFO] [stdout]     |
[INFO] [stdout] 975 | / py_class!(class RichComparisonsRef |py| {
[INFO] [stdout] 976 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 977 | |         Ok("RCR")
[INFO] [stdout] 978 | |     }
[INFO] [stdout] ...   |
[INFO] [stdout] 989 | |     }
[INFO] [stdout] 990 | | });
[INFO] [stdout]     | |__^
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1008:1
[INFO] [stdout]      |
[INFO] [stdout] 1008 | / py_class!(class RichComparisonsOptRef |py| {
[INFO] [stdout] 1009 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1010 | |         Ok("RCR")
[INFO] [stdout] 1011 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1028 | |     }
[INFO] [stdout] 1029 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1008:1
[INFO] [stdout]      |
[INFO] [stdout] 1008 | / py_class!(class RichComparisonsOptRef |py| {
[INFO] [stdout] 1009 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1010 | |         Ok("RCR")
[INFO] [stdout] 1011 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1028 | |     }
[INFO] [stdout] 1029 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1043:1
[INFO] [stdout]      |
[INFO] [stdout] 1043 | / py_class!(class InPlaceOperations |py| {
[INFO] [stdout] 1044 | |     data value: Cell<u32>;
[INFO] [stdout] 1045 | |
[INFO] [stdout] 1046 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1088 | |     }
[INFO] [stdout] 1089 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1043:1
[INFO] [stdout]      |
[INFO] [stdout] 1043 | / py_class!(class InPlaceOperations |py| {
[INFO] [stdout] 1044 | |     data value: Cell<u32>;
[INFO] [stdout] 1045 | |
[INFO] [stdout] 1046 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1088 | |     }
[INFO] [stdout] 1089 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1153:1
[INFO] [stdout]      |
[INFO] [stdout] 1153 | / py_class!(class InPlaceOperationsRef |py| {
[INFO] [stdout] 1154 | |     data value: RefCell<String>;
[INFO] [stdout] 1155 | |
[INFO] [stdout] 1156 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1164 | |     }
[INFO] [stdout] 1165 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1153:1
[INFO] [stdout]      |
[INFO] [stdout] 1153 | / py_class!(class InPlaceOperationsRef |py| {
[INFO] [stdout] 1154 | |     data value: RefCell<String>;
[INFO] [stdout] 1155 | |
[INFO] [stdout] 1156 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1164 | |     }
[INFO] [stdout] 1165 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1180:1
[INFO] [stdout]      |
[INFO] [stdout] 1180 | / py_class!(class ContextManager |py| {
[INFO] [stdout] 1181 | |     data exit_called : Cell<bool>;
[INFO] [stdout] 1182 | |
[INFO] [stdout] 1183 | |     def __enter__(&self) -> PyResult<i32> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1194 | |     }
[INFO] [stdout] 1195 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1180:1
[INFO] [stdout]      |
[INFO] [stdout] 1180 | / py_class!(class ContextManager |py| {
[INFO] [stdout] 1181 | |     data exit_called : Cell<bool>;
[INFO] [stdout] 1182 | |
[INFO] [stdout] 1183 | |     def __enter__(&self) -> PyResult<i32> {
[INFO] [stdout] ...    |
[INFO] [stdout] 1194 | |     }
[INFO] [stdout] 1195 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1220:1
[INFO] [stdout]      |
[INFO] [stdout] 1220 | / py_class!(class Properties |py| {
[INFO] [stdout] 1221 | |     data value: Cell<i32>;
[INFO] [stdout] 1222 | |     data value_by_ref: RefCell<String>;
[INFO] [stdout] 1223 | |     data value_by_opt_ref: RefCell<String>;
[INFO] [stdout] ...    |
[INFO] [stdout] 1263 | |     }
[INFO] [stdout] 1264 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1220:1
[INFO] [stdout]      |
[INFO] [stdout] 1220 | / py_class!(class Properties |py| {
[INFO] [stdout] 1221 | |     data value: Cell<i32>;
[INFO] [stdout] 1222 | |     data value_by_ref: RefCell<String>;
[INFO] [stdout] 1223 | |     data value_by_opt_ref: RefCell<String>;
[INFO] [stdout] ...    |
[INFO] [stdout] 1263 | |     }
[INFO] [stdout] 1264 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1308:1
[INFO] [stdout]      |
[INFO] [stdout] 1308 | / py_class!(pub(crate) class ClassWithVisibility |py| {
[INFO] [stdout] 1309 | |   pub(crate) def __new__(_cls) -> PyResult<Self> {
[INFO] [stdout] 1310 | |     Self::create_instance(py)
[INFO] [stdout] 1311 | |   }
[INFO] [stdout] ...    |
[INFO] [stdout] 1325 | |   }
[INFO] [stdout] 1326 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1308:1
[INFO] [stdout]      |
[INFO] [stdout] 1308 | / py_class!(pub(crate) class ClassWithVisibility |py| {
[INFO] [stdout] 1309 | |   pub(crate) def __new__(_cls) -> PyResult<Self> {
[INFO] [stdout] 1310 | |     Self::create_instance(py)
[INFO] [stdout] 1311 | |   }
[INFO] [stdout] ...    |
[INFO] [stdout] 1325 | |   }
[INFO] [stdout] 1326 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1383:1
[INFO] [stdout]      |
[INFO] [stdout] 1383 | / py_class!(class NumberExt |py| {
[INFO] [stdout] 1384 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1385 | |         Ok("BA")
[INFO] [stdout] 1386 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1402 | |     }
[INFO] [stdout] 1403 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1383:1
[INFO] [stdout]      |
[INFO] [stdout] 1383 | / py_class!(class NumberExt |py| {
[INFO] [stdout] 1384 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1385 | |         Ok("BA")
[INFO] [stdout] 1386 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1402 | |     }
[INFO] [stdout] 1403 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1427:1
[INFO] [stdout]      |
[INFO] [stdout] 1427 | / py_class!(class Py3Number |py| {
[INFO] [stdout] 1428 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1429 | |         Ok("BA")
[INFO] [stdout] 1430 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1442 | |     }
[INFO] [stdout] 1443 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1427:1
[INFO] [stdout]      |
[INFO] [stdout] 1427 | / py_class!(class Py3Number |py| {
[INFO] [stdout] 1428 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stdout] 1429 | |         Ok("BA")
[INFO] [stdout] 1430 | |     }
[INFO] [stdout] ...    |
[INFO] [stdout] 1442 | |     }
[INFO] [stdout] 1443 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1464:1
[INFO] [stdout]      |
[INFO] [stdout] 1464 | / py_class!(class DummyMatMul |py| {
[INFO] [stdout] 1465 | |     data number: i32;
[INFO] [stdout] 1466 | |     def __new__(_cls, arg: i32) -> PyResult<DummyMatMul> {
[INFO] [stdout] 1467 | |         DummyMatMul::create_instance(py, arg)
[INFO] [stdout] ...    |
[INFO] [stdout] 1476 | |     }
[INFO] [stdout] 1477 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]     --> tests/test_class.rs:1464:1
[INFO] [stdout]      |
[INFO] [stdout] 1464 | / py_class!(class DummyMatMul |py| {
[INFO] [stdout] 1465 | |     data number: i32;
[INFO] [stdout] 1466 | |     def __new__(_cls, arg: i32) -> PyResult<DummyMatMul> {
[INFO] [stdout] 1467 | |         DummyMatMul::create_instance(py, arg)
[INFO] [stdout] ...    |
[INFO] [stdout] 1476 | |     }
[INFO] [stdout] 1477 | | });
[INFO] [stdout]      | |__^
[INFO] [stdout]      |
[INFO] [stdout]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stdout]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stdout]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stdout]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 13 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 90 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 5.33s
[INFO] running `Command { std: "docker" "inspect" "f0798b6d7b37b199f5fc1270798f7c538c6a4da5f8304ecb75e1cfa79ed4c4ad", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f0798b6d7b37b199f5fc1270798f7c538c6a4da5f8304ecb75e1cfa79ed4c4ad", kill_on_drop: false }`
[INFO] [stdout] f0798b6d7b37b199f5fc1270798f7c538c6a4da5f8304ecb75e1cfa79ed4c4ad
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] 15520d6f17816102796f03f95f2dfb45bc587c1368110929cfa0638c2765ffde
[INFO] running `Command { std: "docker" "start" "-a" "15520d6f17816102796f03f95f2dfb45bc587c1368110929cfa0638c2765ffde", kill_on_drop: false }`
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/boolobject.rs:10:1
[INFO] [stderr]     |
[INFO] [stderr] 10  | pyobject_newtype!(PyBool, PyBool_Check, PyBool_Type);
[INFO] [stderr]     | ---------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: `#[warn(static_mut_refs)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBool_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/capsule.rs:190:1
[INFO] [stderr]     |
[INFO] [stderr] 190 | pyobject_newtype!(PyCapsule, PyCapsule_CheckExact, PyCapsule_Type);
[INFO] [stderr]     | ------------------------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyCapsule_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/dict.rs:30:1
[INFO] [stderr]     |
[INFO] [stderr] 30  | pyobject_newtype!(PyDict, PyDict_Check, PyDict_Type);
[INFO] [stderr]     | ---------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyDict_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/list.rs:28:1
[INFO] [stderr]     |
[INFO] [stderr] 28  | pyobject_newtype!(PyList, PyList_Check, PyList_Type);
[INFO] [stderr]     | ---------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyList_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/module.rs:33:1
[INFO] [stderr]     |
[INFO] [stderr] 33  | pyobject_newtype!(PyModule, PyModule_Check, PyModule_Type);
[INFO] [stderr]     | ---------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyModule_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/num.rs:56:1
[INFO] [stderr]     |
[INFO] [stderr] 56  | pyobject_newtype!(PyLong, PyLong_Check, PyLong_Type);
[INFO] [stderr]     | ---------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyLong_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/num.rs:65:1
[INFO] [stderr]     |
[INFO] [stderr] 65  | pyobject_newtype!(PyFloat, PyFloat_Check, PyFloat_Type);
[INFO] [stderr]     | ------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyFloat_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/object.rs:113:44
[INFO] [stderr]     |
[INFO] [stderr] 113 |         unsafe { PyType::from_type_ptr(py, &mut ffi::PyBaseObject_Type) }
[INFO] [stderr]     |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 113 |         unsafe { PyType::from_type_ptr(py, addr_of_mut!(ffi::PyBaseObject_Type)) }
[INFO] [stderr]     |                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/set.rs:30:1
[INFO] [stderr]     |
[INFO] [stderr] 30  | pyobject_newtype!(PySet, PySet_Check, PySet_Type);
[INFO] [stderr]     | ------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PySet_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/string.rs:36:1
[INFO] [stderr]     |
[INFO] [stderr] 36  | pyobject_newtype!(PyString, PyUnicode_Check, PyUnicode_Type);
[INFO] [stderr]     | ------------------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyUnicode_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/string.rs:42:1
[INFO] [stderr]     |
[INFO] [stderr] 42  | pyobject_newtype!(PyBytes, PyBytes_Check, PyBytes_Type);
[INFO] [stderr]     | ------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyBytes_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/tuple.rs:31:1
[INFO] [stderr]     |
[INFO] [stderr] 31  | pyobject_newtype!(PyTuple, PyTuple_Check, PyTuple_Type);
[INFO] [stderr]     | ------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyTuple_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: creating a mutable reference to mutable static is discouraged
[INFO] [stderr]    --> src/objects/mod.rs:119:80
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, &mut crate::ffi::$typeobject) }
[INFO] [stderr]     |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/objects/typeobject.rs:31:1
[INFO] [stderr]     |
[INFO] [stderr] 31  | pyobject_newtype!(PyType, PyType_Check, PyType_Type);
[INFO] [stderr]     | ---------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stderr]     = note: this will be a hard error in the 2024 edition
[INFO] [stderr]     = note: this mutable reference has lifetime `'static`, but if the static gets accessed (read or written) by any other means, or any other reference is created, then any further use of this mutable reference is Undefined Behavior
[INFO] [stderr]     = note: this warning originates in the macro `pyobject_newtype` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: use `addr_of_mut!` instead to create a raw pointer
[INFO] [stderr]     |
[INFO] [stderr] 119 |                 unsafe { crate::objects::typeobject::PyType::from_type_ptr(py, addr_of_mut!(crate::ffi::PyType_Type)) }
[INFO] [stderr]     |                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO] [stderr] 
[INFO] [stderr] warning: `cpython` (lib) generated 13 warnings
[INFO] [stderr] warning: `cpython` (lib test) generated 13 warnings (13 duplicates)
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]   --> tests/test_class.rs:36:1
[INFO] [stderr]    |
[INFO] [stderr] 36 | py_class!(class EmptyClass |py| { });
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stderr]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]   --> tests/test_class.rs:36:1
[INFO] [stderr]    |
[INFO] [stderr] 36 | py_class!(class EmptyClass |py| { });
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]   --> tests/test_class.rs:49:1
[INFO] [stderr]    |
[INFO] [stderr] 49 | py_class!(class EmptyClassInModule |py| { });
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]   --> tests/test_class.rs:75:1
[INFO] [stderr]    |
[INFO] [stderr] 75 | / py_class!(class EmptyClassWithNew |py| {
[INFO] [stderr] 76 | |     def __new__(_cls) -> PyResult<EmptyClassWithNew> {
[INFO] [stderr] 77 | |         EmptyClassWithNew::create_instance(py)
[INFO] [stderr] 78 | |     }
[INFO] [stderr] 79 | | });
[INFO] [stderr]    | |__^
[INFO] [stderr]    |
[INFO] [stderr]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]   --> tests/test_class.rs:93:1
[INFO] [stderr]    |
[INFO] [stderr] 93 | / py_class!(class NewWithOneArg |py| {
[INFO] [stderr] 94 | |     data _data: i32;
[INFO] [stderr] 95 | |     def __new__(_cls, arg: i32) -> PyResult<NewWithOneArg> {
[INFO] [stderr] 96 | |         NewWithOneArg::create_instance(py, arg)
[INFO] [stderr] 97 | |     }
[INFO] [stderr] 98 | | });
[INFO] [stderr]    | |__^
[INFO] [stderr]    |
[INFO] [stderr]    = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]    = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]    = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:113:1
[INFO] [stderr]     |
[INFO] [stderr] 113 | / py_class!(class NewWithTwoArgs |py| {
[INFO] [stderr] 114 | |     data _data1: i32;
[INFO] [stderr] 115 | |     data _data2: i32;
[INFO] [stderr] 116 | |     def __new__(_cls, arg1: i32, arg2: i32) -> PyResult<NewWithTwoArgs> {
[INFO] [stderr] 117 | |         NewWithTwoArgs::create_instance(py, arg1, arg2)
[INFO] [stderr] 118 | |     }
[INFO] [stderr] 119 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:144:1
[INFO] [stderr]     |
[INFO] [stderr] 144 | / py_class!(class DataIsDropped |py| {
[INFO] [stderr] 145 | |     data member1: TestDropCall;
[INFO] [stderr] 146 | |     data member2: TestDropCall;
[INFO] [stderr] 147 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:172:1
[INFO] [stderr]     |
[INFO] [stderr] 172 | / py_class!(class InstanceMethod |py| {
[INFO] [stderr] 173 | |     data member: i32;
[INFO] [stderr] 174 | |
[INFO] [stderr] 175 | |     def method(&self) -> PyResult<i32> {
[INFO] [stderr] 176 | |         Ok(*self.member(py))
[INFO] [stderr] 177 | |     }
[INFO] [stderr] 178 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:192:1
[INFO] [stderr]     |
[INFO] [stderr] 192 | / py_class!(class InstanceMethodReturnsNone |py| {
[INFO] [stderr] 193 | |     data member: AtomicUsize;
[INFO] [stderr] 194 | |
[INFO] [stderr] 195 | |     def value(&self) -> PyResult<usize> {
[INFO] [stderr] ...   |
[INFO] [stderr] 202 | |     }
[INFO] [stderr] 203 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:220:1
[INFO] [stderr]     |
[INFO] [stderr] 220 | / py_class!(class InstanceMethodWithArgs |py| {
[INFO] [stderr] 221 | |     data member: i32;
[INFO] [stderr] 222 | |
[INFO] [stderr] 223 | |     def method(&self, multiplier: i32) -> PyResult<i32> {
[INFO] [stderr] ...   |
[INFO] [stderr] 229 | |     }
[INFO] [stderr] 230 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:249:1
[INFO] [stderr]     |
[INFO] [stderr] 249 | / py_class!(class ClassMethod |py| {
[INFO] [stderr] 250 | |     def __new__(cls) -> PyResult<ClassMethod> {
[INFO] [stderr] 251 | |         ClassMethod::create_instance(py)
[INFO] [stderr] 252 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 257 | |     }
[INFO] [stderr] 258 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:281:1
[INFO] [stderr]     |
[INFO] [stderr] 281 | / py_class!(class ClassMethodWithArgs |py| {
[INFO] [stderr] 282 | |     @classmethod
[INFO] [stderr] 283 | |     def method(cls, input: &str) -> PyResult<String> {
[INFO] [stderr] 284 | |         Ok(format!("{}.method({})", cls.name(py), input))
[INFO] [stderr] 285 | |     }
[INFO] [stderr] 286 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:304:1
[INFO] [stderr]     |
[INFO] [stderr] 304 | / py_class!(class StaticMethod |py| {
[INFO] [stderr] 305 | |     def __new__(cls) -> PyResult<StaticMethod> {
[INFO] [stderr] 306 | |         StaticMethod::create_instance(py)
[INFO] [stderr] 307 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 312 | |     }
[INFO] [stderr] 313 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:337:1
[INFO] [stderr]     |
[INFO] [stderr] 337 | / py_class!(class StaticMethodWithArgs |py| {
[INFO] [stderr] 338 | |     @staticmethod
[INFO] [stderr] 339 | |     def method(input: i32) -> PyResult<String> {
[INFO] [stderr] 340 | |         Ok(format!("0x{:x}", input))
[INFO] [stderr] 341 | |     }
[INFO] [stderr] 342 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:357:1
[INFO] [stderr]     |
[INFO] [stderr] 357 | / py_class!(class StaticData |py| {
[INFO] [stderr] 358 | |     static VAL1 = 123;
[INFO] [stderr] 359 | |     static VAL2 = py.None();
[INFO] [stderr] 360 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:374:1
[INFO] [stderr]     |
[INFO] [stderr] 374 | / py_class!(class GCIntegration |py| {
[INFO] [stderr] 375 | |     data self_ref: RefCell<PyObject>;
[INFO] [stderr] 376 | |     data dropped: TestDropCall;
[INFO] [stderr] ...   |
[INFO] [stderr] 386 | |     }
[INFO] [stderr] 387 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:410:1
[INFO] [stderr]     |
[INFO] [stderr] 410 | / py_class!(class Len |py| {
[INFO] [stderr] 411 | |     data l: usize;
[INFO] [stderr] 412 | |
[INFO] [stderr] 413 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stderr] 414 | |         Ok(*self.l(py))
[INFO] [stderr] 415 | |     }
[INFO] [stderr] 416 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:434:1
[INFO] [stderr]     |
[INFO] [stderr] 434 | / py_class!(class Iterator |py| {
[INFO] [stderr] 435 | |     data iter: RefCell<Box<dyn iter::Iterator<Item=i32> + Send>>;
[INFO] [stderr] 436 | |
[INFO] [stderr] 437 | |     def __iter__(&self) -> PyResult<Iterator> {
[INFO] [stderr] ...   |
[INFO] [stderr] 443 | |     }
[INFO] [stderr] 444 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:456:1
[INFO] [stderr]     |
[INFO] [stderr] 456 | / py_class!(class StringMethods |py| {
[INFO] [stderr] 457 | |     def __str__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 458 | |         Ok("str")
[INFO] [stderr] 459 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 475 | |     }
[INFO] [stderr] 476 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:509:1
[INFO] [stderr]     |
[INFO] [stderr] 509 | / py_class!(class Comparisons |py| {
[INFO] [stderr] 510 | |     data val: i32;
[INFO] [stderr] 511 | |
[INFO] [stderr] 512 | |     def __hash__(&self) -> PyResult<i32> {
[INFO] [stderr] ...   |
[INFO] [stderr] 518 | |     }
[INFO] [stderr] 519 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:538:1
[INFO] [stderr]     |
[INFO] [stderr] 538 | / py_class!(class Sequence |py| {
[INFO] [stderr] 539 | |     def __len__(&self) -> PyResult<usize> {
[INFO] [stderr] 540 | |         Ok(5)
[INFO] [stderr] 541 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 550 | |     }
[INFO] [stderr] 551 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:563:1
[INFO] [stderr]     |
[INFO] [stderr] 563 | / py_class!(class SequenceRef |py| {
[INFO] [stderr] 564 | |     def __getitem__(&self, key: &str) -> PyResult<String> {
[INFO] [stderr] 565 | |         if key.is_empty() {
[INFO] [stderr] 566 | |             return Err(PyErr::new::<exc::IndexError, NoArgs>(py, NoArgs));
[INFO] [stderr] ...   |
[INFO] [stderr] 576 | |     }
[INFO] [stderr] 577 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:592:1
[INFO] [stderr]     |
[INFO] [stderr] 592 | / py_class!(class Callable |py| {
[INFO] [stderr] 593 | |     def __call__(&self, arg: i32) -> PyResult<i32> {
[INFO] [stderr] 594 | |         Ok(arg * 6)
[INFO] [stderr] 595 | |     }
[INFO] [stderr] 596 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:611:1
[INFO] [stderr]     |
[INFO] [stderr] 611 | / py_class!(class SetItem |py| {
[INFO] [stderr] 612 | |     data key: Cell<i32>;
[INFO] [stderr] 613 | |     data val: Cell<i32>;
[INFO] [stderr] ...   |
[INFO] [stderr] 619 | |     }
[INFO] [stderr] 620 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:634:1
[INFO] [stderr]     |
[INFO] [stderr] 634 | / py_class!(class SetItemRef |py| {
[INFO] [stderr] 635 | |     data key: RefCell<String>;
[INFO] [stderr] 636 | |     data val: Cell<i32>;
[INFO] [stderr] ...   |
[INFO] [stderr] 642 | |     }
[INFO] [stderr] 643 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:657:1
[INFO] [stderr]     |
[INFO] [stderr] 657 | / py_class!(class SetItemOptRef |py| {
[INFO] [stderr] 658 | |     data key: RefCell<String>;
[INFO] [stderr] 659 | |     data val: Cell<i32>;
[INFO] [stderr] ...   |
[INFO] [stderr] 669 | |     }
[INFO] [stderr] 670 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:684:1
[INFO] [stderr]     |
[INFO] [stderr] 684 | / py_class!(class DelItem |py| {
[INFO] [stderr] 685 | |     data key: Cell<i32>;
[INFO] [stderr] 686 | |
[INFO] [stderr] 687 | |     def __delitem__(&self, key: i32) -> PyResult<()> {
[INFO] [stderr] ...   |
[INFO] [stderr] 690 | |     }
[INFO] [stderr] 691 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:704:1
[INFO] [stderr]     |
[INFO] [stderr] 704 | / py_class!(class SetDelItem |py| {
[INFO] [stderr] 705 | |     data val: Cell<Option<i32>>;
[INFO] [stderr] 706 | |
[INFO] [stderr] 707 | |     def __setitem__(&self, key: i32, val: i32) -> PyResult<()> {
[INFO] [stderr] ...   |
[INFO] [stderr] 715 | |     }
[INFO] [stderr] 716 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:730:1
[INFO] [stderr]     |
[INFO] [stderr] 730 | / py_class!(class Reversed |py| {
[INFO] [stderr] 731 | |     def __reversed__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 732 | |         Ok("I am reversed")
[INFO] [stderr] 733 | |     }
[INFO] [stderr] 734 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:745:1
[INFO] [stderr]     |
[INFO] [stderr] 745 | / py_class!(class Contains |py| {
[INFO] [stderr] 746 | |     def __contains__(&self, item: i32) -> PyResult<bool> {
[INFO] [stderr] 747 | |         Ok(item >= 0)
[INFO] [stderr] 748 | |     }
[INFO] [stderr] 749 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:762:1
[INFO] [stderr]     |
[INFO] [stderr] 762 | / py_class!(class ContainsRef |py| {
[INFO] [stderr] 763 | |     def __contains__(&self, item: &str) -> PyResult<bool> {
[INFO] [stderr] 764 | |         Ok(item.is_empty())
[INFO] [stderr] 765 | |     }
[INFO] [stderr] 766 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:779:1
[INFO] [stderr]     |
[INFO] [stderr] 779 | / py_class!(class ContainsOptRef |py| {
[INFO] [stderr] 780 | |     def __contains__(&self, item: Option<&str>) -> PyResult<bool> {
[INFO] [stderr] 781 | |         Ok(item.map_or(false, str::is_empty))
[INFO] [stderr] 782 | |     }
[INFO] [stderr] 783 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:797:1
[INFO] [stderr]     |
[INFO] [stderr] 797 | / py_class!(class UnaryArithmetic |py| {
[INFO] [stderr] 798 | |     def __neg__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 799 | |         Ok("neg")
[INFO] [stderr] 800 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 812 | |     }
[INFO] [stderr] 813 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:827:1
[INFO] [stderr]     |
[INFO] [stderr] 827 | / py_class!(class BinaryArithmetic |py| {
[INFO] [stderr] 828 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 829 | |         Ok("BA")
[INFO] [stderr] 830 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 862 | |     }
[INFO] [stderr] 863 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:891:1
[INFO] [stderr]     |
[INFO] [stderr] 891 | / py_class!(class RichComparisons |py| {
[INFO] [stderr] 892 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 893 | |         Ok("RC")
[INFO] [stderr] 894 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 905 | |     }
[INFO] [stderr] 906 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:908:1
[INFO] [stderr]     |
[INFO] [stderr] 908 | / py_class!(class RichComparisons2 |py| {
[INFO] [stderr] 909 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 910 | |         Ok("RC2")
[INFO] [stderr] 911 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 919 | |     }
[INFO] [stderr] 920 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]    --> tests/test_class.rs:975:1
[INFO] [stderr]     |
[INFO] [stderr] 975 | / py_class!(class RichComparisonsRef |py| {
[INFO] [stderr] 976 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 977 | |         Ok("RCR")
[INFO] [stderr] 978 | |     }
[INFO] [stderr] ...   |
[INFO] [stderr] 989 | |     }
[INFO] [stderr] 990 | | });
[INFO] [stderr]     | |__^
[INFO] [stderr]     |
[INFO] [stderr]     = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]     = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]     = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1008:1
[INFO] [stderr]      |
[INFO] [stderr] 1008 | / py_class!(class RichComparisonsOptRef |py| {
[INFO] [stderr] 1009 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 1010 | |         Ok("RCR")
[INFO] [stderr] 1011 | |     }
[INFO] [stderr] ...    |
[INFO] [stderr] 1028 | |     }
[INFO] [stderr] 1029 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1043:1
[INFO] [stderr]      |
[INFO] [stderr] 1043 | / py_class!(class InPlaceOperations |py| {
[INFO] [stderr] 1044 | |     data value: Cell<u32>;
[INFO] [stderr] 1045 | |
[INFO] [stderr] 1046 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stderr] ...    |
[INFO] [stderr] 1088 | |     }
[INFO] [stderr] 1089 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1153:1
[INFO] [stderr]      |
[INFO] [stderr] 1153 | / py_class!(class InPlaceOperationsRef |py| {
[INFO] [stderr] 1154 | |     data value: RefCell<String>;
[INFO] [stderr] 1155 | |
[INFO] [stderr] 1156 | |     def __repr__(&self) -> PyResult<String> {
[INFO] [stderr] ...    |
[INFO] [stderr] 1164 | |     }
[INFO] [stderr] 1165 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1180:1
[INFO] [stderr]      |
[INFO] [stderr] 1180 | / py_class!(class ContextManager |py| {
[INFO] [stderr] 1181 | |     data exit_called : Cell<bool>;
[INFO] [stderr] 1182 | |
[INFO] [stderr] 1183 | |     def __enter__(&self) -> PyResult<i32> {
[INFO] [stderr] ...    |
[INFO] [stderr] 1194 | |     }
[INFO] [stderr] 1195 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1220:1
[INFO] [stderr]      |
[INFO] [stderr] 1220 | / py_class!(class Properties |py| {
[INFO] [stderr] 1221 | |     data value: Cell<i32>;
[INFO] [stderr] 1222 | |     data value_by_ref: RefCell<String>;
[INFO] [stderr] 1223 | |     data value_by_opt_ref: RefCell<String>;
[INFO] [stderr] ...    |
[INFO] [stderr] 1263 | |     }
[INFO] [stderr] 1264 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1308:1
[INFO] [stderr]      |
[INFO] [stderr] 1308 | / py_class!(pub(crate) class ClassWithVisibility |py| {
[INFO] [stderr] 1309 | |   pub(crate) def __new__(_cls) -> PyResult<Self> {
[INFO] [stderr] 1310 | |     Self::create_instance(py)
[INFO] [stderr] 1311 | |   }
[INFO] [stderr] ...    |
[INFO] [stderr] 1325 | |   }
[INFO] [stderr] 1326 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1383:1
[INFO] [stderr]      |
[INFO] [stderr] 1383 | / py_class!(class NumberExt |py| {
[INFO] [stderr] 1384 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 1385 | |         Ok("BA")
[INFO] [stderr] 1386 | |     }
[INFO] [stderr] ...    |
[INFO] [stderr] 1402 | |     }
[INFO] [stderr] 1403 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1427:1
[INFO] [stderr]      |
[INFO] [stderr] 1427 | / py_class!(class Py3Number |py| {
[INFO] [stderr] 1428 | |     def __repr__(&self) -> PyResult<&'static str> {
[INFO] [stderr] 1429 | |         Ok("BA")
[INFO] [stderr] 1430 | |     }
[INFO] [stderr] ...    |
[INFO] [stderr] 1442 | |     }
[INFO] [stderr] 1443 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]     --> tests/test_class.rs:1464:1
[INFO] [stderr]      |
[INFO] [stderr] 1464 | / py_class!(class DummyMatMul |py| {
[INFO] [stderr] 1465 | |     data number: i32;
[INFO] [stderr] 1466 | |     def __new__(_cls, arg: i32) -> PyResult<DummyMatMul> {
[INFO] [stderr] 1467 | |         DummyMatMul::create_instance(py, arg)
[INFO] [stderr] ...    |
[INFO] [stderr] 1476 | |     }
[INFO] [stderr] 1477 | | });
[INFO] [stderr]      | |__^
[INFO] [stderr]      |
[INFO] [stderr]      = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]      = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]      = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]      = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]      = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]      = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: calls to `std::mem::drop` with a value that implements `Copy` does nothing
[INFO] [stderr]    --> tests/test_function.rs:114:9
[INFO] [stderr]     |
[INFO] [stderr] 114 |         drop(py); // avoid unused variable warning
[INFO] [stderr]     |         ^^^^^--^
[INFO] [stderr]     |              |
[INFO] [stderr]     |              argument has type `Python<'_>`
[INFO] [stderr]     |
[INFO] [stderr]     = note: use `let _ = ...` to ignore the expression or result
[INFO] [stderr]     = note: `#[warn(dropping_copy_types)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: calls to `std::mem::drop` with a value that implements `Copy` does nothing
[INFO] [stderr]    --> tests/test_function.rs:133:9
[INFO] [stderr]     |
[INFO] [stderr] 133 |         drop(py);
[INFO] [stderr]     |         ^^^^^--^
[INFO] [stderr]     |              |
[INFO] [stderr]     |              argument has type `Python<'_>`
[INFO] [stderr]     |
[INFO] [stderr]     = note: use `let _ = ...` to ignore the expression or result
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]  --> tests/test_sharedref.rs:3:1
[INFO] [stderr]   |
[INFO] [stderr] 3 | / py_class!(class Owner |py| {
[INFO] [stderr] 4 | |     @shared data string: String;
[INFO] [stderr] 5 | | });
[INFO] [stderr]   | |__^
[INFO] [stderr]   |
[INFO] [stderr]   = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]   = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]   = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]   = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]   = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]   = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stderr]  --> tests/test_sharedref.rs:3:1
[INFO] [stderr]   |
[INFO] [stderr] 3 | / py_class!(class Owner |py| {
[INFO] [stderr] 4 | |     @shared data string: String;
[INFO] [stderr] 5 | | });
[INFO] [stderr]   | |__^
[INFO] [stderr]   |
[INFO] [stderr]   = help: move this `impl` block outside the of the current associated function `create_instance`
[INFO] [stderr]   = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stderr]   = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stderr]   = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[INFO] [stderr]   = note: the macro `$crate::py_class_impl` may come from an old version of the `cpython` crate, try updating your dependency with `cargo update -p cpython`
[INFO] [stderr]   = note: this warning originates in the macro `$crate::py_class_impl` which comes from the expansion of the macro `py_class` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `cpython` (test "test_class") generated 90 warnings (44 duplicates)
[INFO] [stderr] warning: `cpython` (test "test_function") generated 2 warnings
[INFO] [stderr] warning: `cpython` (test "test_sharedref") generated 2 warnings
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.03s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/cpython-c09e8601745735aa)
[INFO] [stdout] 
[INFO] [stdout] running 96 tests
[INFO] [stdout] test buffer::test::test_compatible_size ... ok
[INFO] [stdout] test argparse::test::test_parse ... ok
[INFO] [stdout] test objects::dict::test::test_contains ... ok
[INFO] [stdout] test buffer::test::test_bytes_buffer ... ok
[INFO] [stdout] test objectprotocol::number::test::addition ... ok
[INFO] [stdout] test err::tests::set_typeerror ... ok
[INFO] [stdout] test objectprotocol::test::test_debug_string ... ok
[INFO] [stdout] test objectprotocol::test::test_display_string ... ok
[INFO] [stdout] test argparse::test::test_default_param_type ... ok
[INFO] [stdout] test objects::dict::test::test_del_item_does_not_update_original_object ... ok
[INFO] [stdout] test objectprotocol::test::test_compare ... ok
[INFO] [stdout] test objects::iterator::tests::vec_iter ... ok
[INFO] [stdout] test objects::dict::test::test_del_item ... ok
[INFO] [stdout] test objects::list::test::test_append ... ok
[INFO] [stdout] test argparse::test::test_default_value ... ok
[INFO] [stdout] test objects::boolobject::test::test_true ... ok
[INFO] [stdout] test objects::list::test::test_extract ... ok
[INFO] [stdout] test objects::dict::test::test_items_list ... ok
[INFO] [stdout] test objects::dict::test::test_len ... ok
[INFO] [stdout] test objects::dict::test::test_set_item ... ok
[INFO] [stdout] test objects::dict::test::test_set_item_does_not_update_original_object ... ok
[INFO] [stdout] test objects::num::test::float_to_i32 ... ok
[INFO] [stdout] test objects::dict::test::test_get_item ... ok
[INFO] [stdout] test objects::dict::test::test_items ... ok
[INFO] [stdout] test objects::num::test::float_to_i64 ... ok
[INFO] [stdout] test objects::list::test::test_len ... ok
[INFO] [stdout] test objects::boolobject::test::test_false ... ok
[INFO] [stdout] test objects::list::test::test_get_item ... ok
[INFO] [stdout] test objects::num::test::float_to_u32 ... ok
[INFO] [stdout] test objects::list::test::test_set_item ... ok
[INFO] [stdout] test objects::list::test::test_iter ... ok
[INFO] [stdout] test objects::num::test::int_to_float ... ok
[INFO] [stdout] test objects::list::test::test_insert ... ok
[INFO] [stdout] test objects::num::test::float_to_u64 ... ok
[INFO] [stdout] test objects::num::test::str_to_i32 ... ok
[INFO] [stdout] test objects::num::test::str_to_i64 ... ok
[INFO] [stdout] test objects::num::test::str_to_u32 ... ok
[INFO] [stdout] test objects::num::test::str_to_u64 ... ok
[INFO] [stdout] test objects::num::test::test_i64_max ... ok
[INFO] [stdout] test objects::num::test::test_i64_min ... ok
[INFO] [stdout] test objects::num::test::test_u32_max ... ok
[INFO] [stdout] test objects::num::test::test_u64_max ... ok
[INFO] [stdout] test objects::num::test::to_from_f64 ... ok
[INFO] [stdout] test objects::num::test::to_from_f32 ... ok
[INFO] [stdout] test objects::num::test::to_from_i16 ... ok
[INFO] [stdout] test objects::num::test::to_from_i32 ... ok
[INFO] [stdout] test objects::num::test::to_from_i64 ... ok
[INFO] [stdout] test objects::num::test::to_from_i8 ... ok
[INFO] [stdout] test objects::num::test::to_from_isize ... ok
[INFO] [stdout] test objects::num::test::to_from_u16 ... ok
[INFO] [stdout] test objects::num::test::to_from_u32 ... ok
[INFO] [stdout] test objects::num::test::to_from_u64 ... ok
[INFO] [stdout] test objects::num::test::to_from_u8 ... ok
[INFO] [stdout] test objects::num::test::to_from_usize ... ok
[INFO] [stdout] test objects::object::test_sizeof ... ok
[INFO] [stdout] test objects::sequence::test::test_extract_bytearray_to_vec ... ok
[INFO] [stdout] test objects::sequence::test::test_extract_range_to_vec ... ok
[INFO] [stdout] test objects::sequence::test::test_list_coercion ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_concat ... ok
[INFO] [stdout] test objects::sequence::test::test_numbers_are_not_sequences ... ok
[INFO] [stdout] test objects::sequence::test::test_lists_coerce_to_tuples ... ok
[INFO] [stdout] test objects::sequence::test::test_extract_tuple_to_vec ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_contains ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_count ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_get_item ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_iter ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_index ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_repeat ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_strings ... ok
[INFO] [stdout] test objects::sequence::test::test_strings_are_sequences ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_concat_string ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_empty ... ok
[INFO] [stdout] test objects::sequence::test::test_strings_coerce_to_lists ... ok
[INFO] [stdout] test objects::sequence::test::test_tuple_coercion ... ok
[INFO] [stdout] test objects::set::test::test_add ... ok
[INFO] [stdout] test objects::set::test::test_add_does_not_update_original_object ... ok
[INFO] [stdout] test objects::sequence::test::test_seq_del_item ... ok
[INFO] [stdout] test objects::set::test::test_contains ... ok
[INFO] [stdout] test objects::set::test::test_btree_set ... ok
[INFO] [stdout] test objects::set::test::test_discard ... ok
[INFO] [stdout] test objects::set::test::test_discard_does_not_update_original_object ... ok
[INFO] [stdout] test objects::set::test::test_len ... ok
[INFO] [stdout] test objects::set::test::test_pop ... ok
[INFO] [stdout] test objects::set::test::test_clear ... ok
[INFO] [stdout] test objects::set::test::test_pop_does_not_update_original_object ... ok
[INFO] [stdout] test objects::string::test::test_extract_byte_str ... ok
[INFO] [stdout] test objects::string::test::test_extract_lone_surrogate ... ok
[INFO] [stdout] test objects::string::test::test_extract_lone_surrogate_lossy ... ok
[INFO] [stdout] test objects::string::test::test_extract_str ... ok
[INFO] [stdout] test objects::string::test::test_extract_umlaut ... ok
[INFO] [stdout] test objects::string::test::test_non_bmp ... ok
[INFO] [stdout] test objects::tests::test_btreemap_to_python ... ok
[INFO] [stdout] test objects::tests::test_hashmap_to_python ... ok
[INFO] [stdout] test objects::tuple::test::test_len ... ok
[INFO] [stdout] test python::test::test_eval ... ok
[INFO] [stdout] test buffer::test::test_array_buffer ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 96 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.05s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_class.rs (/opt/rustwide/target/debug/deps/test_class-405f1a1594e44ff5)
[INFO] [stdout] 
[INFO] [stdout] running 46 tests
[INFO] [stdout] test class_method ... ok
[INFO] [stdout] test class_method_with_args ... ok
[INFO] [stdout] test contains ... ok
[INFO] [stdout] test context_manager ... ok
[INFO] [stdout] test contains_opt_ref ... ok
[INFO] [stdout] test data_is_dropped ... ok
[INFO] [stdout] test empty_class_with_new ... ok
[INFO] [stdout] test empty_class_in_module ... ok
[INFO] [stdout] test binary_arithmetic ... ok
[INFO] [stdout] test delitem ... ok
[INFO] [stdout] test class_with_visibility ... ok
[INFO] [stdout] test comparisons ... ok
[INFO] [stdout] test contains_ref ... ok
[INFO] [stdout] test callable ... ok
[INFO] [stdout] test python3_numbers ... ok
[INFO] [stdout] test gc_integration ... ok
[INFO] [stdout] test inplace_operations ... ok
[INFO] [stdout] test inplace_operations_ref ... ok
[INFO] [stdout] test instance_method ... ok
[INFO] [stdout] test instance_method_returns_none ... ok
[INFO] [stdout] test rich_comparisons_ref ... ok
[INFO] [stdout] test iterator ... ok
[INFO] [stdout] test sequence_ref ... ok
[INFO] [stdout] test matrix_multiply ... ok
[INFO] [stdout] test new_with_one_arg ... ok
[INFO] [stdout] test new_with_two_args ... ok
[INFO] [stdout] test python3_string_methods ... ok
[INFO] [stdout] test rich_comparisons ... ok
[INFO] [stdout] test rich_comparisons_opt_ref ... ok
[INFO] [stdout] test rich_comparisons_python_3_type_error ... ok
[INFO] [stdout] test instance_method_with_args ... ok
[INFO] [stdout] test sequence ... ok
[INFO] [stdout] test len ... ok
[INFO] [stdout] test setdelitem ... ok
[INFO] [stdout] test setitem_ref ... ok
[INFO] [stdout] test setitem ... ok
[INFO] [stdout] test setitem_opt_ref ... ok
[INFO] [stdout] test static_data ... ok
[INFO] [stdout] test properties ... ok
[INFO] [stdout] test empty_class ... ok
[INFO] [stdout] test reversed ... ok
[INFO] [stdout] test string_methods ... ok
[INFO] [stdout] test unary_arithmetic ... ok
[INFO] [stdout] test static_method ... ok
[INFO] [stdout] test number_extensions ... ok
[INFO] [stdout] test static_method_with_args ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 46 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_function.rs (/opt/rustwide/target/debug/deps/test_function-9e729aab00fafdd9)
[INFO] [stdout] 
[INFO] [stdout] running 7 tests
[INFO] [stdout] test inline_two_args ... ok
[INFO] [stdout] test panicking ... ok
[INFO] [stdout] test one_arg ... ok
[INFO] [stdout] test no_args ... ok
[INFO] [stdout] test trailing_comma ... ok
[INFO] [stdout] test none_return ... ok
[INFO] [stdout] test opt_args ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_sharedref.rs (/opt/rustwide/target/debug/deps/test_sharedref-37031fa130daf3f7)
[INFO] [stdout] 
[INFO] [stdout] running 13 tests
[INFO] [stdout] test test_leaked_borrow ... ok
[INFO] [stdout] test test_borrow_while_borrow_mut - should panic ... ok
[INFO] [stdout] test test_leaked_borrow_after_mut ... ok
[INFO] [stdout] test test_leaked_borrow_mut ... ok
[INFO] [stdout] test test_leaked_borrow_mut_after_mut ... ok
[INFO] [stdout] test test_borrow_mut_while_borrow - should panic ... ok
[INFO] [stdout] test test_try_borrow_mut_while_leaked_ref ... ok
[INFO] [stdout] test test_try_borrow_mut_while_borrow ... ok
[INFO] [stdout] test test_leaked_map_after_mut - should panic ... ok
[INFO] [stdout] test test_try_leak_while_borrow_mut ... ok
[INFO] [stdout] test test_leak_while_borrow_mut - should panic ... ok
[INFO] [stdout] test test_try_borrow_mut_while_leaked_ref_mut ... ok
[INFO] [stdout] test test_try_borrow_while_borrow_mut ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 13 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_thread_exit.rs (/opt/rustwide/target/debug/deps/test_thread_exit-fba9200bd1484810)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests cpython
[INFO] [stdout] 
[INFO] [stdout] running 33 tests
[INFO] [stdout] test src/lib.rs - (line 56) ... ignored
[INFO] [stdout] test src/objectprotocol.rs - objectprotocol::ObjectProtocol::compare (line 90) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule (line 201) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule (line 210) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule_fn (line 386) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule_fn (line 397) ... ignored
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 120) ... ignored
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 134) ... ignored
[INFO] [stdout] test src/objectprotocol.rs - objectprotocol::ObjectProtocol::call_method (line 228) - compile ... ok
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::PyCapsule (line 34) - compile ... ok
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule (line 232) - compile ... ok
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 63) ... ignored
[INFO] [stdout] test src/objects/none.rs - objects::none::PyNone (line 31) ... ok
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::PyCapsule::new (line 569) ... ok
[INFO] [stdout] test src/sharedref.rs - sharedref::PySharedRef (line 104) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::PyCapsule (line 133) ... ok
[INFO] [stdout] test src/sharedref.rs - sharedref::UnsafePyLeaked (line 310) ... ignored
[INFO] [stdout] test src/sharedref.rs - sharedref::UnsafePyLeaked (line 315) ... ignored
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule (line 317) ... ok
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule_fn (line 462) ... ok
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::PyCapsule (line 165) ... ok
[INFO] [stdout] test src/objects/tuple.rs - objects::tuple::NoArgs (line 206) ... ok
[INFO] [stdout] test src/objects/module.rs - objects::module::PyModule::call (line 115) ... ok
[INFO] [stdout] test src/err.rs - err::py_exception (line 42) ... ok
[INFO] [stdout] test src/lib.rs - (line 71) ... FAILED
[INFO] [stdout] test src/objects/capsule.rs - objects::capsule::py_capsule_fn (line 418) ... ok
[INFO] [stdout] test src/function.rs - function::py_fn (line 99) ... ok
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 237) ... ok
[INFO] [stdout] test src/pythonrun.rs - pythonrun::GILGuard (line 87) ... ok
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 289) ... ok
[INFO] [stdout] test src/py_class/py_class.rs - py_class::py_class::py_class (line 36) ... ok
[INFO] [stdout] test src/pythonrun.rs - pythonrun::GILProtected (line 145) ... ok
[INFO] [stdout] test src/sharedref.rs - sharedref::PySharedRefCell (line 41) ... ok
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout] 
[INFO] [stdout] ---- src/lib.rs - (line 71) stdout ----
[INFO] [stdout] Test executable failed (exit status: 101).
[INFO] [stdout] 
[INFO] [stdout] stderr:
[INFO] [stdout] thread 'main' panicked at src/lib.rs:8:25:
[INFO] [stdout] called `Result::unwrap()` on an `Err` value: PyErr { ptype: <class 'TypeError'>, pvalue: Some('Expected type that converts to PyString but received NoneType'), ptraceback: None }
[INFO] [stdout] stack backtrace:
[INFO] [stdout]    0:     0x5574b4413bc5 - std::backtrace_rs::backtrace::libunwind::trace::h59d96bdb08384354
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/../../backtrace/src/backtrace/libunwind.rs:105:5
[INFO] [stdout]    1:     0x5574b4413bc5 - std::backtrace_rs::backtrace::trace_unsynchronized::h9cf5becacfc93fba
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
[INFO] [stdout]    2:     0x5574b4413bc5 - std::sys_common::backtrace::_print_fmt::h10b76d10405dbd48
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/sys_common/backtrace.rs:68:5
[INFO] [stdout]    3:     0x5574b4413bc5 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h6ed9e62a156d84e4
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/sys_common/backtrace.rs:44:22
[INFO] [stdout]    4:     0x5574b443130b - core::fmt::rt::Argument::fmt::h645c680983f03c9f
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/core/src/fmt/rt.rs:165:63
[INFO] [stdout]    5:     0x5574b443130b - core::fmt::write::h8bcd80919a02be29
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/core/src/fmt/mod.rs:1169:21
[INFO] [stdout]    6:     0x5574b4411dff - std::io::Write::write_fmt::hed769ca6c29434ec
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/io/mod.rs:1835:15
[INFO] [stdout]    7:     0x5574b441399e - std::sys_common::backtrace::_print::h6306f131a28d62b0
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/sys_common/backtrace.rs:47:5
[INFO] [stdout]    8:     0x5574b441399e - std::sys_common::backtrace::print::h7079288e0a26dfcc
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/sys_common/backtrace.rs:34:9
[INFO] [stdout]    9:     0x5574b4414d09 - std::panicking::default_hook::{{closure}}::hb063ecec81a736ba
[INFO] [stdout]   10:     0x5574b4414a4d - std::panicking::default_hook::hd56ee406bf547b5c
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:298:9
[INFO] [stdout]   11:     0x5574b44151a3 - std::panicking::rust_panic_with_hook::h624aa3ca42ebb8f2
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:795:13
[INFO] [stdout]   12:     0x5574b4415084 - std::panicking::begin_panic_handler::{{closure}}::hbc4e76194a5e287c
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:664:13
[INFO] [stdout]   13:     0x5574b4414089 - std::sys_common::backtrace::__rust_end_short_backtrace::h847fedc9d1ff7b6d
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/sys_common/backtrace.rs:171:18
[INFO] [stdout]   14:     0x5574b4414db7 - rust_begin_unwind
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:652:5
[INFO] [stdout]   15:     0x5574b43ece33 - core::panicking::panic_fmt::hec11a924b87ce965
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/core/src/panicking.rs:72:14
[INFO] [stdout]   16:     0x5574b43ed326 - core::result::unwrap_failed::h382691b96ca8c13a
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/core/src/result.rs:1654:5
[INFO] [stdout]   17:     0x5574b43ee2f8 - rust_out::main::h696a342f0ae7cd72
[INFO] [stdout]   18:     0x5574b43ed803 - core::ops::function::FnOnce::call_once::hacff659aa20c7b40
[INFO] [stdout]   19:     0x5574b43ed656 - std::sys_common::backtrace::__rust_begin_short_backtrace::hcc6b8bea3112e884
[INFO] [stdout]   20:     0x5574b43ed6a9 - std::rt::lang_start::{{closure}}::h4db0ca8543e29a47
[INFO] [stdout]   21:     0x5574b440f46d - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h239f0051f1e18680
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/core/src/ops/function.rs:284:13
[INFO] [stdout]   22:     0x5574b440f46d - std::panicking::try::do_call::hf7072797cbfea7fa
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:559:40
[INFO] [stdout]   23:     0x5574b440f46d - std::panicking::try::h3a37e38691a5244b
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:523:19
[INFO] [stdout]   24:     0x5574b440f46d - std::panic::catch_unwind::hc7cc1460e4236209
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panic.rs:149:14
[INFO] [stdout]   25:     0x5574b440f46d - std::rt::lang_start_internal::{{closure}}::hce632608b277cffc
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/rt.rs:141:48
[INFO] [stdout]   26:     0x5574b440f46d - std::panicking::try::do_call::hafc0f13e6abd9d79
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:559:40
[INFO] [stdout]   27:     0x5574b440f46d - std::panicking::try::h67b8f1800ef15799
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panicking.rs:523:19
[INFO] [stdout]   28:     0x5574b440f46d - std::panic::catch_unwind::he5b260dc522c68be
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/panic.rs:149:14
[INFO] [stdout]   29:     0x5574b440f46d - std::rt::lang_start_internal::hf119eb75d1ffe221
[INFO] [stdout]                                at /rustc/1871252fc8bb672d40787e67404e6eaae7059369/library/std/src/rt.rs:141:20
[INFO] [stdout]   30:     0x5574b43ed687 - std::rt::lang_start::ha9360cc92730957e
[INFO] [stdout]   31:     0x5574b43eeb75 - main
[INFO] [stdout]   32:     0x7f8164d97d90 - <unknown>
[INFO] [stdout]   33:     0x7f8164d97e40 - __libc_start_main
[INFO] [stdout]   34:     0x5574b43ed585 - _start
[INFO] [stdout]   35:                0x0 - <unknown>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout]     src/lib.rs - (line 71)
[INFO] [stdout] 
[INFO] [stdout] test result: FAILED. 20 passed; 1 failed; 12 ignored; 0 measured; 0 filtered out; finished in 0.61s
[INFO] [stdout] 
[INFO] [stderr] error: doctest failed, to rerun pass `--doc`
[INFO] running `Command { std: "docker" "inspect" "15520d6f17816102796f03f95f2dfb45bc587c1368110929cfa0638c2765ffde", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "15520d6f17816102796f03f95f2dfb45bc587c1368110929cfa0638c2765ffde", kill_on_drop: false }`
[INFO] [stdout] 15520d6f17816102796f03f95f2dfb45bc587c1368110929cfa0638c2765ffde
