Closed Michael-J-Ward closed 1 month ago
I'm sure @andygrove would have the same Q as on previous PR.
@davidhewitt, could you spare a little more knowledge about the effects of changing lib.name
?
Does this have any impact on downstream maturin projects that use this crate as a dependency? If they also use the name _internal, will there be a conflict?
Should we replace all references to _internal with datafusion_internal instead?
@andygrove , I have another commit queued up if you want to switch the lib.name
and python module from _internal
to _datafusion_internal
@andygrove , I have another commit queued up if you want to switch the
lib.name
and python module from_internal
to_datafusion_internal
I think we can undo this last commit and ignore my question/concern. I missed that the maturin project definition was already qualifying _internal
as datafusion._internal
, so I think there should be no conflict with downstream maturin projects.
Sorry for the noise.
@andygrove, the commit that changes lib.name
is not in this PR. It's in a different branch of my fork.
I created my own noise be referencing the suggestion in this PR in that commit message.
Looks like you figured this out already, but yes I agree no need to change lib.name
here 👍
Supersedes https://github.com/apache/datafusion-python/pull/694
Rationale for this change
The previous layout leads to an import error when installing with
maturin build
andpip install .
.This error was common enough that
maturin
changed the recommended project layout to what this commit does.A prior PR attempted to solve this by altering
lib.name
in Cargo.toml, but that did not work for me.Maintainer of
pyo3
explains the issue on the prior PR