On Sun, Sep 21, 2014 at 8:20 AM, Nick Coghlan
On 21 September 2014 22:53, Antoine Pitrou
On Sun, 21 Sep 2014 22:36:35 +1000 Nick Coghlan
"Compilation can be hard on Windows" is no longer a factor that is taken into account when deciding whether or not to add things to the standard library
Where is the pronouncement or discussion on that point?
"no longer taken into acount" was too strong - "has significantly less weight due to the existence of other options" is more accurate. It's still part of the rationale for the ssl feature backports, for example.
- we're taking other steps to deal with that problem as part of the packaging toolchain, and one of the key ones is allowing publication of binary wheels for Mac OS X and Windows on PyPI.
I don't see how that changes anything. The hard (or, at least, tedious) part is not publishing packages, it's building the packages in the first place. "setup.py upload" has always worked fine.
Yep, one of the later steps is a build farm integrated into PyPI, so you can just upload the tarball in most cases and you're done. We' re still a *long* way from having that be feasible at this point, but we'll get there eventually.
There's also an option that's free for Open Source that I've been looking at for some Ruby projects I maintain. AppVeyor  is a continuous integration system that integrates well with services like GitHub and BitBucket and will build wheels for Python projects once they've passed tests. This may be a good solution until PyPI can produce a build farm. A quick search of GitHub shows that this seems to be picking up momentum in the Python community more than others. : http://www.appveyor.com/