Skip to content

Fix void dtype handling #61637

New issue

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

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

Already on GitHub? # to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

flying-sheep
Copy link
Contributor

@flying-sheep
Copy link
Contributor Author

which doc/source/whatsnew/vX.X.X.rst am I supposed to edit?

@@ -0,0 +1,174 @@
from __future__ import annotations

from collections.abc import (
Copy link
Member

Choose a reason for hiding this comment

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

Can you write a simpler targeted test?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

What should be removed? I want to test that an ExtensionArray based on a void dtype can be put into a Series, that needs quite a few interplaying parts

Copy link
Member

Choose a reason for hiding this comment

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

would passing the numpy v16 array directly do it?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: Series constructor incorrectly assumes that any dtype with .kind == 'V...' is a “compound dtype”
2 participants