Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Pandas apply on either axis #366

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.

Sign up for GitHub

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

Jump to bottom
Closed
interrogator wants to merge 2 commits into from
Closed

Pandas apply on either axis #366

interrogator wants to merge 2 commits into from

Conversation

@interrogator
Copy link

@interrogator interrogator commented Apr 4, 2017 •
edited by casperdcl
Loading

Summary fortox --skip-missing-interpreters:

SKIPPED:  py32: InterpreterNotFound: python3.2
SKIPPED:  py33: InterpreterNotFound: python3.3
SKIPPED:  py34: InterpreterNotFound: python3.4
  py26: commands succeeded
  py27: commands succeeded
  py35: commands succeeded
  py36: commands succeeded
SKIPPED:  pypy: InterpreterNotFound: pypy
SKIPPED:  pypy3: InterpreterNotFound: pypy3
  pypy3.3-5.2-alpha1: commands succeeded
  flake8: commands succeeded
ERROR:   setup.py: commands failed
  perf: commands succeeded

@casperdcl
Copy link
Member

casperdcl commented May 1, 2017 •
edited
Loading

Thanks, but I think this PR may be broken since you use the axis as a bool and discard its value. Might just merge in #299 today as nobody's objected to it yet.

@casperdcl casperdcl closed this May 1, 2017
@casperdcl casperdcl added the duplicate 🗐 Seen it before label May 1, 2017
@interrogator
Copy link
Author

interrogator commented May 19, 2017

axis isn't discarded, it's passed to apply, but used en route to calculate the correct number of iterations. So, I don't really get what you mean.

Anyway, this fix is also in #299, pretty much the same implementation, but it never got merged and now has conflicts. What's the plan?

@casperdcl
Copy link
Member

casperdcl commented May 19, 2017

Hi @interrogator, we want to merge in #299 asap but just need someone to fix the unit test failures.

@casperdcl
Copy link
Member

casperdcl commented Apr 3, 2018

fixed in #524

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

duplicate 🗐 Seen it before

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@interrogator @casperdcl