The Python releases have come at a very steady pace over the last two months, consistently moving the language ahead. Recently, the Python Software Foundation produced the latest release in the 3.5 series--Python 3.5.3.
How many times have you copied a large chunk of HTML or XML from a web page or
software application and pasted it into Komodo IDE, only to find that it's
either all on one line or not indented properly, and thus a nightmare to read?
properly before you commit it? How can you ensure your Python code is correctly
UPDATE Feb 7, 2017: ActiveTcl 8.6.6 is now available on Windows. You can download it here.
The Tcl Core Team has done an outstanding job with the 8.6 series, with 8.6.6 being the latest version. This version contains some enhancements, but the bulk of the release are bug fixes and improvements to items started earlier in the 8.6 lineage.
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 has been a long road, but Python 3 may finally have the upper hand.
In a way I’m a very isolated developer. Not in that I work from home, which I do, but I work on Komodo, which comes with its own “stack” (Mozilla) and doesn’t have access to a huge package repository like you would with Node.JS. This means much of the work I do is isolated within this stack, and I only interact with what’s happening in the “outside world” through integrations and side projects. You might get the sense that this is a negative, and certainly in some ways it is, but I consider this a positive overall because, frankly, modern full-stack development sucks.
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.
More often than not, debugging is a simple operation: