When you create a pure Python sandbox using virtualenv --no-site-packages the global site-packages directory is rightfully not included ... however, this poses a challenge in accessing non-trivial packages from within the virtualenv.
We recently launched a survey to owners of Komodo IDE 6, asking for their feedback on our newest IDE release. We were really pleased to see that overall our customers are really pleased with what we've provided. We thought we'd share some interesting stats with you in case you're considering picking up a copy of Komodo IDE (don't forget, you save $50 on Komodo upgrades and new Komodo IDE purchases until Dec. 31/10).
We're very excited about the work we're doing with Python these days here at ActiveState. It's been a great year for both Patriots & Python fans, so I though before I shut down my computer to turn my focus to football and turkey, I wanted to reflect on why I am so thankful for Python.
Getting some programmers to come up with a list of things they are thankful for in their favorite programming language is like getting a recalcitrant teenager to say grace at a family dinner. Something about the act of giving thanks seems to make us feel embarrassed and extremely uncool. Most people wouldn't even bother asking, but this Thanksgiving we decided to make a certain Perl developer squirm a bit for his turkey dinner.
Ladies and gentlemen, I give you a list of things I'm apparently thankful for with relation to Perl:
The new toolbox in Komodo 6 (available in Komodo IDE and Komodo Edit) has addressed several concerns we and many of our customers have had over the years. This screencast introduces some of the changes and new features, and the post goes into a bit more detail.
Ease of Sharing
First, we wanted to make it easier to share tools. To do this, we had to free tools from the project system.
Now each tool is a standalone file with a .komodotool extension, and toolbox hierarchies are simply managed by the filesystem.
Dynamic languages have the reputation of being great for quick prototyping of an application, or for quick “duct tape” fixes to link systems together. When it is time to go to full scale production, most people assume that traditional languages, such as Java or C/C#, will be running under the hood. This isn’t necessarily the case. You might be surprised at how many large scale applications rely on dynamic languages.