to_gbq doesn't respect location argument when it also creates dataset

[robertlacok]

When trying to use the to_gbq method to both create dataset and the table, the method fails when setting the location other than US.

The reason is that the location is not respected when creating dataset, so it defaults to US. However, trying to launch a LoadJob with location='EU' when the dataset is in the US leads to failure.

Steps to reproduce:

to_gbq(df, 'my_dataset.my_table', google_cloud_project, location='EU')

where my_dataset doesn't exist.

I can try fixing it by passing the location argument down to constructors of _Table and _Dataset, and then here in the create method of _Dataset doing something like:

if self.location is not None:
    dataset.location = self.location

If you OK it I will test and submit a PR. Is there a better way?

[max-sixty]

Thanks for the report and diagnosis @robertlacok

@tswast - what do you think about a) a function arg b) part of the config c) part of the class you recently added?

[tswast]

We've already got the function argument for location 😄 (added in #177). I think it's more a matter of plumbing it through to the dataset object.

@robertlacok Yes, PRs welcome!