automatic type tagging from PyCall #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jverzani
added a commit
that referenced
this pull request
Jun 11, 2013
automatic type tagging from PyCall
Collaborator
|
Thanks for this! Sorry it took so long, somehow I missed an email about it. |
Contributor
Author
|
I had assumed you were just waiting for the merge into PyCall of the corresponding functions :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements automatic tagging of SymPy types. It depends upon my pull request to PyCall JuliaPy/PyCall.jl#20 so it won't work right now without that.