charlesbluca commented on issue #701: URL: https://github.com/apache/datafusion-python/issues/701#issuecomment-2163408725
> Does conda-forge pull from main? Or do we need a new release to test if that fix solves the issue? conda-forge pulls the sdist for a versioned release from PyPI, but I don't actually think the maturin constraint contained in this code forces us to that maturin version; for example, in https://github.com/conda-forge/datafusion-feedstock/pull/44, we are rebuilding using the 34.0.0 source code, which constrains `maturin>=0.15,<0.16`, we are still able to pull a newer maturin version and build successfully with it. In short, I think we should be safe to move to the updated constraint in #725 to unblock some of the older conda-forge that have been blocked: - https://github.com/conda-forge/datafusion-feedstock/pull/43 - https://github.com/conda-forge/datafusion-feedstock/pull/44 - https://github.com/conda-forge/datafusion-feedstock/pull/45 - https://github.com/conda-forge/datafusion-feedstock/pull/46 - https://github.com/conda-forge/datafusion-feedstock/pull/47 - https://github.com/conda-forge/datafusion-feedstock/pull/48 And then continue using this updated constraint for future conda-forge builds moving forward. As a side note, not sure if you're interested in being a maintainer of the linked feedstock? This would give you write access to the repo as well as notifications of these past build attempts. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
