Am 01.02.2016 um 10:26 schrieb eryk sun:
> On Sun, Jan 31, 2016 at 10:42 PM, Mark Hammond
> wrote:
>> On 17/01/2016 6:51 AM, Malte Forkel wrote:
>>> I'm trying the register a COM server using the install script of a built
>>> distribution, created with the bdist_wininst format of distutils. But
Am 01.02.2016 um 05:42 schrieb Mark Hammond:
> On 17/01/2016 6:51 AM, Malte Forkel wrote:
>> Hi,
>>
>> I'm trying the register a COM server using the install script of a built
>> distribution, created with the bdist_wininst format of distutils. But
>> the script fails with a message that MSVCR90.d
Eryk's reply is right on the money - I'd forgotten about that. IIRC,
having that manifest directly in pythoncomxx.dll or pywintypesxx.dll
ended up using a different activation context, which had its own
problems; that loader module exists purely to work around these problems.
I'm still a bit c
On 2/1/2016 1:27 PM, Ulli Horlacher wrote:
When I compile my Python program with PyInstaller and give it to a user
with Windows 8.1 he gets the warning:
Windows protected your PC
Windows SmartScreen prevented an unrecognized app from starting.
Publisher: Unknown Publish
When I compile my Python program with PyInstaller and give it to a user
with Windows 8.1 he gets the warning:
Windows protected your PC
Windows SmartScreen prevented an unrecognized app from starting.
Publisher: Unknown Publisher
App: fexit.exe
How can I prevent
On Sun, Jan 31, 2016 at 10:42 PM, Mark Hammond wrote:
> On 17/01/2016 6:51 AM, Malte Forkel wrote:
>>
>> I'm trying the register a COM server using the install script of a built
>> distribution, created with the bdist_wininst format of distutils. But
>> the script fails with a message that MSVCR9
