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.

Sign up for GitHub

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

Jump to bottom

Importing mantid into wrong python shouldn't segfault #2439

Closed
peterfpeterson opened this issue Sep 1, 2010 · 1 comment
Closed

Importing mantid into wrong python shouldn't segfault #2439

peterfpeterson opened this issue Sep 1, 2010 · 1 comment
Assignees
@martyngigg
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Maintenance Unassigned issues to be addressed in the next maintenance period.
Milestone
Release 2.6

Comments

@peterfpeterson
Copy link
Member

On SNS analysis computers more than one python is installed. It is quite easy to start the python that mantid wasn't compiled against and segfault during from MantidFramework import mtd. Try to print an error message before breaking.

Keywords: Maintenance
@peterfpeterson
Copy link
Member Author

This issue was originally trac ticket 1592

@peterfpeterson peterfpeterson added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Python Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@peterfpeterson peterfpeterson added this to the Release 2.6 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martyngigg martyngigg

Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
None yet
Milestone
Release 2.6
Development

No branches or pull requests
2 participants
@peterfpeterson @martyngigg