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

Warning if __new__ implicitly casts to DynamicMap #4301

Merged
merged 6 commits into from Mar 18, 2020

Conversation

jlstevens
Copy link
Contributor

This PR implements the warning discussed with @jbednar and @philippjfr. The idea is to make the intuitive thing work while alerting the user that some magic is happening in the background. In a sense, this functionality is very similar to how we approach .collate.

image

Currently work in progress: we can discuss how to improve the warning message and I will format better suggestions for using .apply when kdims, vdims and kwargs are not empty.

@jlstevens jlstevens changed the title Warning when __new__ used to implicitly cast to DynamicMap Warning when __new__ implicitly casts to DynamicMap Mar 18, 2020
@jlstevens jlstevens changed the title Warning when __new__ implicitly casts to DynamicMap Warning if __new__ implicitly casts to DynamicMap Mar 18, 2020
@jlstevens
Copy link
Contributor Author

@philippjfr @jbednar Ready to review and maybe merge once the tests go green.

Co-Authored-By: Philipp Rudiger <prudiger@anaconda.com>
@jlstevens
Copy link
Contributor Author

Second PR build is about to pass and all the other tests are green. Merging.

@jlstevens jlstevens merged commit 69e931a into master Mar 18, 2020
@philippjfr philippjfr deleted the new_dmap_cast_warning branch April 25, 2022 14:41
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.

None yet

3 participants