> I would also point out that CPython (distutils, specifically)
supported mingw builds (that's the original mingw 32-bit version) for
a long time. Support for that bit-rotted as the mingw project
fragmented with various 64-bit versions, and slow progress from the
mingw project(s) for supporting
On Feb 1, 2018, at 04:19, Oleg Sivokon wrote:
>
> Oh, so this is the real reason... well, corporate interests are hard to argue
> against. But, this is an interesting statistic nevertheless. Thanks for
> letting me know.
Maybe it hasn’t happened because no volunteer has
> As much as Steve is unlikely to do the work to initiate and
> maintain support of these other tools—whether due to his employer's
> interests or his own—I too was unlikely to do work like this thread is
> asking. In fact, the chances I would have done it were zero because I was
> sitting on my
On Thu, Feb 1, 2018 at 4:19 AM, Oleg Sivokon wrote:
>
> > so why shouldn’t the one with the most users?
>
> Because it makes compilation difficult, and cross-compilatin completely
> impossible? Why is it difficult: a package maintainer needs to (1) buy MS
> Windows (2) create
On 2018-02-01 10:19, Oleg Sivokon wrote:
>
>> so why shouldn’t the one with the most users?
>
> Because it makes compilation difficult, and cross-compilatin completely
> impossible? Why is it difficult: a package maintainer needs to (1) buy MS
> Windows (2) create a special workflow for
> so why shouldn’t the one with the most users?
Because it makes compilation difficult, and cross-compilatin completely
impossible? Why is it difficult: a package maintainer needs to (1) buy MS
Windows (2) create a special workflow for compiling on a different machine.
This is both costly
On 1 February 2018 at 00:42, Gregory P. Smith wrote:
> TL;DR of Steve's post - MSVC is the compiler of choice for most serious
> software on Windows. So we use it to best integrate with the world. There is
> no compelling reason to change that.
>
> The free-as-in-beer MSVC
On Wed, Jan 31, 2018 at 03:04:04PM +, Oleg Sivokon wrote:
> Now, since Go won't compile with MSVC
[...]
Perhaps you should be asking Google why Go doesn't support the most
popular C compiler on Windows.
--
Steve
___
Python-Dev mailing list
ntinuing with it is perfectly sound.
> Unwillingness on the part of package developers to not even test on Windows
> before releasing a wheel for it is not a compelling reason to change
> anything.
>
>
>
> Cheers,
>
> Steve
>
>
>
> Top-posted from my Windows phone
>
>
&
on Windows
before releasing a wheel for it is not a compelling reason to change anything.
Cheers,
Steve
Top-posted from my Windows phone
From: Oleg Sivokon
Sent: Thursday, February 1, 2018 5:40
To: python-dev@python.org
Subject: [Python-Dev] Why is Python for Windows compiled with MSVC?
Hello
On 2018-01-31 19:07, Ray Donnelly wrote:
On Wed, Jan 31, 2018 at 3:04 PM, Oleg Sivokon wrote:
Hello list.
I'll give some background before asking my question in more detail.
[snip]
Now all I had to do was to re-create my success on Windows (most of the
employees in my
On 1/31/2018 10:04 AM, Oleg Sivokon wrote:
Why did you choose to use non-free compiler, which also makes cross-compilation
impossible? There wasn't really a reason not to choose MinGW as
Python was ported to DOS years before the initial 1998 release of the
mingw32 predecessor. There has
On Wed, Jan 31, 2018 at 3:04 PM, Oleg Sivokon wrote:
> Hello list.
>
> I'll give some background before asking my question in more detail.
>
> I've been tasked with writing some infrastructure code that needs to talk to
> Kubernetes. (Kubernetes is a popular software for
Hello list.
I'll give some background before asking my question in more detail.
I've been tasked with writing some infrastructure code that needs to talk to
Kubernetes. (Kubernetes is a popular software for managing and automating
virtualization / containerization of cloud services). One of
14 matches
Mail list logo