anaconda Qt vs system Qt The Next CEO of Stack OverflowGetting “Not found” message when running a 32-bit binary on a 64-bit systemError while loading shared librarieslxml with custom install location for libxml2/libxslt doesn't find correct locationChrooting any arbitrary program using dynamic linker?How to use libraries installed by nix at run-time?Change Environment Path Variable Orderdiscrepancy between path for binary and man pagePython sources compile a different versionInstalling Anaconda on Linux Mint without messing up preinstalled Python?Safely managing system/local/project Python packages?
Why were Madagascar and New Zealand discovered so late?
Horror movie/show or scene where a horse creature opens its mouth really wide and devours a man in a stables
Whats the best way to handle refactoring a big file?
How do I go from 300 unfinished/half written blog posts, to published posts?
Opposite of a diet
How easy is it to start Magic from scratch?
Robert Sheckley short story about vacation spots being overwhelmed
How to be diplomatic in refusing to write code that breaches the privacy of our users
How can I open an app using Terminal?
Should I tutor a student who I know has cheated on their homework?
How to write the block matrix in LaTex?
Unreliable Magic - Is it worth it?
How long to clear the 'suck zone' of a turbofan after start is initiated?
What does "Its cash flow is deeply negative" mean?
Was a professor correct to chastise me for writing "Prof. X" rather than "Professor X"?
How do I construct this japanese bowl?
How to make a variable always equal to the result of some calculations?
When airplanes disconnect from a tanker during air to air refueling, why do they bank so sharply to the right?
Which organization defines CJK Unified Ideographs?
If I blow insulation everywhere in my attic except the door trap, will heat escape through it?
Can the Reverse Gravity spell affect the Meteor Swarm spell?
How to get regions to plot as graphics
WOW air has ceased operation, can I get my tickets refunded?
Anatomically Correct Mesopelagic Aves
anaconda Qt vs system Qt
The Next CEO of Stack OverflowGetting “Not found” message when running a 32-bit binary on a 64-bit systemError while loading shared librarieslxml with custom install location for libxml2/libxslt doesn't find correct locationChrooting any arbitrary program using dynamic linker?How to use libraries installed by nix at run-time?Change Environment Path Variable Orderdiscrepancy between path for binary and man pagePython sources compile a different versionInstalling Anaconda on Linux Mint without messing up preinstalled Python?Safely managing system/local/project Python packages?
The anaconda python framework includes its own Qt shared libraries, among other ones. Because of the nature of the framework, it must appear first in the PATH
environment variable so its python binaries have preference over the system's ones.
This creates a conflict when one would like to use the system's Qt shared libraries for projects having nothing to do with python. When compiling a Qt project, it will use the qmake
binary from anaconda along with its shared libraries.
One can force to use the qmake
binary by prepending its path to the PATH
variable, but this doesn't work with the shared libraries. I tried changing the LD_LIBRARY_PATH
but it keeps choosing the anaconda ones.
"Solutions" I found:
LD_PRELOAD: Force the .so that uses the Qt shared libs to use the system ones by adding them one by one to the LD_PRELOAD env var. This ended up being tedious and time consuming.
Mess with Anaconda: Delete everything Qt related from anaconda as advised here. This seems too dirty and error prone in the future if one wants to develop GUI applications in python.
Anaconda Qt > System Qt: Use the anaconda Qt instead of the system Qt. This seems like a wrong assignment of responsibilities. My Qt project that has nothing to do with python should not be coupled to my anaconda install. They should be independent of one another.
Change modus operandi: Instead of all my shells having the anaconda path prepended to thePATH
variable, have an easily available script that prepends it whenever I need it, as advised here. The problems are that I'm used to having my python binaries always readily available and that it's prone to mistakes when I'm using the system's python binaries unknowingly.
Move anaconda: Temporarily moving the anaconda folder so it can't be found in the path. It's the quickest one but it relies too much on my memory to fix everything after I finish using the system Qt libraries.
Qt is not the only "not python" package included by anaconda by default, so any "real" solution a priori may be applied to any other conflicting ones.
python path dynamic-linking qt shared-library
add a comment |
The anaconda python framework includes its own Qt shared libraries, among other ones. Because of the nature of the framework, it must appear first in the PATH
environment variable so its python binaries have preference over the system's ones.
This creates a conflict when one would like to use the system's Qt shared libraries for projects having nothing to do with python. When compiling a Qt project, it will use the qmake
binary from anaconda along with its shared libraries.
One can force to use the qmake
binary by prepending its path to the PATH
variable, but this doesn't work with the shared libraries. I tried changing the LD_LIBRARY_PATH
but it keeps choosing the anaconda ones.
"Solutions" I found:
LD_PRELOAD: Force the .so that uses the Qt shared libs to use the system ones by adding them one by one to the LD_PRELOAD env var. This ended up being tedious and time consuming.
Mess with Anaconda: Delete everything Qt related from anaconda as advised here. This seems too dirty and error prone in the future if one wants to develop GUI applications in python.
Anaconda Qt > System Qt: Use the anaconda Qt instead of the system Qt. This seems like a wrong assignment of responsibilities. My Qt project that has nothing to do with python should not be coupled to my anaconda install. They should be independent of one another.
Change modus operandi: Instead of all my shells having the anaconda path prepended to thePATH
variable, have an easily available script that prepends it whenever I need it, as advised here. The problems are that I'm used to having my python binaries always readily available and that it's prone to mistakes when I'm using the system's python binaries unknowingly.
Move anaconda: Temporarily moving the anaconda folder so it can't be found in the path. It's the quickest one but it relies too much on my memory to fix everything after I finish using the system Qt libraries.
Qt is not the only "not python" package included by anaconda by default, so any "real" solution a priori may be applied to any other conflicting ones.
python path dynamic-linking qt shared-library
Did you executedldconfig
command after settingLD_LIBRARY_PATH
so the changes get applied? I always forget to do it.
– r1verside
Jan 5 '18 at 3:45
3
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47
add a comment |
The anaconda python framework includes its own Qt shared libraries, among other ones. Because of the nature of the framework, it must appear first in the PATH
environment variable so its python binaries have preference over the system's ones.
This creates a conflict when one would like to use the system's Qt shared libraries for projects having nothing to do with python. When compiling a Qt project, it will use the qmake
binary from anaconda along with its shared libraries.
One can force to use the qmake
binary by prepending its path to the PATH
variable, but this doesn't work with the shared libraries. I tried changing the LD_LIBRARY_PATH
but it keeps choosing the anaconda ones.
"Solutions" I found:
LD_PRELOAD: Force the .so that uses the Qt shared libs to use the system ones by adding them one by one to the LD_PRELOAD env var. This ended up being tedious and time consuming.
Mess with Anaconda: Delete everything Qt related from anaconda as advised here. This seems too dirty and error prone in the future if one wants to develop GUI applications in python.
Anaconda Qt > System Qt: Use the anaconda Qt instead of the system Qt. This seems like a wrong assignment of responsibilities. My Qt project that has nothing to do with python should not be coupled to my anaconda install. They should be independent of one another.
Change modus operandi: Instead of all my shells having the anaconda path prepended to thePATH
variable, have an easily available script that prepends it whenever I need it, as advised here. The problems are that I'm used to having my python binaries always readily available and that it's prone to mistakes when I'm using the system's python binaries unknowingly.
Move anaconda: Temporarily moving the anaconda folder so it can't be found in the path. It's the quickest one but it relies too much on my memory to fix everything after I finish using the system Qt libraries.
Qt is not the only "not python" package included by anaconda by default, so any "real" solution a priori may be applied to any other conflicting ones.
python path dynamic-linking qt shared-library
The anaconda python framework includes its own Qt shared libraries, among other ones. Because of the nature of the framework, it must appear first in the PATH
environment variable so its python binaries have preference over the system's ones.
This creates a conflict when one would like to use the system's Qt shared libraries for projects having nothing to do with python. When compiling a Qt project, it will use the qmake
binary from anaconda along with its shared libraries.
One can force to use the qmake
binary by prepending its path to the PATH
variable, but this doesn't work with the shared libraries. I tried changing the LD_LIBRARY_PATH
but it keeps choosing the anaconda ones.
"Solutions" I found:
LD_PRELOAD: Force the .so that uses the Qt shared libs to use the system ones by adding them one by one to the LD_PRELOAD env var. This ended up being tedious and time consuming.
Mess with Anaconda: Delete everything Qt related from anaconda as advised here. This seems too dirty and error prone in the future if one wants to develop GUI applications in python.
Anaconda Qt > System Qt: Use the anaconda Qt instead of the system Qt. This seems like a wrong assignment of responsibilities. My Qt project that has nothing to do with python should not be coupled to my anaconda install. They should be independent of one another.
Change modus operandi: Instead of all my shells having the anaconda path prepended to thePATH
variable, have an easily available script that prepends it whenever I need it, as advised here. The problems are that I'm used to having my python binaries always readily available and that it's prone to mistakes when I'm using the system's python binaries unknowingly.
Move anaconda: Temporarily moving the anaconda folder so it can't be found in the path. It's the quickest one but it relies too much on my memory to fix everything after I finish using the system Qt libraries.
Qt is not the only "not python" package included by anaconda by default, so any "real" solution a priori may be applied to any other conflicting ones.
python path dynamic-linking qt shared-library
python path dynamic-linking qt shared-library
asked Jan 5 '18 at 2:54
AlechanAlechan
212
212
Did you executedldconfig
command after settingLD_LIBRARY_PATH
so the changes get applied? I always forget to do it.
– r1verside
Jan 5 '18 at 3:45
3
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47
add a comment |
Did you executedldconfig
command after settingLD_LIBRARY_PATH
so the changes get applied? I always forget to do it.
– r1verside
Jan 5 '18 at 3:45
3
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47
Did you executed
ldconfig
command after setting LD_LIBRARY_PATH
so the changes get applied? I always forget to do it.– r1verside
Jan 5 '18 at 3:45
Did you executed
ldconfig
command after setting LD_LIBRARY_PATH
so the changes get applied? I always forget to do it.– r1verside
Jan 5 '18 at 3:45
3
3
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47
add a comment |
1 Answer
1
active
oldest
votes
Simple do not activate conda by default. Modify .bashrc to activate conda only if you want it to be activated. This way you fully separate it from the system... At least this works on Linux and osx. No idea about windows.
New contributor
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414904%2fanaconda-qt-vs-system-qt%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Simple do not activate conda by default. Modify .bashrc to activate conda only if you want it to be activated. This way you fully separate it from the system... At least this works on Linux and osx. No idea about windows.
New contributor
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
add a comment |
Simple do not activate conda by default. Modify .bashrc to activate conda only if you want it to be activated. This way you fully separate it from the system... At least this works on Linux and osx. No idea about windows.
New contributor
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
add a comment |
Simple do not activate conda by default. Modify .bashrc to activate conda only if you want it to be activated. This way you fully separate it from the system... At least this works on Linux and osx. No idea about windows.
New contributor
Simple do not activate conda by default. Modify .bashrc to activate conda only if you want it to be activated. This way you fully separate it from the system... At least this works on Linux and osx. No idea about windows.
New contributor
New contributor
answered yesterday
looooloooo
1
1
New contributor
New contributor
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
add a comment |
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
Welcome to Unix.SE! Could you edit your answer to show more details of how to go about what you’re describing? Since it’s simple, it shouldn’t be hard to explain ;-).
– Stephen Kitt
yesterday
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
If I'm not mistaken, that corresponds to my solution 4
– Alechan
9 hours ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414904%2fanaconda-qt-vs-system-qt%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you executed
ldconfig
command after settingLD_LIBRARY_PATH
so the changes get applied? I always forget to do it.– r1verside
Jan 5 '18 at 3:45
3
File bugs with the anaconda Qt devs asking them to stop bundling stuff with their software. This hostility to the OS, the attitude that the system is nothing but a terrible obstruction to our glorious code which must be ignored, worked around, and subverted is the worst thing about python (and ruby and some other languages). Bundling is not only lazy and arrogant, it's actively harmful.
– cas
Jan 5 '18 at 3:47