tisonkun commented on PR #9808:
URL: 
https://github.com/apache/arrow-datafusion/pull/9808#issuecomment-2065501861

   This can cause a clippy failure (and perhaps further compiler error) as desc 
in https://github.com/PyO3/pyo3/issues/4094.
   
   But we need to release a new arrow version and bump the dep to arrow in 
datafusion first?
   
   ```
   stdout :     Updating crates.io index
   error: failed to select a version for `pyo3-ffi`.
       ... required by package `pyo3 v0.20.0`
       ... which satisfies dependency `pyo3 = "^0.20"` of package `arrow 
v51.0.0`
       ... which satisfies dependency `arrow = "^51.0.0"` of package 
`datafusion-benchmarks v37.0.0 
(/Users/tison/Brittani/arrow-datafusion/benchmarks)`
   versions that meet the requirements `=0.20.0` are: 0.20.0
   
   the package `pyo3-ffi` links to the native library `python`, but it 
conflicts with a previous package which links to `python` as well:
   package `pyo3-ffi v0.21.2`
       ... which satisfies dependency `pyo3-ffi = "=0.21.2"` of package `pyo3 
v0.21.2`
       ... which satisfies dependency `pyo3 = "^0.21.2"` of package 
`datafusion-common v37.0.0 
(/Users/tison/Brittani/arrow-datafusion/datafusion/common)`
       ... which satisfies path dependency `datafusion-common` (locked to 
37.0.0) of package `datafusion-benchmarks v37.0.0 
(/Users/tison/Brittani/arrow-datafusion/benchmarks)`
   Only one package in the dependency graph may specify the same links value. 
This helps ensure that only one copy of a native library is linked in the final 
binary. Try to adjust your dependencies so that only one package uses the 
`links = "python"` value. For more information, see 
https://doc.rust-lang.org/cargo/reference/resolver.html#links.
   
   failed to select a version for `pyo3-ffi` which could resolve this conflict
   ```


-- 
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