[INFO] fetching crate cpython 0.7.1...
[INFO] checking cpython-0.7.1 against master#5518eaa946291f00471af8b254b2a1715f234882 for pr-120393
[INFO] extracting crate cpython 0.7.1 into /workspace/builds/worker-3-tc1/source
[INFO] validating manifest of crates.io crate cpython 0.7.1 on toolchain 5518eaa946291f00471af8b254b2a1715f234882
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5518eaa946291f00471af8b254b2a1715f234882" "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-3-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" "+5518eaa946291f00471af8b254b2a1715f234882" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded rustversion v1.0.5
[INFO] [stderr]   Downloaded serde_bytes v0.11.5
[INFO] [stderr]   Downloaded half v1.7.1
[INFO] [stderr]   Downloaded python3-sys v0.7.1
[INFO] [stderr]   Downloaded syn v1.0.80
[INFO] [stderr]   Downloaded libc v0.2.103
[INFO] [stderr]   Downloaded python27-sys v0.7.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+5518eaa946291f00471af8b254b2a1715f234882" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 04740fb39f89baaa277d2af09fac7bc6bfbcb59132da7ae4cc59aed7f967705a
[INFO] running `Command { std: "docker" "start" "-a" "04740fb39f89baaa277d2af09fac7bc6bfbcb59132da7ae4cc59aed7f967705a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "04740fb39f89baaa277d2af09fac7bc6bfbcb59132da7ae4cc59aed7f967705a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "04740fb39f89baaa277d2af09fac7bc6bfbcb59132da7ae4cc59aed7f967705a", kill_on_drop: false }`
[INFO] [stdout] 04740fb39f89baaa277d2af09fac7bc6bfbcb59132da7ae4cc59aed7f967705a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+5518eaa946291f00471af8b254b2a1715f234882" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 8c3824bed931946637f56aaec9c1c5977e2464d715dfd9e4c730603bc0ff5a97
[INFO] running `Command { std: "docker" "start" "-a" "8c3824bed931946637f56aaec9c1c5977e2464d715dfd9e4c730603bc0ff5a97", kill_on_drop: false }`
[INFO] [stderr]    Compiling memchr v2.4.1
[INFO] [stderr]    Compiling regex-syntax v0.6.27
[INFO] [stderr]    Compiling autocfg v1.0.1
[INFO] [stderr]    Compiling serde v1.0.130
[INFO] [stderr]    Compiling libc v0.2.103
[INFO] [stderr]    Compiling cpython v0.7.1 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling rustversion v1.0.5
[INFO] [stderr]    Compiling paste v1.0.5
[INFO] [stderr]     Checking half v1.7.1
[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]     Checking serde_bytes v0.11.5
[INFO] [stderr]     Checking serde_cbor v0.11.2
[INFO] [stderr]    Compiling python3-sys v0.7.1
[INFO] [stdout] warning: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout]     = note: `#[warn(static_mut_ref)]` 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout]     = note: `#[warn(static_mut_ref)]` 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout] help: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout] help: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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] [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: 13 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.81s
[INFO] running `Command { std: "docker" "inspect" "8c3824bed931946637f56aaec9c1c5977e2464d715dfd9e4c730603bc0ff5a97", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8c3824bed931946637f56aaec9c1c5977e2464d715dfd9e4c730603bc0ff5a97", kill_on_drop: false }`
[INFO] [stdout] 8c3824bed931946637f56aaec9c1c5977e2464d715dfd9e4c730603bc0ff5a97
[INFO] checking cpython-0.7.1 against try#7622c0f807a4e13c4db886a1681bf343795692df+rustflags=-Dnon_local_definitions for pr-120393
[INFO] extracting crate cpython 0.7.1 into /workspace/builds/worker-3-tc2/source
[INFO] validating manifest of crates.io crate cpython 0.7.1 on toolchain 7622c0f807a4e13c4db886a1681bf343795692df
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+7622c0f807a4e13c4db886a1681bf343795692df" "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-3-tc2/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" "+7622c0f807a4e13c4db886a1681bf343795692df" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+7622c0f807a4e13c4db886a1681bf343795692df" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 00ff8b5252df168f285c7fcb717ddf7b37e18a9004a4f8bef34d6ff42e7addbf
[INFO] running `Command { std: "docker" "start" "-a" "00ff8b5252df168f285c7fcb717ddf7b37e18a9004a4f8bef34d6ff42e7addbf", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "00ff8b5252df168f285c7fcb717ddf7b37e18a9004a4f8bef34d6ff42e7addbf", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "00ff8b5252df168f285c7fcb717ddf7b37e18a9004a4f8bef34d6ff42e7addbf", kill_on_drop: false }`
[INFO] [stdout] 00ff8b5252df168f285c7fcb717ddf7b37e18a9004a4f8bef34d6ff42e7addbf
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/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 -Dnon_local_definitions" "-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+7622c0f807a4e13c4db886a1681bf343795692df" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] f2680ac1dcbc2a59ce1f813e7d1d8be30ce88164981a956b28fc4b7777eb4f44
[INFO] running `Command { std: "docker" "start" "-a" "f2680ac1dcbc2a59ce1f813e7d1d8be30ce88164981a956b28fc4b7777eb4f44", kill_on_drop: false }`
[INFO] [stderr]    Compiling memchr v2.4.1
[INFO] [stderr]    Compiling regex-syntax v0.6.27
[INFO] [stderr]    Compiling serde v1.0.130
[INFO] [stderr]    Compiling libc v0.2.103
[INFO] [stderr]    Compiling autocfg v1.0.1
[INFO] [stderr]    Compiling cpython v0.7.1 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling rustversion v1.0.5
[INFO] [stderr]     Checking half v1.7.1
[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]     Checking serde_cbor v0.11.2
[INFO] [stderr]     Checking serde_bytes v0.11.5
[INFO] [stderr]    Compiling python3-sys v0.7.1
[INFO] [stdout] warning: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout]     = note: `#[warn(static_mut_ref)]` 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout]     = note: `#[warn(static_mut_ref)]` 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout] help: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of mutable static
[INFO] [stdout]     |
[INFO] [stdout]     = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
[INFO] [stdout]     = note: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
[INFO] [stdout] help: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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: mutable reference of 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 of 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: reference of mutable static is a hard error from 2024 edition
[INFO] [stdout]     = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause 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: mutable references are dangerous since if there's any other pointer or reference used for that static while the reference lives, that's UB; 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] [stdout] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: requested on the command line with `-D non-local-definitions`
[INFO] [stdout]   = note: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: aborting due to 2 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `cpython` (test "test_sharedref") due to 3 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[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: 13 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: requested on the command line with `-D non-local-definitions`
[INFO] [stdout]    = note: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 377 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 377 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 614 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 614 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 637 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 637 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 660 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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] 660 | |
[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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: 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 neither the type nor the trait are at the same nesting level as the `impl` block
[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: this error 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] error: aborting due to 90 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `cpython` (test "test_class") due to 91 previous errors
[INFO] running `Command { std: "docker" "inspect" "f2680ac1dcbc2a59ce1f813e7d1d8be30ce88164981a956b28fc4b7777eb4f44", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f2680ac1dcbc2a59ce1f813e7d1d8be30ce88164981a956b28fc4b7777eb4f44", kill_on_drop: false }`
[INFO] [stdout] f2680ac1dcbc2a59ce1f813e7d1d8be30ce88164981a956b28fc4b7777eb4f44
