Zitat von Tony Kelman :
A maintainer has volunteered. Others will help. Can any core developers
please begin reviewing some of his patches?
Unfortunately, every attempt to review these patches has failed for me,
every time. In the last iteration of an attempt to add mingw64 support,
I had ask
On 26 October 2014 23:11, Ray Donnelly wrote:
> I don't know where this "ABI compatible" thing came into being;
Simple. If a mingw-built CPython doesn't work with the same extensions
as a MSVC-built CPython, then the community gets fragmented (because
you can only use the extensions built for you
On 26 October 2014 23:24, Tony Kelman wrote:
> I want, and in many places *need*, an all-MinGW stack.
OK, I'm willing to accept that statement. But I don't understand it,
and I don't think you've explained why you *need* your CPython
interpreter to be compiled with mingw (as opposed to a number o
Not really, to be honest. I still don't understand why anyone not
directly involved in CPython development would need to build their own
Python executable on Windows. Can you explain a single specific
situation where installing and using the python.org executable is not
possible
I want, and in m
On Sun, Oct 26, 2014 at 10:41 PM, Paul Moore wrote:
> On 26 October 2014 13:12, Tony Kelman wrote:
>> Only cross-compilation and the build system in the above list are relevant
>> to CPython, but I hope I have convinced you, Paul Moore, etc. that there are
>> real reasons for some groups of users
On 26 October 2014 14:28, Ray Donnelly wrote:
> I like this idea. To reduce the workload, we should probably pick
> Python3 (at least initially)?
Aren't the existing patches on the tracker already for Python 3.5+?
They should be, as that's the only version that's likely to be a
possible target (u
On 26 October 2014 17:59, Tony Kelman wrote:
> Ensuring compatibility with CPython's
> chosen msvcrt has made that work even more difficult for them.
Ensuring compatibility with CPython's msvcrt is mandatory unless you
want to create a split in the community over which extensions work
with which
On 26 October 2014 13:12, Tony Kelman wrote:
> Only cross-compilation and the build system in the above list are relevant
> to CPython, but I hope I have convinced you, Paul Moore, etc. that there are
> real reasons for some groups of users and developers to prefer MinGW-w64
> over MSVC.
Not real
If this includes (or would likely include) a significant portion of the
Scientific Computing community, I would think that would be a compelling
use case.
I can't speak for any of the scientific computing community besides myself,
but my thoughts: much of the development, as you know, happens on
Hi Stefan,
On 26 October 2014 02:50, Stefan Richthofer wrote:
> It appears weakrefs are only cleared if this is done by gc (where no
> resurrection can happen anyway). If a resurrection-performing-__del__ is
> just called by ref-count-drop-to-0, weakrefs persist -
How do you reach this conclusio
On Sun, Oct 26, 2014 at 2:28 PM, Ray Donnelly wrote:
> On Sun, Oct 26, 2014 at 1:12 PM, Tony Kelman wrote:
>> Thanks all for the responses. Clearly this is a subject about which
>> people feel strongly, so that's good at least. David Murray's guidance
>> in particular points to the most likely pa
On Sun, 26 Oct 2014 06:12:45 -0700, "Tony Kelman" wrote:
> Steve Dower:
> > Building CPython for Windows is not something that needs solving.
>
> Not in your opinion, but numerous packagers of MinGW-based native or
> cross-compiled package sets would love to include Python. The fact
> that they c
On Sun, Oct 26, 2014 at 1:12 PM, Tony Kelman wrote:
> Thanks all for the responses. Clearly this is a subject about which
> people feel strongly, so that's good at least. David Murray's guidance
> in particular points to the most likely path to get improvements to
> really happen.
>
> Steve Dower:
>You shouldn't have to emulate that. The exact behavior of GC is allowed to vary between systems.
Yes, of course. I am looking into this for JyNI, which in contrast should emulate CPython behavior as good as possible.
And for such details, -one by one- I am currently weighting up whether it's ea
Thanks all for the responses. Clearly this is a subject about which
people feel strongly, so that's good at least. David Murray's guidance
in particular points to the most likely path to get improvements to
really happen.
Steve Dower:
> Building CPython for Windows is not something that needs solv
On 26.10.2014 00:14, Ned Deily wrote:
> In article ,
> David Bolen wrote:
>
>> David Bolen writes:
>>
>>> which appears to die mid-stream while receiving the manifests.
>>>
>>> So I'm sort of hoping there might be some record server-side as to why
>>> things are falling apart mid-way.
>>
>> Jus
Frank, Matthew I intel.com> writes:
> 4. Module _decimal is failing to compile. The problem is that it has
> a header called memory.h. Android's libc has the problem that
> /usr/include/stdlib.h includes . But the build system
> puts -I. on the include path before the system dirs (a
17 matches
Mail list logo
