111–119 of 119 posts
Not mentioned among the major features: Windows builds have finally moved to Visual Studio 2010.
Just after Visual Studio 2012 was released?
(I did the 2010 changes)
Not mentioned among the major features: Windows builds have finally moved to Visual Studio 2010.
It seems strange to me that they use Visual Studio rather than mingw/msys. Do any HN readers know why that is?
(Windows contributor who did the VS2010 work)
Not mentioned among the major features: Windows builds have finally moved to Visual Studio 2010.
It seems strange to me that they use Visual Studio rather than mingw/msys. Do any HN readers know why that is?
(Windows contributor who did the VS2010 work)
Earlier quoted context omitted.
http://www.python.org/dev/peps/pep-3333/ Last-Modified: 2011-01-16 09:57:25 +0000 (Sun, 16 Jan 2011) ... Status: Final ... Created: 26-Sep-2010 Until this was made final(January 2011), web frameworks that use the wsgi spec had no python 3 path short of ditching the wsgi spec. Now that it is final, there is a path to python 3 for web-dev. Cherrpy got there first I think. Pyramid/Webob got there, and others as well, an…
Django has unofficially supported python 3 for a year.
"•A C implementation of the "decimal" module, with up to 80x speedup for decimal-heavy applications" That in itself is should make a few python gamers happy. Also some serious motivations for older version users, not all but more and more. Also many other interesting develepments others have highlighted already.
"•A C implementation of the "decimal" module, with up to 80x speedup for decimal-heavy applications" That in itself is should make a few python gamers happy. Also some serious motivations for older version users, not all but more and more. Also many other interesting develepments others have highlighted already.
"•A C implementation of the "decimal" module, with up to 80x speedup for decimal-heavy applications" That in itself is should make a few python gamers happy. Also some serious motivations for older version users, not all but more and more. Also many other interesting develepments others have highlighted already.
Earlier quoted context omitted.
It seems strange to me that they use Visual Studio rather than mingw/msys. Do any HN readers know why that is?
I don't know why they don't, but I'd give serious thought to not supporting Windows at all if I had to use mingw/msys. And this is coming from somebody whose first order of business on a Windows machine is to install cygwin. The environment is just Not Friendly. Visual Studio is the vendor-suggested way of building C++ and it's free besides; there's not really a good reason not to use it.
In my experience it's been Cygwin that's a bloated, non-intuitive, awful monstrosity to be avoided at all costs. I've had great difficulties in the past with Cygwin DLL's, particularly when a program comes with its own Cygwin DLL which is a different version than the system Cygwin.
I haven't used Cygwin since 2005 or so due to these difficulties.
For Windows virtualization solutions, my first stop these days would be Virtualbox, qemu or the like. Second preference is mingw/msys.
I've also had a positive experience with a little-known solution called Colinux [1], essentially a Windows port of another little-known technology in the Linux mainline kernel called user-mode Linux. Colinux requires some setup, especially if you want graphics (for GUI work, you need some remote desktop with a Windows client like Xming or VNC). Again, I'd recommend VirtualBox or qemu for casual use, but Colinux is an interesting technology, and I've found it gets very good performance.
My negative experiences with Cygwin were so great, it is only something I use when there is no alternative available. And in preference to all of these is simply using Linux, but sometimes that's simply not an acceptable alternative to Windows (i.e. when you're making a product that you want to run on all popular OS's, supporting only Linux seems like a recipe for disaster. See Sage [2] for an example of an open-source project whose official line on Windows compatbility is "use Virtualbox.")
Earlier quoted context omitted.
I don't know why they don't, but I'd give serious thought to not supporting Windows at all if I had to use mingw/msys. And this is coming from somebody whose first order of business on a Windows machine is to install cygwin. The environment is just Not Friendly. Visual Studio is the vendor-suggested way of building C++ and it's free besides; there's not really a good reason not to use it.
I've found mingw and msys to be very fast and easy to use. In my experience it's been Cygwin that's a bloated, non-intuitive, awful monstrosity to be avoided at all costs. I've had great difficulties in the past with Cygwin DLL's, particularly when a program comes with its own Cygwin DLL which is a different version than the system Cygwin. I haven't used Cygwin since 2005 or so due to these difficulties. For Windows…
Colinux is actually pretty cool, but the need for an X server and the setup time is a pain in the ass.