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

Deprecate the backend.qt{4,5} rcParams.#10282

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

Merged

Conversation

anntzer
Copy link
Contributor

@anntzeranntzer commentedJan 22, 2018
edited
Loading

  1. For the rcParams rewrite (MEP32), they may make it tricky to
    transform rcParams into a nested dictionary type of object, as "backend"
    is already the name of another (more important) rcParam.
    (I haven't decided on a nested dict design yet, just keeping options open.)
    This specific issue could be solved with deprecation + renaming, but also...

  2. The use of these rcParams can easily be replaced by a) first
    importing one of the bindings (qt_compat will ensure that the already
    imported binding gets used, as importing multiple bindings in the same
    process is a bad idea anyways), or b) setting the QT_API environment
    variable appropriately.

Milestoning as 2.2 so that the rcparams may actually get removed when (if) MEP32 makes it in 3.0, but feel free to push back too.

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

@anntzeranntzer added this to thev2.2 milestoneJan 22, 2018
1) For the rcParams rewrite (MEP32), they may make it tricky totransform rcParams into a nested dictionary type of object, as "backend"is already the name of another (more important) rcParam.  This specificissue could be solved with deprecation + renaming, but also...2) The use of these rcParams can easily be replaced by a) firstimporting one of the bindings (qt_compat will ensure that the alreadyimported binding gets used, as importing multiple bindings in the sameprocess is a bad idea anyways), or b) setting the QT_API environmentvariable appropriately.
@jklymakjklymak added the Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. labelJan 24, 2018
@jklymak
Copy link
Member

So, is an alternative to make new rcParams that do the same thing? I don't use these rcParams, but maybe some people do. I'm not sure about the goal here other than an rcParams namespace issue?

@anntzer
Copy link
ContributorAuthor

Renaming would be the other option, but again I think QT_API or preimporting either module is good enough. Of course, we'll see how much pushback we get after releasing this...

Copy link
Member

@jklymakjklymak left a comment

Choose a reason for hiding this comment

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

I'm fine w/ this, but maybe there is a large audience who uses these rcParams...

@tacaswelltacaswell merged commit090e9f1 intomatplotlib:masterJan 29, 2018
@anntzeranntzer deleted the deprecate-backend-qt45 branchJanuary 29, 2018 21:05
@jklymak
Copy link
Member

OK, maybe I made a mistake approving this.

On master, with no matplotlibrc file (i.e. using the defaults), I get both these deprecation warnings, which is super annoying.

I think somehow if the user doesnot specify these parameters, they should not still get a warning!

@jklymakjklymak mentioned this pull requestJan 30, 2018
6 tasks
@QuLogicQuLogic modified the milestones:needs sorting,v2.2.0Feb 12, 2018
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@tacaswelltacaswelltacaswell approved these changes

@jklymakjklymakjklymak approved these changes

Assignees
No one assigned
Labels
Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Milestone
v2.2.0
Development

Successfully merging this pull request may close these issues.

4 participants
@anntzer@jklymak@tacaswell@QuLogic

[8]ページ先頭

©2009-2025 Movatter.jp