-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
WIP: Prepare _TimeViewer for next version of pyvista #7458
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
WIP: Prepare _TimeViewer for next version of pyvista #7458
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7458 +/- ##
==========================================
- Coverage 90.08% 85.69% -4.39%
==========================================
Files 454 454
Lines 82439 82609 +170
Branches 13028 13066 +38
==========================================
- Hits 74264 70792 -3472
- Misses 5352 9142 +3790
+ Partials 2823 2675 -148 |
|
Also the workaround for the scraper (#7416) is not necessary anymore in this PR and should be removed. |
|
Please do remove it here then |
|
All green here and no timeout, I'll proceed with doc building. |
|
Circle was successful too: https://18688-1301584-gh.circle-artifacts.com/0/dev/index.html |
|
This is ready when we need it @agramfort, @larsoner |
|
Tentatively marking for 0.20. It would be good if we could wait for their release, but let's see how long it takes them. In the meantime @GuillaumeFavelier you have conflicts |
|
@larsoner 0.24 is out since yesterday |
|
I'll fix the conflicts |
|
@GuillaumeFavelier should we merge then? |
|
After giving it more thought, I think it's better to wait for 0.21 except if we really need it for a specific reason before the release. The version 0.23.1 of pyvista has been tested extensively compared to the latest one. |
|
does it work fine for you? shall we try to test? we can have 3-4 people
testing quickly
… |
|
Testing is always welcome for |
|
Agreed we should probably wait until 0.21 to advertise PyVista stuff. Having an extra 6 months of testing during which core users/contributors/maintainers, some of whom have asked about 3D viz semi-recently (@bloyl, @drammock) start actually using it in scripts would be beneficial in finding bugs before we force less experienced users to do it. @GuillaumeFavelier are there |
|
AFAIK, the only entry about the new https://github.com/mne-tools/mne-python/blob/master/doc/changes/latest.inc#L130 |
|
I am a bit reluctant to wait to advertise pyvista. With 0.20 I would like
to have user feedback
and keep improving as bugs are reported. Users can still use mayavi if need
be. I don't think
we broke any mayavi code. So let's take the release opportunity to
advertise pyvista with nice
screenshots so we keep the ball rolling at a good speed.
my 2c
… |
|
Pushed an empty commit to get Circle to build the frontpage examples so we can at least see if one plot works |
|
Thanks @GuillaumeFavelier |
This PR is a draft to test the next version of pyvista.
pyvista 0.24It's an item of #7162