--
Anaconda Community Support Group Brought to you by Continuum Analytics
---
You received this message because you are subscribed to the Google Groups "Anaconda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+unsubscribe@continuum.io.
To post to this group, send email to anac...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/anaconda/.
Never seen anything quite like this. It seems likely that when you run "python" you are getting a different python than the one you want. Activating environments really should take care of that, though. What is the output ofIf on linux/mac:which pythonif on windows:where pythonand also what isecho $PATHorecho %PATH%PYTHONPATH is also potentially a culprit. Do you have that set?
On Thu, Dec 1, 2016 at 5:31 PM, Mark Yuen <mark....@gmail.com> wrote:
Hi- I am having some trouble with the seaborn package and was wondering if anyone else is seeing the same.Here is what I'm doing (done on 2 diff computers)* creating a new environment and installing seaborn* activating that env* when i try to "import seaborn" it says that there is no module named seaborn. however it shows in that env in anaconda navigator.Also the strangest thing is that the module may actually work though it gives the import error. Is anyone else seeing the same issue? thank you, mark
--
Anaconda Community Support Group Brought to you by Continuum Analytics
---
You received this message because you are subscribed to the Google Groups "Anaconda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+u...@continuum.io.
To unsubscribe from this group and stop receiving emails from it, send an email to anaconda+unsubscribe@continuum.io.