Last year a survey was conducted on python 2 and 3 usage.
Here is the 2014 edition, slightly updated (from 9 to 11 questions).
It should not take you more than 1 minute to fill. I would be pleased if
you took that time.
Here's the url: http://goo.gl/forms/tDTcm8UzB3
I'll publish the results around the end of the year.
Last year results: https://wiki.python.org/moin/2.x-vs-3.x-survey
I installed Python 3.4.2 on my work computer. I was looking at the book
"Head First Programming" which references download PYGAME. I downloaded
what I believe to be the correct version and it tells me that I don't see
the installer. I look in the registry and there is no:
Did I do something wrong? This is all new to me. Any help would be greatly
[image: Inline image 1]
FYI, I've just committed these changes (http://bugs.python.org/issue22919).
There shouldn't be any immediate failures, as the updated projects will still build with VS 2010, but our Windows developers/buildbots can migrate onto the later tools as they feel comfortable.
I know there are at least a few bugs coming out of the new compiler, so I'll be tracking those down and fixing things. Feel free to nosy me (or Windows) on the issue tracker if you find anything.
It is my pleasure to announce the release of Python 2.7.9, a new bugfix
release in the Python 2.7 series. Despite technically being a
maintenance release, Python 2.7.9 includes several majors changes from
- The "ensurepip" module has been backported to Python 2.7
- Python 3's ssl module has been backported to Python 2.7.
- HTTPS certificates are now verified by default using the system's
- SSLv3 has been disabled by default due to the POODLE attack.
Downloads are at
Please report bugs to
I would like to thank the people who made the above security and
usability improvements listed above possible. Among others, Alex Gaynor,
David Reid, Nick Coghlan, and Donald Stufft wrote many PEPs and a lot of
code to bring those features to 2.7.9. Thank you.
2.7 release manager
on behalf on python-dev and all of Python's contributors
I was visiting you buildbot page for inspiration and found that i apparently have the option to force stop/start all your builds without any access control.
You may want to put something to enforce access control?
On behalf of the IronPython team, I'm very happy to announce the
release of IronPython 2.7.5. Like all IronPython 2.7-series
releases, .NET 4 is required to install it. Installing this release
will replace any existing IronPython 2.7-series installation.
Assemblies for embedding are provided for .NET 3.5, .NET 4, .NET 4.5,
and Silverlight 5.
IronPython 2.7.5 is primarily a collection of bug fixes which
smooths off many of the remaining rough edges. The complete list of
changes is also available.
A major new feature is the inclusion of `ensurepip`, which will
install the `pip` package manager:
; -X:Frames is required when using pip
ipy.exe -X:Frames -m ensurepip
; Run from an Administrator console if using IronPython installer
ipy.exe -X:Frames -m pip install html5lib
**Note:** The assembly version of IronPython has changed to 188.8.131.52.
All previous 2.7 versions had the same version (184.108.40.206) which caused
issues when different versions were installed. Publisher policy files
are used to so that applications don't have to be recompiled, but
recompiling is strongly recommended.
A huge thanks goes out to Pawel Jasinski, who contributed most of the
changes in this release. Thanks is also due to Simon Opelt, Alex Earl,
Jeffrey Bester, yngipy hernan, Alexander Köplinger,Vincent Ducros, and
For Visual Studio integration, check out Python Tools for Visual
Studio which has support for IronPython as well as CPython, and
many other fantastic features.
IronPython 2.7.5 is also available for embedding via NuGet. The main
package is IronPython, and the standard library is in
MicroPython is a Python3 language implementation which scales down to
run on microcontrollers with tens of Ks of RAM and few hundreds of Ks
of code size. Besides microcontrollers, it's also useful for small
embedded Linux systems, where storage space is limited, for embedding
as a scripting engine into standalone applications, where quick startup
time is needed, etc.
It went several months since the original announcement of MicroPython 1.0
there were number of releases in the meantime, but we were too busy
implementing new features, so this announcement provides just high-level
overview of changes:
* Basic Unicode support added (thanks to Chris Angelico for driving the
* More functionality of standard types and functions are implemented
(for example, MicroPython can run subset of http.client module
functionality from CPython3 stdlib).
* Highly optimized for code size implementations of important Python
modules are added. There offer subset of functionality and prefixed
with "u". For example, ure, uheapq, uzlib, uhashlib, ubinascii are
* Lots of microcontroller hardware bindings added and generalized.
Besides core interpreter, there's also good progress on modules and
* MicroPython standard library project,
https://github.com/micropython/micropython-lib , an effort to
port/develop as much as possible Python stdlib modules to
MicroPython, has good progress, with few dozens of modules available
on PyPI already (pip-micropython wrapper is provided to install
* An asyncio subset implementation, dubbed "uasyncio", is available
and should be stable enough.
* Proof of concept web microframework, "picoweb", based on uasyncio is
being developed: https://github.com/pfalcon/picoweb
* Lots of other projects available on github.
Reference implementation of MicroPython runs on a microcontroller board
with 1Mb Flash and 128Kb RAM, which should offer good platform for
people interested in microcontroller usage (more info:
http://micropython.org/). MicroPython can also be easily built and
supported on Linux, MacOSX, and Windows systems (more info: