Skip to content
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

TST: move conftest.py to top-level #15731

Merged
merged 1 commit into from
Mar 18, 2017
Merged

Conversation

jreback
Copy link
Contributor

@jreback jreback commented Mar 18, 2017

xref #15341

@jreback jreback added the Testing pandas testing functions or related to the test suite label Mar 18, 2017
@jreback jreback added this to the 0.20.0 milestone Mar 18, 2017
@TomAugspurger TomAugspurger mentioned this pull request Mar 18, 2017
17 tasks
@jreback jreback merged commit 6a52c15 into pandas-dev:master Mar 18, 2017
jreback added a commit that referenced this pull request Mar 18, 2017
@jorisvandenbossche
Copy link
Member

@jreback The concerns of before regarding pd.test() (the reason conftest.py was not in the top level), are those solved / not needed anymore ?

@jreback
Copy link
Contributor Author

jreback commented Mar 20, 2017

@jorisvandenbossche so the issue was that when installed, if conftest.py is at the top-level (and not below pandas), then its not installed; this can be resolved by by actually including it as a data file in setup.py, but then need to have to explicity tell pytest . This only matters for pandas.test(); so we could explicity path it in there.

But this is just simpler. In any even I made the BUILD_TEST build now run pandas.test() so this is tested anyhow.

@jreback
Copy link
Contributor Author

jreback commented Mar 20, 2017

FYI I reverted my original commit: 59b88ab

@jorisvandenbossche
Copy link
Member

For what reason did you revert?

Personally, it doesn't really matter to me where conftest.py goes. It is just a choice when putting it top-level that pd.test() cannot specify the custom markers. Which is not the biggest problem I think. But I also don't mind it being inside pandas (it is not visible to users, so not really a problem)

@jreback
Copy link
Contributor Author

jreback commented Mar 20, 2017

@jorisvandenbossche well, it IS a problem in that in reality conftest.py will have more and more things. This is a central repository for fixtures and such. If pandas had been built from the ground up with pytest, we would have a whole set of conftest.py. So its not a problem per-se, just not very clean (and not very typical).

@jorisvandenbossche
Copy link
Member

OK, so we agree to just keep it in pandas?
That was not fully clear to me that you were OK with that, so that was the only reason of my question above!

@jreback
Copy link
Contributor Author

jreback commented Mar 21, 2017

yeah not sure what to do with it really.

AnkurDedania pushed a commit to AnkurDedania/pandas that referenced this pull request Mar 21, 2017
AnkurDedania pushed a commit to AnkurDedania/pandas that referenced this pull request Mar 21, 2017
mattip pushed a commit to mattip/pandas that referenced this pull request Apr 3, 2017
mattip pushed a commit to mattip/pandas that referenced this pull request Apr 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Testing pandas testing functions or related to the test suite
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants