Skip to content

Conversation

@mesejo
Copy link
Contributor

@mesejo mesejo commented Sep 10, 2024

Which issue does this PR close?

Closes #809.

Are there any user-facing changes?

Yes

expr.into()
}

#[pyo3(signature = (low, high, negated=false))]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the introduction of the python wrappers, we've been preferring to avoid #[pyo3(signature = ...)] annotations for simple defaults and let the python wrappers handle them.

(I see that I left that out of the guidelines, I'll throw a quick PR for that.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI for optionals we might have to have these signatures in when we upgrade to pyo3 0.22. It's part of the DF42 update PR that's up

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, do you folks think I should remove it?

Copy link
Contributor

@emgeee emgeee Sep 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be kept in as we'll have to add it anyways once the pyo3 0.22 upgrade hits #867

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, leave it in for now.

@timsaucer timsaucer merged commit 02d4453 into apache:main Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose between

4 participants