Skip to content

Make py_class!'s generated type public #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 7 commits into from

Conversation

ihrwein
Copy link
Contributor

@ihrwein ihrwein commented Jul 22, 2016

This PR contains the following changes:

  • make the type generated by py_class! public
  • replace ExtractPyObject with FromPyObject in the documentation

Tibor Benke added 6 commits July 21, 2016 16:15
struct DataIsDropped is public, so all of its fields needs to be public
as well.

Signed-off-by: Tibor Benke <[email protected]>
Signed-off-by: Tibor Benke <[email protected]>
@ihrwein
Copy link
Contributor Author

ihrwein commented Jul 22, 2016

I investigated the failing testcase and it seems like str(CustomError) produces mymodule.CustomErrrorCustomError on nightly Rust.

Update:
It seems like there is a regression in the nightly compilers. The first faulty compiler is nightly-2016-07-09 (this means the bug is between 2ad5ed07f and 5e18b4bad). I would report this as a bug, but I couldn't write a minimal testcase without cpython.

It was an FFI bug :)

Use null-terminated strings to call PyErr_NewException()

Signed-off-by: Tibor Benke <[email protected]>
@dgrunwald
Copy link
Owner

I don't think extension types should be public by default. See #46.

I've cherry-picked the PyErr_NewException bugfix; thanks!

@dgrunwald dgrunwald closed this Jul 28, 2016
@ihrwein
Copy link
Contributor Author

ihrwein commented Jul 28, 2016

Ok, thanks!

Could you cherry-pick the documentation related fixes as well?

And another question: what do you think, when will cpython 0.6 be ready?

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.

2 participants