Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #41675 > unrolled thread

Re: Windows Deployment Of Python Modules

Started byDavid Robinow <drobinow@gmail.com>
First post2013-03-21 18:40 -0400
Last post2013-03-21 18:40 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Windows Deployment Of Python Modules David Robinow <drobinow@gmail.com> - 2013-03-21 18:40 -0400

#41675 — Re: Windows Deployment Of Python Modules

FromDavid Robinow <drobinow@gmail.com>
Date2013-03-21 18:40 -0400
SubjectRe: Windows Deployment Of Python Modules
Message-ID<mailman.3605.1363905628.2939.python-list@python.org>
On Thu, Mar 21, 2013 at 6:23 PM, Adam Tauno Williams
<awilliam@whitemice.org> wrote:
> 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).
 OK, I have no idea what you're talking about. Clearly you want
something more than installing packages.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web