Skip to content

Refs BUG-9099: Support simultaneous copy and dtype args in DataFrame init #9105

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

Merged
merged 1 commit into from
Dec 20, 2014

Conversation

mairas
Copy link

@mairas mairas commented Dec 18, 2014

closes #9099
This is a somewhat brute-force fix for supporting copy and dtype arguments in DataFrame constructor. Some data might be copied twice if both arguments are set, but if I did the operations in a different order, one other unit test would fail.

@jreback
Copy link
Contributor

jreback commented Dec 18, 2014

perfect pls add a release note in v0.16.0 in bug fix section

@mairas
Copy link
Author

mairas commented Dec 19, 2014

OK, this time I actually read the contribution guidelines. ;-)

Added the info, new pull request:

#9105

ma.

On Thu Dec 18 2014 at 4:43:29 PM jreback [email protected] wrote:

perfect pls add a release note in v0.16.0 in bug fix section


Reply to this email directly or view it on GitHub
#9105 (comment).

@shoyer shoyer added this to the 0.16.0 milestone Dec 20, 2014
@jreback jreback added API Design Compat pandas objects compatability with Numpy or Python functions Bug and removed API Design labels Dec 20, 2014
@jreback jreback merged commit 5cf4f02 into pandas-dev:master Dec 20, 2014
@jreback
Copy link
Contributor

jreback commented Dec 20, 2014

@mairas thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Compat pandas objects compatability with Numpy or Python functions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: DataFrame constructor ignores copy=True argument if dtype is set
3 participants