Re: Question regarding building Python Windows installer

References	(1 earlier) <7B6560631CF08A4B8189A9CB669768F4228EB578@FMSMSX101.amr.corp.intel.com> <CAKJDb-Ox2BYk9pjUXwsB0V26rZ3o0og_7UVbq1BHWAxZDeu4Ag@mail.gmail.com> <7B6560631CF08A4B8189A9CB669768F4228EC7B2@FMSMSX101.amr.corp.intel.com> <CAKJDb-N640pOaepN7WhO1hbiZg5nCdUznvUO4td3cMzkJJ4PZg@mail.gmail.com> <7B6560631CF08A4B8189A9CB669768F4228ECF7B@FMSMSX101.amr.corp.intel.com>
From	Zachary Ware <zachary.ware+pylist@gmail.com>
Date	2013-07-15 15:51 -0500
Subject	Re: Question regarding building Python Windows installer
Newsgroups	comp.lang.python
Message-ID	<mailman.4746.1373921488.3114.python-list@python.org> (permalink)

Show all headers | View raw

(Side note: Please avoid top-posting in future.  Bottom-posting keeps
context more clearly)

On Mon, Jul 15, 2013 at 2:27 PM, Mcadams, Philip W
<philip.w.mcadams@intel.com> wrote:
> Yes.  My goal was to create the installer to put the modified python on my Mercurial server.  So I could have effectively copied over the <source tree with your compiled interpreter\Lib\site-packages to the <Python2.7 install dir>\Lib\site-packages on the server?  What I was trying to resolve was the issue with large Mercurial pushes.  I instead am using the IIS Crypto tool to resolve the issue.  I'd found a link that stated that modification to the _ssl.c module in Python could also fix the issue but that the python source would to be recompiled.  Since we are going with IISCrypto the Python change is no longer needed.  But out curiosity, and in case I ran into a situation where did indeed need to make a fix to Python I've wondered what's the best way to do that.  Hopefully this gives you a little insight on what I'm trying to do.  Thanks for your replies.
>

Hmmm, not quite.  <source tree with your compiled
interpreter>\Lib\site-packages would be empty.  I meant the other way
around, copying the installed site-packages dir into the source tree
to use mercurial from the source tree.  I think you'd also have to
copy hg and hg.bat from <install dir>\Scripts as well, though.  You
might have been able to get away with just copying the newly compiled
_ssl.pyd from your source tree to <install dir>\DLLs, but I can't
guarantee that.

I think the solution you've gone for is a much better solution in the
long run, though.  Building your own Python (on Windows) should
probably be a last resort.

--
Zach

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

Thread

Re: Question regarding building Python Windows installer Zachary Ware <zachary.ware+pylist@gmail.com> - 2013-07-15 15:51 -0500

csiph-web