dosubot[bot] commented on issue #6860:
URL: https://github.com/apache/opendal/issues/6860#issuecomment-3609583149

   <!-- Answer -->
   This error is likely caused by a mismatch between the versions of 
pyo3-stub-gen and pyo3, or by a recent change in PyO3 where the 
`PyEncodingWarning` type was removed or renamed (possibly to 
`PyUnicodeWarning`). To resolve this, check your `Cargo.toml` for the versions 
of both pyo3-stub-gen and pyo3, and make sure they are compatible. You may need 
to update pyo3-stub-gen or patch it to use `PyUnicodeWarning` if 
`PyEncodingWarning` is no longer present in the latest PyO3.
   
   It's also worth reviewing the PyO3 changelog to confirm when this change 
occurred. If you want to further isolate the issue, try building with an older 
Python version (like 3.10) to see if the error persists. For reference, a 
similar issue was resolved in the past by updating PyO3 to support the newer 
Python version, which suggests that keeping dependencies up to date is 
important for compatibility 
([source](https://github.com/apache/opendal/issues/4268)).
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/c103cf8e-9b80-4f5b-8d20-b6df37928889?feedback_type=other)</sup>
   
   [![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/997a2c5a-0c54-497b-989d-44651635dd36/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20error%20is%20likely%20caused%20by%20a%20mismatch%20between%20the%20versions%20of%20pyo3-stub-gen%20and%20pyo3%2C%20or%20by%20a%20recent%20change%20in%20PyO3%20where%20the%20%60PyEncodingWarning%60%20type%20was%20removed%20or%20renamed%20%28possibly%20to%20%60PyUnicodeWarning%60%29.%20To%20resolve%20this%2C%20check%20your%20%60Cargo.toml%60%20for%20the%20versions%20of%20both%20pyo3-stub-gen%20and%20pyo3%2C%20and%20make%20sure%20they%20are%20compatible.%20You%20may%20need%20to%20update%20pyo3-stub-gen%20or%20patch%20it%20to%20use%20%60PyUnicodeWarning%60%20if%20%60PyEncodingWarning%60%20is%20no%20longer%20present%20in%20the%20latest%20PyO3.%0A%0AIt%27s%20also%20worth%20reviewing%20the%20PyO3%20changelog%20to%20confirm%20when%20this%20change%20
 
occurred.%20If%20you%20want%20to%20further%20isolate%20the%20issue%2C%20try%20building%20with%20an%20older%20Python%20version%20%28like%203.10%29%20to%20see%20if%20the%20error%20persists.%20For%20reference%2C%20a%20similar%20issue%20was%20resolved%20in%20the%20past%20by%20updating%20PyO3%20to%20support%20the%20newer%20Python%20version%2C%20which%20suggests%20that%20keeping%20dependencies%20up%20to%20date%20is%20important%20for%20compatibility%20%28%5Bsource%5D%28https%3A//github.com/apache/opendal/issues/4268%29%29.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/opendal/issues/6860)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to