"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>Brennus wrote:
>> I have solved my problem, or at least part of it by downgrading
>> to Visual Studio 2003. For whatever reason, the same steps applied
>> to Visual Studio 2005 result in massive problems.
>>
>> Even the python.exe compiled by VS 2005
Alex Martelli wrote:
> I believe the python core developers who do develop on Windows have not
> even tried VS 2005 and have no intention of so doing for the foreseeable
> future.
That is not true. I have already tried it. Many others did, too, and
found that Microsoft managed to break ISO C comp
Brennus wrote:
> I compiled pythoncore.lib. I statically link this to my dll
> and define Py_BUILD_CORE before including Python.h.
Can you please elaborate? How did you do this? How do you know
pythoncore.lib is a static library? What msvcrt is it linked
with (use depends.exe to find out)?
> The
Brennus wrote:
> I have solved my problem, or at least part of it by downgrading
> to Visual Studio 2003. For whatever reason, the same steps applied
> to Visual Studio 2005 result in massive problems.
>
> Even the python.exe compiled by VS 2005 throws A/Vs on startup.
>
> Does Python have to use
Brennus <[EMAIL PROTECTED]> wrote:
...
> I have solved my problem, or at least part of it by downgrading
> to Visual Studio 2003. For whatever reason, the same steps applied
> to Visual Studio 2005 result in massive problems.
>
> Even the python.exe compiled by VS 2005 throws A/Vs on startup.
>I have a dll/so which embeds python. I can verify it works by
>compiling it as an executable and adding an appropriate main.
>
>I tried to write unit tests for this library with ctypes and a simple
>python script. Access violations and other strange things result. I
>suspect this is because I am
Martin v. Löwis wrote:
>Brennus wrote:
>> I have a dll/so which embeds python. I can verify it works by
>> compiling it as an executable and adding an appropriate main.
>
>Please explain in more detail how you did the embedding. Did you
>statically link the Python interpreter into your dll/so, or
Brennus wrote:
> I have a dll/so which embeds python. I can verify it works by
> compiling it as an executable and adding an appropriate main.
Please explain in more detail how you did the embedding. Did you
statically link the Python interpreter into your dll/so, or did
you use a shared one?
> H
I have a dll/so which embeds python. I can verify it works by
compiling it as an executable and adding an appropriate main.
I tried to write unit tests for this library with ctypes and a simple
python script. Access violations and other strange things result. I
suspect this is because I am basica
