Path: csiph.com!usenet.pasdenom.info!gegeweb.org!newsfeed.kamp.net!newsfeed.kamp.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: zachary.ware@gmail.com
In-Reply-To: <7B6560631CF08A4B8189A9CB669768F4228ECF7B@FMSMSX101.amr.corp.intel.com>
References: <7B6560631CF08A4B8189A9CB669768F4228E86B7@FMSMSX101.amr.corp.intel.com> <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: Mon, 15 Jul 2013 15:51:05 -0500
Subject: Re: Question regarding building Python Windows installer
To: "Mcadams, Philip W" <philip.w.mcadams@intel.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "python-list@python.org" <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.4746.1373921488.3114.python-list@python.org>
Lines: 34
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:50712

(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 m=
y Mercurial server.  So I could have effectively copied over the <source tr=
ee with your compiled interpreter\Lib\site-packages to the <Python2.7 insta=
ll 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 t=
ool to resolve the issue.  I'd found a link that stated that modification t=
o 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 Pytho=
n 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 wh=
at 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