0

At work we have a common /Lib folder on a network drive where we put modules that anyone in the group can access via Python's import command. The folder is on everyone's PYTHONPATH.

But I can't access the shared /Lib now that I have replaced my regular python with the Anaconda distribution. PYTHONPATH is no longer relevant and the answer to this question says it is "unnecessary".

How should a small group of people, some using the Anaconda distribution, on Windows machines share common python code?

Community
  • 1
  • 1
Ian Atkinson
  • 73
  • 1
  • 3
  • import sys print sys.path check your sys.path – pigletfly Jun 03 '15 at 03:16
  • Although I've created a PYTHONPATH environment variable and put the location of the network drive library there, my sys.path is just the folder that I call "print sys.path" from, followed by 'C:\\Miniconda\\python27.zip', 'C:\\Miniconda\\DLLs', etc. Anaconda ignores PYTHONPATH. – Ian Atkinson Jun 03 '15 at 03:44
  • Anaconda should not be ignoring `PYTHONPATH`. If you use `import os; os.environ["PYTHONPATH"]` is it there? – asmeurer Jun 03 '15 at 16:28
  • os.envirion['PYTHONPATH'] bears no relationship to what I set via the Windows "My computer" GUI before rebooting. I believe I need to take this up with my ICT department who manage the more "system" aspects of the machine before I can ask a proper question on stackoverflow. Sorry about wasting your time. – Ian Atkinson Jun 04 '15 at 00:22

1 Answers1

0

The question arose from a Windows machine with a strange configuration, and is not actually about the behaviour of the Anaconda distribution of Python at all. The question should probably be purged from stackoverflow by a moderator.

Ian Atkinson
  • 73
  • 1
  • 3