Re: Windows Deployment Of Python Modules

References	<1363896869.1738.30.camel@linux-86wr.site> <CAF3XjbyqLpYdCnJcf5hCCLpbEnm32MDO9eic0N5Lu1hpnCthwQ@mail.gmail.com>
Subject	Re: Windows Deployment Of Python Modules
From	Adam Tauno Williams <awilliam@whitemice.org>
Date	2013-03-21 18:23 -0400
Newsgroups	comp.lang.python
Message-ID	<mailman.3603.1363904627.2939.python-list@python.org> (permalink)

Show all headers | View raw

David Robinow <drobinow@gmail.com> wrote:
>On Thu, Mar 21, 2013 at 4:14 PM, Adam Tauno Williams
><awilliam@whitemice.org> wrote:
>>
>> Python itself is easy to deploy on Windows;  just toss the MSI in
>your
>> local update server and away it goes.
>>
>> That's slick;  LSUS is awesome.
>>   <http://www.localupdatepublisher.com/>
>>
>> But that gives you Python with no pip, easy_install, etc...  And
>*that*
>> is not packaged appropriately.  Is there some trick to getting
>modules
>> installed on Windows workstations en masse [in an automated fashion]?
>> It seems like I must be missing something.
>> For example, I want Python installed, and the iniparse module.
>python setup.py install
>Am I missing something?


Yes! 

 That does not get the package to the workstation.  It also is not conducive to automation (or success auditing).


-- 
Adam Tauno Williams

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Windows Deployment Of Python Modules Adam Tauno Williams <awilliam@whitemice.org> - 2013-03-21 18:23 -0400

csiph-web