pyo3/tests/ui/invalid_result_conversion.s...

error[E0277]: the trait bound `PyErr: From<MyError>` is not satisfied
  --> tests/ui/invalid_result_conversion.rs:21:1
   |
21 | #[pyfunction]
   | ^^^^^^^^^^^^^ the trait `From<MyError>` is not implemented for `PyErr`
   |
   = help: the following other types implement trait `From<T>`:
             <PyErr as From<pyo3::Bound<'py, T>>>
             <PyErr as From<std::io::Error>>
             <PyErr as From<PyBorrowError>>
             <PyErr as From<PyBorrowMutError>>
             <PyErr as From<PyDowncastError<'a>>>
             <PyErr as From<DowncastError<'_, '_>>>
             <PyErr as From<DowncastIntoError<'_>>>
             <PyErr as From<NulError>>
           and $N others
   = note: required for `MyError` to implement `Into<PyErr>`
   = note: this error originates in the attribute macro `pyfunction` (in Nightly builds, run with -Z macro-backtrace for more info)
Don't use intocallback in method macros (#2664) * Don't use intocallback in method macros Co-authored-by: mejrs <> 2022-10-16 09:35:58 +00:00			error[E0277]: the trait bound `PyErr: From<MyError>` is not satisfied
Fix IntoPyCallbackOutput paper cuts (#2326) * Implement IntoPy for arrays of IntoPy * Improve `IntoPyCallbackOutput` compile error 2022-05-09 17:15:43 +00:00			`--> tests/ui/invalid_result_conversion.rs:21:1`
			`\|`
			`21 \| #[pyfunction]`
Don't use intocallback in method macros (#2664) * Don't use intocallback in method macros Co-authored-by: mejrs <> 2022-10-16 09:35:58 +00:00			\| ^^^^^^^^^^^^^ the trait `From<MyError>` is not implemented for `PyErr`
Fix IntoPyCallbackOutput paper cuts (#2326) * Implement IntoPy for arrays of IntoPy * Improve `IntoPyCallbackOutput` compile error 2022-05-09 17:15:43 +00:00			`\|`
Don't use intocallback in method macros (#2664) * Don't use intocallback in method macros Co-authored-by: mejrs <> 2022-10-16 09:35:58 +00:00			= help: the following other types implement trait `From<T>`:
Implement `From<Bound<'py, T>>` for PyErr (#3881) * Implement `From<Bound<'py, T>>` for PyErr * Replace PyErr::from_value_bound calls with .into * Fix From<MyError> expected error message * Add a trait bound to From<Bound<'py, T>> for PyErr 2024-02-26 23:14:41 +00:00			`<PyErr as From<pyo3::Bound<'py, T>>>`
ci: updates for Rust 1.72 2023-08-25 08:48:01 +00:00			`<PyErr as From<std::io::Error>>`
update `test_compile_error` ui test output 2024-01-27 11:37:26 +00:00			`<PyErr as From<PyBorrowError>>`
add `call_bound` and `call_method_bound` 2023-12-29 14:43:43 +00:00			`<PyErr as From<PyBorrowMutError>>`
ci: updates for Rust 1.72 2023-08-25 08:48:01 +00:00			`<PyErr as From<PyDowncastError<'a>>>`
make `DowncastError` and `DowncastIntoError` public 2023-12-21 12:51:39 +00:00			`<PyErr as From<DowncastError<'_, '_>>>`
			`<PyErr as From<DowncastIntoError<'_>>>`
ci: updates for Rust 1.72 2023-08-25 08:48:01 +00:00			`<PyErr as From<NulError>>`
Don't use intocallback in method macros (#2664) * Don't use intocallback in method macros Co-authored-by: mejrs <> 2022-10-16 09:35:58 +00:00			`and $N others`
Update ui tests for Rust 1.65.0 2022-11-04 04:29:23 +00:00			= note: required for `MyError` to implement `Into<PyErr>`
Fix IntoPyCallbackOutput paper cuts (#2326) * Implement IntoPy for arrays of IntoPy * Improve `IntoPyCallbackOutput` compile error 2022-05-09 17:15:43 +00:00			= note: this error originates in the attribute macro `pyfunction` (in Nightly builds, run with -Z macro-backtrace for more info)