Skip to content

Add @ operator, no coersion #21

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 3 commits into from

Conversation

DavidMertz
Copy link

This replaces #16. I did not have the git-fu to prune the commit history under my fork's master. This has the same changes, but in a new branch that is rebased with cleaner commits.

David Mertz added 3 commits May 9, 2017 12:30
# This is the 1st commit message:
# This is a combination of 2 commits.
# This is the 1st commit message:

# This is a combination of 5 commits.
# This is the 1st commit message:
# This is a combination of 3 commits.
# This is the 1st commit message:
# This is a combination of 3 commits.
# This is the 1st commit message:
# This is a combination of 3 commits.
# This is the 1st commit message:
# This is a combination of 4 commits.
# This is the 1st commit message:
Add @ operator (__matmul__ and __rmatmul__) and tests.  Do not implem ent coersion of Python lists/tuples.

# This is the commit message pydata#2:

test for __rmatmul__

# This is the commit message pydata#3:

Better implementation of __rmatmul__ and test that exercises the actual code, not NumPy's

# The commit message pydata#4 will be skipped:

#	Cleanup tests of coersion failure

# The commit message pydata#2 will be skipped:

#	# This is a combination of 2 commits.
#	# This is the 1st commit message:
#
#	Resolve merge conflict in rebasing
#
#	# The commit message pydata#2 will be skipped:
#
#	#	test for __rmatmul__

# The commit message pydata#3 will be skipped:

#	Resolve merge conflict in rebasing

# The commit message pydata#2 will be skipped:

#	test for __rmatmul__

# The commit message pydata#3 will be skipped:

#	Better implementation of __rmatmul__ and test that exercises the actual code, not NumPy's

# This is the commit message pydata#2:

Remove handling of lists etc.

# The commit message pydata#3 will be skipped:

#	Remove handling of lists etc.

# The commit message pydata#2 will be skipped:

#	# This is a combination of 3 commits.
#	# This is the 1st commit message:
#	# This is a combination of 2 commits.
#	# This is the 1st commit message:
#
#	# This is a combination of 2 commits.
#	# This is the 1st commit message:
#
#	Resolve merge on rebase
#
#	# The commit message pydata#2 will be skipped:
#
#	#	Resolve merge on rebase
#
#	# The commit message pydata#2 will be skipped:
#
#	#	Better implementation of __rmatmul__ and test that exercises the actual code, not NumPy's
#
#	# The commit message pydata#2 will be skipped:
#
#	#	Remove handling of lists etc.
#
#	# The commit message pydata#3 will be skipped:
#
#	#	Remove handling of lists etc.

# The commit message pydata#3 will be skipped:

#	Resolve merge on rebase

# The commit message pydata#4 will be skipped:

#	Resolve merge on rebase

# The commit message pydata#5 will be skipped:

#	Resolve merge on rebase

# The commit message pydata#2 will be skipped:

#	Better implementation of __rmatmul__ and test that exercises the actual code, not NumPy's

# The commit message pydata#2 will be skipped:

#	Remove handling of lists etc.

# The commit message pydata#3 will be skipped:

#	Remove handling of lists etc.
…atmul__) and tests. Do not implem ent coersion of Python lists/tuples.
@DavidMertz
Copy link
Author

Oh well... looks like @jakevdp merged the branch with the messier commit history while I was learning the maddening mysteries of git rebase -i (which is great except when it fails to merge a bunch of the commits).

I think if you apply this it will still clean the commit history (but should otherwise be identical code changes). But I am way less than confident in my understanding of git, so use your judgement.

@jakevdp
Copy link
Contributor

jakevdp commented May 9, 2017

Oh, sorry about that. I did a squash and merge on the other one so it's just a single commit. FWIW, for doing this kind of cleaning of commit history, I tend to use git reset --soft and then re-commit the changes manually. Thanks!

@jakevdp jakevdp closed this May 9, 2017
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