One alternative to consider is using Cygwin. A complete Cygwin environment,
including a GCC toolchain, is pretty small. And it can build a *nix-style
CPython that works inside the Cygwin environment. That may not be sufficient
for a lot of uses, but for your purpose, it should be.
Another alter
On Feb 26, 2016 9:56 AM, "Alexander Walters"
wrote:
>
> No.
>
> Visual Studio is a solid compiler suit, mingw is a jenky mess, especially
when you try and move to 64bit (where I don't think there is one true
version of mingw).
I see why you say this, but I think you're seriously underestimating m
You might be interested in a project funded by NumFOCUS + PSF to make the
mingw ecosystem work with CPython.
http://mingwpy.github.io/
-- Andy
On Fri, Feb 26, 2016 at 12:24 PM, R. David Murray
wrote:
> On Fri, 26 Feb 2016 10:05:19 -0800, Dan Stromberg
> wrote:
> > But what do you really think
On Fri, 26 Feb 2016 at 10:18 Alexander Walters
wrote:
> You mean honestly pointing out what would happen with a suggestion? It
> is a horrifically bad idea. I didn't say they were bad people.
>
You're right, you didn't directly insult Mathieu, but the tone was
unnecessary. Calling mingw a "jenk
On Fri, 26 Feb 2016 10:05:19 -0800, Dan Stromberg wrote:
> But what do you really think?
>
> IMO, windows builds probably should do both visual studio and mingw.
> That is, there probably should be two builds on windows, since there's
> no clear consensus about which to use.
>
> I certainly pref
You mean honestly pointing out what would happen with a suggestion? It
is a horrifically bad idea. I didn't say they were bad people.
On 2/26/2016 13:14, Brian Curtin wrote:
The attitude in these responses is counter productive and not really
how it works on this list.
On Fri, Feb 26, 2016 at
Hi Mathieu
I just want to say that we are very aware of the concerns and issues
faced here and people (including myself) are actively working to resolve
them.
For example, I am working with the Visual C++ team to encourage and
support work such as
https://blogs.msdn.microsoft.com/vcblog/201
Ok, fine. Bring a windows build bot online. And also take on the
support burden of guiding people to which version of which compiler you
use for each of the currently supported python versions. And go ahead
and write the pep to change how wheel distributions work (which will
effectively kill
But what do you really think?
IMO, windows builds probably should do both visual studio and mingw.
That is, there probably should be two builds on windows, since there's
no clear consensus about which to use.
I certainly prefer mingw over visual studio - and I have adequate
bandwidth for either.
No.
Visual Studio is a solid compiler suit, mingw is a jenky mess,
especially when you try and move to 64bit (where I don't think there is
one true version of mingw). I'm sorry that Visual Studio makes it very
hard for you to contribute, but changing THE compiler of the
distribution from the
Hi.
I am currently working on adding some functionality on a standard
library module (http://bugs.python.org/issue15873). The Python part
went fine, but now I have to do the C counterpart, and I have ran into
in several problems, which, stacked up, are a huge obstacle to easily
contribute further.
ACTIVITY SUMMARY (2016-02-19 - 2016-02-26)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open5437 ( +5)
closed 32764 (+46)
total 38201 (+51)
Open issues wit
12 matches
Mail list logo
