Installing Python on a Windows Network

I am launching a local installation of Anaconda + a third-party tool group (Mosek) + that I wrote ...

I understand that I can wrap everything using virtualenv (or conda) to make it a clean environment.

The company operates on a Win 8 network.

I think there are two fundamental approaches

1) I can install all this on a network drive (do I need Python to write pyc files?). Is it enough if I dump it into a read-only folder? Is it enough if people only change their way? What about the registry (and related problems)?

2) People copy the environment and install it locally. (Maybe with some kind of installer?). That way they can add additional modules without bothering me to change one and only central Python.

I call experts here ...

Thomas

+3
source share
1 answer

condaalready supports automatic configuration 2. Just add the Anaconda network adapter to PATH and use conda to create a new environment conda create. If conda discovers that Anaconda is read-only, it will write things locally. If you are looking for ways to automate this more seamlessly, you should check out Anaconda Server .

Regarding the registry, it is important that Windows applications can automatically find Python.

Regarding the read-only question, as far as I know, Python works great when run from a read-only installation. I can not guarantee that all the libraries that you use will be, but they should.

+1
source

All Articles