A difficult decision for any Python team is whether to move from Python 2 and into Python 3. Although this is not a new decision for Python development teams, 2017 brings with it several important differences that make this decision crucial for proper forward planning. It feels like this is the year that we're really seeing the move to Python 3. It will be a long road, but I think Python 3 may finally have the upper hand.

ActivePython 2.7.13 has just been released, following in the footsteps of the community version released by the core team in mid-December. For this version of ActivePython we have included packages that support testing and code quality, such as Pytest and Pyflakes, as well as including some of the most popular packages like VirtualEnv, Six, and Requests.

Steve Hay, a member of the Perl 5 core team, mentions in the community release announcement that “Perl 5.24.1 represents approximately 8 months of development since Perl 5.24.0 and contains approximately 8,100 lines of changes across 240 files from 18 authors.“ And with that, ActivePerl 5.24.1 becomes our recommended version suitable for production contexts. However, there is one ongoing security issue that is important to understand.

Steve Hay, a member of the Perl 5 core team, mentions in the community release announcement that “Perl 5.24.1 represents approximately 8 months of development since Perl 5.24.0 and contains approximately 8,100 lines of changes across 240 files from 18 authors.“ And with that, ActivePerl 5.24.1 becomes our recommended version suitable for production contexts. However, there is one ongoing security issue that is important to understand.

Today we announced the release of our new ActivePython distributions! The updates include releasing our 2.7.12 and 3.5.2 ActivePython builds as well as incorporating some additional packages. In addition to being a founding sponsor of the Python Software Foundation, this is part of our renewed commitment to provide the best in open source languages to communities and businesses alike.

A difficult decision for any Python team is whether to move from Python 2 and into Python 3. Although this is not a new decision for Python development teams, 2017 brings with it several important differences that make this decision crucial for proper forward planning. It feels like this is the year that we're really seeing the move to Python 3. It will be a long road, but I think Python 3 may finally have the upper hand.

ActivePython 2.7.13 has just been released, following in the footsteps of the community version released by the core team in mid-December. For this version of ActivePython we have included packages that support testing and code quality, such as Pytest and Pyflakes, as well as including some of the most popular packages like VirtualEnv, Six, and Requests.

Steve Hay, a member of the Perl 5 core team, mentions in the community release announcement that “Perl 5.24.1 represents approximately 8 months of development since Perl 5.24.0 and contains approximately 8,100 lines of changes across 240 files from 18 authors.“ And with that, ActivePerl 5.24.1 becomes our recommended version suitable for production contexts. However, there is one ongoing security issue that is important to understand.

Today we announced the release of our new ActivePython distributions! The updates include releasing our 2.7.12 and 3.5.2 ActivePython builds as well as incorporating some additional packages. In addition to being a founding sponsor of the Python Software Foundation, this is part of our renewed commitment to provide the best in open source languages to communities and businesses alike.

Today we announced the release of our new ActivePython distributions! The updates include releasing our 2.7.12 and 3.5.2 ActivePython builds as well as incorporating some additional packages. In addition to being a founding sponsor of the Python Software Foundation, this is part of our renewed commitment to provide the best in open source languages to communities and businesses alike.