Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Make CI fail if interactive toolkits can't be tested#11497

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
anntzer wants to merge3 commits intomatplotlib:masterfromanntzer:pinpyqt

Conversation

anntzer
Copy link
Contributor

@anntzeranntzer commentedJun 24, 2018
edited
Loading

PyQt5.11 appears to break the build (I can reproduce the failure
locally).

Also make it a failure to fail to install the GUI toolkits for testing,
to avoid missing new failures there.

Also supersedes#11494.

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is PEP 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

.travis.yml Outdated
python -mpip install --upgrade $PRE pgi
python -c 'import pgi as gi; gi.require_version("Gtk", "3.0"); from pgi.repository import Gtk'
fi
python -c 'import PyQt5.QtCore'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

These still need theecho bit to make sure the build doesn't fail if they aren't importable.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Actually the point is exactly to fail when they are not importable, instead of having to figure this out manually every time this happens.

@QuLogic
Copy link
Member

I have a hack solution to fix PyQt5 5.11 here, but I need to turn it into something reasonable.

@QuLogic
Copy link
Member

See#11500.

@anntzer
Copy link
ContributorAuthor

PyQt5.11 has been withdrawn (https://riverbankcomputing.com/pipermail/pyqt/2018-June/040459.html), so I repurposed the PR to just move GUI deps to requirement files too and fail the CI when they fail to install properly.

@anntzer
Copy link
ContributorAuthor

So it appears that the interactive tests are failing with wx+OSX. Any OSX specialist wants to have a look at this (can you repro locally?), or should we just skip them?

@tacaswelltacaswell added this to thev3.0 milestoneJul 1, 2018
@jklymak
Copy link
Member

I'm a little confused where we stand here. Right nownone of the Travis CI tests are passing because of QT5 issues. Is this fix, correct, or#11500? or are they complimentary?

@anntzeranntzer changed the titlePin PyQt5 to <5.10.Make CI fail if interactive toolkits can't be testedJul 3, 2018
@anntzer
Copy link
ContributorAuthor

See#11500 (comment); as for this PR the scope has changed and I renamed it accordingly.

# pgi is only installable on Linux
pyqt5
# wxpython 4.0.2 is broken on OSX, see https://groups.google.com/forum/#!topic/wxpython-dev/lNvdniiXhdY
wxpython!=4.0.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Looks like 4.0.3 is also failing now?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

let's try excluding it too...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Fails to build faster! Actually I'm not clear why the mac build is trying to use 3.7....

Also make it a failure to fail to install the GUI toolkits for testing,to avoid missing new failures there.
@jklymak
Copy link
Member

Force-pushed a change to pin python to 3.6 for OS X. It was trying to use 3.7.

@jklymak
Copy link
Member

Well, that didn't work either. Sorry, you should revert my commits...

@anntzer
Copy link
ContributorAuthor

but now it's failing on something different (pyqt5). I'll try something later.

@jklymak
Copy link
Member

This looks to be broken, but feel free to re-open if I'm wrong...

@jklymakjklymak closed thisFeb 9, 2019
@anntzer
Copy link
ContributorAuthor

I think some variant of this PR should still go in, but let's do thisafter the current qt breakage is fixed :)

@anntzeranntzer deleted the pinpyqt branchFebruary 11, 2019 06:35
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@jklymakjklymakjklymak left review comments

@dstansbydstansbydstansby requested changes

Assignees
No one assigned
Projects
None yet
Milestone
v3.1.0
Development

Successfully merging this pull request may close these issues.

5 participants
@anntzer@QuLogic@jklymak@dstansby@tacaswell

[8]ページ先頭

©2009-2025 Movatter.jp