All / Any

ActivePython and CVE-2015-1793


Are ActivePython releases affected by CVE-2015-1793?


No ActivePython releases, in any product line, are affected by CVE-2015-1793.

ActivePerl and CVE-2015-1793


Are ActivePerl releases affected by CVE-2015-1793?


No ActivePerl releases, in any product line, are affected by CVE-2015-1793.

ActiveTcl and CVE-2015-1793


Are ActiveTcl releases affected by CVE-2015-1793?


ActiveTcl is affected. No other releases were shipped with the OpenSSL libraries that have the issue.

Sites where Teacup updates have installed tls versions 1.6.6,, or 1.6.7 are also affected.

tls version will be released with an updated OpenSSL library, and can be installed to patch or replace add-on tls versions in other releases.

Alternately, there is also the option of using teacup to fall back to a tls version prior to 1.6.6 which is not affected.

Contents of cumulative-patch-1 for 3.6.0


What fixes were included in 3.6.0 cumulative-patch-1?


This patch fixes the following issues:

-Minor issue with authentication component failing to re-advertise itself if it crashed for a length of time
-Issue with importing data from previous version if the import included admin buildpacks
-Removes requirement to authenticate newly attached DEAs with every existing DEA. Also removes this requirement from restarting the DEA role or restarting the DEA itself.
-Allows specifying source using https for custom appstore URLs in the web console.

ActivePython - Any plans to update to 2.7.9 or even 2.7.10?


Just wondering... According to the download page, the latest version of ActivePython is 2.7.8, but the official Python release is at 2.7.10:

2.7.9 -> Released 2014-12-10
2.7.10 -> Released 2015-05-23

I understand that the "extra goodies" that ActiveState adds to the distribution add some time to the release, so asking for 2.7.10 would be too much, but 2.7.9 has been around for almost 6 months...

Is there any place where I can check on the ActivePython release schedule so I don't have to bother people here?


TCL exec state saving


I need to save the state of a process, i.e. program, data and exec state, I know it is possible, but is it efficient and how do we do it? I think the hardest is the exec state so I would like to focus on that.


Is it efficient to save the exec state in TCL and how do we do it?

Hi all,

I want to save the whole process context, including the exec state. I know it is feasible but I don't know if with a script language it is efficient and how to do it.
My goal is to chose the best language to to this, and I'm in this community to find out on TCL about this subject.

Thanks to all,

teacup update behind a proxy


this issue is not completely an installation issue but related somehow.

I am behind a proxy and the proxy rejects the update request of teacup. I guess if teacup would use a user agent in the HTTP header field similar to a browser then the proxy would let the request through.

Is it possible to set a user agent for teacup?
Or is there any other possibility for me to get updates?

Thanks in advance


Perl form handling script

I have a Perl script that reads input from an HTML form, edits it and sends e-mail with the fields from the form.

I used the form and entered my data. When I received the e-mail from the script it contained data from a person who used the form before I did AND my data in each field. For example:
Name: John WiltonVernell Turner

What do I do to ensure that the data in the variables in my script only contain the data of the current user and not the previous one?
It doesn't happen all the time.

my code to read the form data looks like this:
sub GetFormInput {

Start Komodo with Clean Profile


How can I easily start Komodo with a clean profile?


Sometimes when you're using Komodo you may run into issues or want to see what your default settings were many customizations later.

In either case, you or the Komodo dev team will want you to start Komodo with a clean profile. One way is to manually move your profile aside using the instructions provided in another general FAQ post about Komodo File Locations.

Another easier and less error prone way is to use the KOMODO_USERDATADIR environmental variable:

  • Stop Komodo if it is running (this is optional, the following allows you to running multiple instances of Komodo)
  • Open a command line or Terminal window
  • Set KOMODO_USERDATADIR to a path of your choosing. eg.


    set KOMODO_USERDATADIR=%TEMP%\ko #Windows


    export KOMODO_USERDATADIR="/tmp/ko" #unixy

  • Start Komodo from the same commandline window, eg  /path/to/komodo (or just komodo if it's on your PATH).

Komodo will then start with a completely clean profile with all default settings.

- Carey