Remove setup.py tests and adapt docs to use tests.py

[jenshnielsen]

Given the number of issues that we have been seeing with setup.py test
#4720 and #5315 among others I suggest removing it and recommending python tests.py

We already have 2/3 other ways of running the tests and the only thing that setup.py test brings is the ability to install the test dependencies which is done inside the build enviroment with setuptools only available to the test process. I think it is better just to recommend manually installing the test dependencies.

[jenshnielsen]

Related to #5428 and may conflict with #5325

[tacaswell]

👍 in principle but want to be careful to not conflict with #5405 too badly.

@pizzathief Your branch needs a resbase anyway. How much of a hassle would it be for us to merge this as-is and than have you re-base on top of the new master?

[jenshnielsen]

Im ok with rebasing this if need be. I think we should change the docs as soon as possible for the next release. Actually removing the method can better wait

[tacaswell]

Actually, could you split this up in to a documentation only commit? That
the docs say to use setup.py test as the primary method of testing is a
mistake on my part, i thought we had reverted ask of those.

I am +1 on merging the docs and rebuilding what we have deployed for 1.5

On Wed, Nov 11, 2015, 08:25 Jens Hedegaard Nielsen notifications@github.com
wrote:

Im ok with rebasing this if need be. I think we should change the docs as
soon as possible for the next release. Actually removing the method can
better wait

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

[jenshnielsen]

I will cherry-pick to a new branch with the docs changes only and target the 1.5 docs branch

[pizzathief]

reasonably hassle free, I think.

[tacaswell]

@jenshnielsen What is the state of this PR? I think this needs to be re-bassed because the docs only PR was merged.

[jenshnielsen]

@tacaswell Yes you are right. Rebase done

[tacaswell]

@mdboom any problem porting this all they way back to v1.5.0-doc?

[jenshnielsen]

The docs part was merged in #5462 so I guess that this can just be backported to 1.5.x ?

[tacaswell]

Great, thanks for remembering that.

[tacaswell]

backported to v1.5.x as 4a705d1