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

Simpler check for whether a Framework Python build is being used.#11851

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 merge1 commit intomatplotlib:masterfromanntzer:frameworkcheck

Conversation

anntzer
Copy link
Contributor

This check works even before an NSApp is started.

Simpler alternative to#11850. Basically the first stackoverflow answer for the question (https://stackoverflow.com/questions/15752390/how-to-tell-if-python-instance-was-compiled-as-framework), from a CPython core dev.

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

This check works even before an NSApp is started.
@anntzeranntzer added Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. GUI: MacOSX labelsAug 13, 2018
@anntzeranntzer added this to thev3.0 milestoneAug 13, 2018
@jklymak
Copy link
Member

Unfortunately, this doesnt' work w/ my Anacondapythonw. That config variable is not set even if I usepythonw...

@anntzer
Copy link
ContributorAuthor

Looks like@efiring knows something about this perhttp://matplotlib.1069221.n5.nabble.com/Re-Anaconda-Support-OSX-why-not-make-python-invoke-the-framework-tp43793p43806.html :)
(and that anaconda's pythonw is not a real framework build but manually emulates one, whatever that means...)
Oh well.

jklymak reacted with thumbs up emoji

@jklymak
Copy link
Member

Yeah, I guess anaconda does something funky. OTOH, I shudder to think what installing the framework build w/o anaconda would be like...

@anntzer
Copy link
ContributorAuthor

Isn't that just (for example) python.org's python? Anyways, the discussion is not very relevant, we're stuck with whatever anaconda did and#11850 seems better unless Apple plans to actually remove their deprecated features :p

@tacaswelltacaswell modified the milestones:v3.0,v3.1Aug 19, 2018
@tacaswell
Copy link
Member

Moving this to 3.1 as I just merged#11850. I think this is inline with@anntzer 's last comment.

anntzer reacted with thumbs up emoji

@tacaswelltacaswell removed the Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. labelAug 19, 2018
@jklymak
Copy link
Member

Closing this, as this approach won't work unfortunately...

@anntzeranntzer deleted the frameworkcheck branchNovember 12, 2018 20:01
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
v3.1.0
Development

Successfully merging this pull request may close these issues.

3 participants
@anntzer@jklymak@tacaswell
[8]ページ先頭
©2009-2025 Movatter.jp