> The practical problem is: how should 'The PSF' get a Microsoft-signed
> certificate?
If you want to experiment with a signed installer, try
http://www.dcl.hpi.uni-potsdam.de/home/loewis/python-2.5.1.msi
In order for Windows to verify the signature, you can install
http://www.dcl.hpi.uni-potsd
Martin v. Löwis wrote:
>> I have a set of extensions that use SWIG to wrap my own C++ library.
>> This library, on a day-to-day basis is built against VS8 since the rest
>> of our product suite is. Right now I have no way to work with this code
>> using VS8 since the standard distribution is buil
I recommend that those people install the official binaries. Why do
you
need to build the binaries from source, if all you want is to build
extensions?
I've been following this discussion and it seems like an appropriate
place to mention such a scenario which I have encountered myself and
>> Is there a shell script to build a final distribution tree? If
>> not, is there a simple way to build an MSI similar to the one found
>> on the Python.org site for the official releases but using the
>> PCBuild8 stuff?
>
> I believe not.
It's actually not that difficult. You just have to run
> From: Jamie Kirkpatrick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 23 May 2007 5:16 AM
> I have a set of extensions that use SWIG to wrap my own C++ library. This
library, on a
> day-to-day basis is built against VS8 since the rest of our product suite
is. Right now
> I have no way to work w
> I have a set of extensions that use SWIG to wrap my own C++ library.
> This library, on a day-to-day basis is built against VS8 since the rest
> of our product suite is. Right now I have no way to work with this code
> using VS8 since the standard distribution is built against VS7 which
> uses
