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

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

Merged
merged 3 commits into from Dec 15, 2015

Conversation

jenshnielsen
Copy link
Member

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
Copy link
Member Author

Related to #5428 and may conflict with #5325

@tacaswell
Copy link
Member

👍 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
Copy link
Member Author

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
Copy link
Member

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
Copy link
Member Author

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

@pizzathief
Copy link
Contributor

reasonably hassle free, I think.

@tacaswell
Copy link
Member

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

@jenshnielsen
Copy link
Member Author

@tacaswell Yes you are right. Rebase done

tacaswell added a commit that referenced this pull request Dec 15, 2015
Remove setup.py tests and adapt docs to use tests.py
@tacaswell tacaswell merged commit e789a70 into matplotlib:master Dec 15, 2015
@tacaswell
Copy link
Member

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

@jenshnielsen
Copy link
Member Author

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

@tacaswell
Copy link
Member

Great, thanks for remembering that.

tacaswell added a commit that referenced this pull request Dec 15, 2015
Remove setup.py tests and adapt docs to use tests.py

conflicts in setup.py due to parts of #5604 being back-ported
as well.  Removed the windows bdist patch code to resolve.
@tacaswell
Copy link
Member

backported to v1.5.x as 4a705d1

@QuLogic QuLogic added this to the Critical bugfix release (1.5.1) milestone Dec 15, 2015
@jenshnielsen jenshnielsen deleted the nosetuptest branch January 5, 2016 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants