Open reaperhulk opened 1 year ago
Sorry for the extremely slow reply @reaperhulk. Did you find any answer to this? It's not a problem that I've observed, however if there's new checks in setuptools which can fail when using setuptools-rust
it sounds like something which needs further investigation.
I don't think we ever got to the bottom of this, still a big question mark.
(As an aside, we're now looking at migrating to maturin, so this may become irrelevant for us.)
On Wed, Apr 26, 2023, 4:40 PM David Hewitt @.***> wrote:
Sorry for the extremely slow reply @reaperhulk https://github.com/reaperhulk. Did you find any answer to this? It's not a problem that I've observed, however if there's new checks in setuptools which can fail when using setuptools-rust it sounds like something which needs further investigation.
— Reply to this email directly, view it on GitHub https://github.com/PyO3/setuptools-rust/issues/313#issuecomment-1524017264, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAGBGUR6ZSL7VGHR2NBRDXDGB2PANCNFSM6AAAAAAUZMU7PM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
In which case I'll wait to see if any other users are noticing this and can provide a minimal repro. It doesn't look like this is blocking anyone at present, and my time is stretched very thin recently.
I spent some time investigating this a few months ago and it appeared at the time that there might not be a non-deprecated path available. I haven’t had a chance to follow up.
In
cryptography
builds we have been getting this deprecation warning for a while:We declare
cryptography.hazmat.bindings._rust
as the target in ourRustExtension
call and then use the standardfind:
mechanisms in our setup.cfg. Is there somethingsetuptools-rust
needs to tellsetuptools
so that it auto-discovers this package without this warning? Or, quite possibly, something we need to do on our end because we've done something dumb? 😄