>> To implement such a system, you need to get all ABI dependencies out
>> of the header files; this includes the structure layouts in particular.
>
> That could hurt the performance of some things. Macros
> like PyList_GET_ITEM etc. rely on knowing about struct
> layouts to get at things quickly.
Martin v. Löwis wrote:
> To implement such a system, you need to get all ABI dependencies out
> of the header files; this includes the structure layouts in particular.
That could hurt the performance of some things. Macros
like PyList_GET_ITEM etc. rely on knowing about struct
layouts to get at th
>>> I think the best lesson here is Tcl. Because it uses stubs mechanism,
>>> you don't need to depend on tclXX.dll, you don't deal with really
>>> direct implementation details, you don't care about runtimes,
>>> everything is much easier. Maybe it's possible (and not too late) for
>>> Python to s
Martin v. Löwis wrote:
>> I think the best lesson here is Tcl. Because it uses stubs mechanism,
>> you don't need to depend on tclXX.dll, you don't deal with really
>> direct implementation details, you don't care about runtimes,
>> everything is much easier. Maybe it's possible (and not too late)
Alexey Borzenkov wrote:
> I think the best lesson here is Tcl. Because it uses stubs mechanism,
> you don't need to depend on tclXX.dll, you don't deal with really
> direct implementation details, you don't care about runtimes,
How does that solve the problem of an extension using
one stdio libra
> I think the best lesson here is Tcl. Because it uses stubs mechanism,
> you don't need to depend on tclXX.dll, you don't deal with really
> direct implementation details, you don't care about runtimes,
> everything is much easier. Maybe it's possible (and not too late) for
> Python to somehow emb
On Thu, Mar 6, 2008 at 3:52 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Mingw tends to be rather more stable (though not itself without the
> occasional library compatibility issue), and more freely available.
Not all extensions can be built using mingw (pywin32 comes to mind
immediately). And
Greg Ewing wrote:
> Steven Bethard wrote:
>> Is this mainly a request to use more open source tools? Because if
>> the concern is just cost, Python 2.6 and 3.0 compile with the free
>> Microsoft Visual Studio 2008 Express editions.
>
> I don't think it's only about cost, it's about not
> being re
Steven Bethard wrote:
> Is this mainly a request to use more open source tools? Because if
> the concern is just cost, Python 2.6 and 3.0 compile with the free
> Microsoft Visual Studio 2008 Express editions.
I don't think it's only about cost, it's about not
being reliant on tools that appear an
Greg Ewing writes:
> Christian Heimes wrote:
> > The latest alphas of Python 2.6 and 3.0 are build with VS 2088.
>
> Wow, that must be a very, very pre-alpha release...
Nah, it's a version optimized for 8/16-bit segmented archi
Steven Bethard wrote:
> On Tue, Mar 4, 2008 at 5:10 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
>> Christian Heimes wrote:
>> > Bob Kline wrote:
>> >> Any possibility of revisiting this question (upgrading to a more recent
>> >> compiler for Windows builds of Python)?
>> >
>> > The latest alph
On Tue, Mar 4, 2008 at 5:10 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Christian Heimes wrote:
> > Bob Kline wrote:
> >> Any possibility of revisiting this question (upgrading to a more recent
> >> compiler for Windows builds of Python)?
> >
> > The latest alphas of Python 2.6 and 3.0 are b
Greg Ewing wrote:
> Christian Heimes wrote:
>> The latest alphas of Python 2.6 and 3.0 are build with VS 2088.
>
> Wow, that must be a very, very pre-alpha release...
>
> Or has someone at Redmond stolen Guido's time machine?
DA-LE
Christian Heimes wrote:
> Bob Kline wrote:
>> Any possibility of revisiting this question (upgrading to a more recent
>> compiler for Windows builds of Python)?
>
> The latest alphas of Python 2.6 and 3.0 are build with VS 2088. I've
^^
Christian Heimes wrote:
> The latest alphas of Python 2.6 and 3.0 are build with VS 2088.
Wow, that must be a very, very pre-alpha release...
Or has someone at Redmond stolen Guido's time machine?
--
Greg Ewing, Computer Science D
Bob Kline wrote:
> Christian Heimes wrote:
>
>> Is VS 2008 recent enought for you? :]
>>
>>
>
> Yes, thanks! I would hope Microsoft has fixed that bug by now. :-)
>
And yes, indeed, the bug is gone in Python 2.6.
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
Christian Heimes wrote:
> Bob Kline wrote:
>
>> Any possibility of revisiting this question (upgrading to a more recent
>> compiler for Windows builds of Python)?
>>
>
> The latest alphas of Python 2.6 and 3.0 are build with VS 2088. I've
> spent some time to get the new build system ready
> Any possibility of revisiting this question (upgrading to a more recent
> compiler for Windows builds of Python)?
Python 2.6 is built with Visual Studio 2008.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/m
Bob Kline wrote:
> Any possibility of revisiting this question (upgrading to a more recent
> compiler for Windows builds of Python)?
The latest alphas of Python 2.6 and 3.0 are build with VS 2088. I've
spent some time to get the new build system ready for Python 3.0a2.
Is VS 2008 recent enought
I know this is a topic which has been discussed before (more than
once). I'm just adding one more data point. Python.org currently uses
VS2003's compiler for building the distributed Windows binaries for
Python. Unfortunately, there's a nasty bug in the runtime libraries
that support this co
20 matches
Mail list logo
