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

$HOME/.matplotlib conflicts (Trac #498) #631

Closed
pkienzle opened this issue Mar 30, 2019 · 3 comments
Closed

$HOME/.matplotlib conflicts (Trac #498) #631

pkienzle opened this issue Mar 30, 2019 · 3 comments
Assignees
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Milestone

Comments

@pkienzle
Copy link
Contributor

pkienzle commented Mar 30, 2019

Matplotlib's configuration file conflicts can cause exceptions to be thrown on application startup which are not captured in sasview.log.

Within sasview.py we need a try/catch block around the import statements so that we can catch exceptions and output them to sasview.log.

We need to set the MPLCONFIGDIR to a sasview specific directory to avoid conflicts with other versions of python installed on the system. This directory needs to be removed as part of the uninstall process so we don't conflict with older versions of sasview. Alternatively, put the sasview install in a directory tagged with version number so that we can have different versions installed at the same time.

Make sure the .matplotlib directory is located in a directory writable by the user; not all users have write access to Program Files.

Migrated from http://trac.sasview.org/ticket/498

{
    "status": "closed",
    "changetime": "2016-03-20T12:48:31",
    "_ts": "2016-03-20 12:48:31.591130+00:00",
    "description": "Matplotlib's configuration file conflicts can cause exceptions to be thrown on application startup which are not captured in sasview.log.\n\nWithin sasview.py we need a try/catch block around the import statements so that we can catch exceptions and output them to sasview.log.\n\nWe need to set the MPLCONFIGDIR to a sasview specific directory to avoid conflicts with other versions of python installed on the system.  This directory needs to be removed as part of the uninstall process so we don't conflict with older versions of sasview.  Alternatively, put the sasview install in a directory tagged with version number so that we can have different versions installed at the same time.\n\nMake sure the .matplotlib directory is located in a directory writable by the user; not all users have write access to Program Files.",
    "reporter": "pkienzle",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView Bug Fixing",
    "time": "2016-02-01T21:38:16",
    "component": "SasView",
    "summary": "$HOME/.matplotlib conflicts",
    "priority": "blocker",
    "keywords": "",
    "milestone": "SasView 4.0.0",
    "owner": "ajj",
    "type": "defect"
}
@pkienzle pkienzle added this to the SasView 4.0.0 milestone Mar 30, 2019
@pkienzle pkienzle added Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour Incomplete Migration and removed Incomplete Migration labels Mar 30, 2019
@ajj
Copy link
Member

ajj commented Mar 30, 2019

Trac update at 2016/02/28 11:23:06:

  • ajj changed owner from "" to "ajj"
  • ajj changed priority from "major" to "critical"
  • ajj changed status from "new" to "assigned"

@butlerpd
Copy link
Member

Trac update at 2016/03/19 12:25:09:

  • butler commented:

Andrew says this needs fixing for 4.0 or many things will break?

  • butler changed priority from "critical" to "blocker"

@ajj
Copy link
Member

ajj commented Mar 30, 2019

Trac update at 2016/03/20 12:48:31:

  • ajj commented:

sasview now uses .sasview/,matplotlib

  • ajj changed resolution from "" to "fixed"
  • ajj changed status from "assigned" to "closed"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Projects
None yet
Development

No branches or pull requests

3 participants