Ivan “CLOVIS” Canet

If you want to go to low barrier of entry but with a little bit of manual work, here's what I do in other projects: - Add the changelog sections...

Current state of this prototype: - First and foremost, I've been figuring out what needs to be done as I go from one thing to the next, so the commit...

Hi @davidhewitt! I opened #2454 to discuss the various ideas of this prototype. I think it's is good enough to show what the steps needed are, but it's far from...

> Merging PR should preferably now squash commits into a single commit. I'm not a PyO3 maintainer, so the decision is ultimately up to them, but as a user that...

@davidhewitt don't worry about the full review for now, it's just a prototype. If you have time, please just read this issue and give me your general feedback on the...

I was thinking of feature-gating the macro generation but not the inspection API itself (so you would be able to construct inspection APIs yourself in all cases, but would need...

It seems like #2490 will be merged soon. I won't have a lot of time on my hands in the close future, so if someone else wants to help in...

Currently stuck on the same thing (https://github.com/PyO3/pyo3/discussions/2294). What is the correct way to create a Python instance of a class with inheritance then? Or can they only be instantiated from...

For multiple reasons, using .pyi files is inconvenient for me at the moment (`help(foo)` ignores them, it's in a different place from the code so no one updates them, etc)....

Ah, I see. Would it be possible to integrate such a tool with PyO3 so it can take advantage of the information PyO3 already possesses? (e.g. as an optional cargo...