Skip to content
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

Should named tuple be serialized as tuple or like dict #21

Closed
cypreess opened this issue Mar 13, 2019 · 4 comments
Closed

Should named tuple be serialized as tuple or like dict #21

cypreess opened this issue Mar 13, 2019 · 4 comments
Labels
feature A new feature that awaits implementation

Comments

@cypreess
Copy link

Similarly to #18 I start being biased towards thinking that because of "readability counts" NamedTuples should be expressed like to dicts. The whole point of naming tuple positions is because of poor readability of tuples. Then we totally drop it on serialization level when we already decided we go for readability.

@cypreess cypreess changed the title Should named tuple be serialized as tuple or dict Should named tuple be serialized as tuple or like dict Mar 13, 2019
@ramonhagenaars
Copy link
Owner

Good point. As for deserialization, both arrays and dicts should be deserializable to a namedtuple.

@ramonhagenaars ramonhagenaars added the feature A new feature that awaits implementation label Mar 14, 2019
@cypreess
Copy link
Author

When could we expect this feature to be implemented?

@ramonhagenaars
Copy link
Owner

This will be the next minor update, so 0.8.2. Expect it anytime soon. :-)

@ramonhagenaars ramonhagenaars added the in progress This issue is worked on label Mar 24, 2019
@ramonhagenaars
Copy link
Owner

This issue has been solved in 0.8.2.

@ramonhagenaars ramonhagenaars removed the in progress This issue is worked on label Apr 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature that awaits implementation
Projects
None yet
Development

No branches or pull requests

2 participants