> "But the only thing is installing python on every client system is the > challenge. Because we have nearly 2000+ systems in which we need to install. > > Which is a hectic task for sysadmins to do. That's the reason we opted for > a network python."
It seems to me that if you have 2000+ machines to admin, that your sysadmins would have a solutions for remote distribution of packages. I can't believe they would have to manually install python on each of 2000 machines. > 1. From my understandings, pyinstaller will make a executable package (which > i want to avoid). Yea it will create an executable package either as a single file, or a directory, that is portable. It doesn't mean you have to make the package completely self contained, if you were to use the approach I suggested of a wrapper that sources all of the python modules from the network location. Then the executable just becomes a portable python environment. > 2. Can you explain for is there a detailed explanation anywhere. Bcoz i > never used pyinstaller. The pyinstaller manual has a lot of information: http://www.pyinstaller.org/export/v2.0/project/doc/Manual.html?format=raw You can either use the pyinstaller script as a one-step process to build the package, with command line flags, or, you can use the approach where you first call Makespec to build a .spec file. You would then tweak that file with your specific settings, and then run the build tool with the spec file to build the package. This allows you to save the same spec file and just rebuild new packages. And also allows you to do a lot more options. > 3. In my studio production systems are having 32 and 64 bit OS. Today we > tried locally on development systems with different bits ver of Python. > Application was developed in 64 bit. compiled and placed the application > files (.pyc) and the dependent modules (like PyQt4, mysql connector, win32, > etc) and paths are set. when i launched it on the original developed system. > it worked from serve too, but when it comes to other development system with > python 32 bit. we faced problems at imports of PyQt and win32 modules. OSX/Linux allow for "fat" binaries that contain multiple architectures. I am not sure the extend of this in Windows though. I believe you would need two different python installations. But this is where pyinstaller might help since you only need to build two packages, and then just dist them to the proper target machines. > > as you mentioned in one of ur reply "If you at least have python installed > on the clients, Im sure a network location for PyQt would work fine" > > So do i need to place both 32 and 64 bit PyQt and win32 modules on server > and depending on the python application bit i need to set the path...? Probably. You can either go the route of having python scripts that source the right path locations, or, pyinstaller packages that are build with 32 or 64 bit environments. > > > On Thursday, September 27, 2012 7:31:15 PM UTC+5:30, Justin Israel wrote: >> >> Use pyinstaller to package just the python environment. Make the entry >> point a wrapper python script that sets up the sys.path to point at the >> server network locations of your actual project. >> Then when your app runs, it will use the live production location instead >> of the bundled code. You can update network code and everyone will pick it >> up at next launch. I have an app that does this at my studio as well. >> >> >> On Sep 26, 2012, at 11:28 PM, PBLN RAO <[email protected]> wrote: >> >> Justin, >> >> You understood me correctly. >> >> Previously I tested the PyQt and mysql modules from a server on network, >> and they worked perfectly. >> >> But the only thing is installing python on every client system is the >> challenge. Because we have nearly 2000+ systems in which we need to install. >> Which is a hectic task for sysadmins to do. That's the reason we opted for a >> network python. >> >> Any how thx for the help. >> >> If you have any alternates let me know. Mean while i will also try any >> other alternates. >> >> On Wednesday, September 26, 2012 7:54:55 PM UTC+5:30, Justin Israel wrote: >>> >>> I am not certain how windows behaves in this situation, but I know on osx >>> or linux you can have python installed on the network and run scripts from >>> that interpreter, which would pick up PyQt in its site-packages. >>> You would have to see if windows doesn't complain about running python >>> from a network location. Otherwise, pyinstaller might be your best option if >>> you dont want python installed locally. It will create a standalone exe >>> (which you said you didnt want). >>> If you at least have python installed on the clients, Im sure a network >>> location for PyQt would work fine. >>> >>> On Sep 26, 2012, at 1:06 AM, PBLN RAO <[email protected]> wrote: >>> >>> Hi all, >>> >>> we have developed an application which is a portable version and in a >>> stage to deploy. >>> >>> we are planning to keep the copy (all .pyc) in server and give shortcuts >>> to end user to use it from server. >>> >>> the client systems will not have python and pyqt installed locally. >>> >>> so how can we deploy this app in server so that all of them can access >>> without installation process or making it a .exe. >>> >>> -- >>> view archives: http://groups.google.com/group/python_inside_maya >>> change your subscription settings: >>> http://groups.google.com/group/python_inside_maya/subscribe >> >> -- >> view archives: http://groups.google.com/group/python_inside_maya >> change your subscription settings: >> http://groups.google.com/group/python_inside_maya/subscribe > > -- > view archives: http://groups.google.com/group/python_inside_maya > change your subscription settings: > http://groups.google.com/group/python_inside_maya/subscribe -- view archives: http://groups.google.com/group/python_inside_maya change your subscription settings: http://groups.google.com/group/python_inside_maya/subscribe
