Subscribe: ActiveState Community Site - Comments
http://community.activestate.com/crss
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
activeperl  activepython  activestate  alm  end  install  installation  installers  path  ppm  python  reply  run  script  set  time 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: ActiveState Community Site - Comments

ActiveState Community Site - Comments



Comments



 



Three limitations and a missing option

Tue, 05 Dec 2017 17:31:23 +0000

In reply to ppm update error:

1). Never use the version number as part of the installation target PATH. This has been a fatal problem for years. Especially, do not use ".". Windows software still doesn't handle "." in a folder name consistently.

2.) PPM does not work as expected when multiple versions of ActivePerl are installed simultaneously. Only *the last* version of PPM installed will be working. There is a work-around for this which basically is writing a batch script that alters the PATH value every time you switch Perls.

3). If you install ActivePerl into "Program Files" the functionality of PPM cannot be guaranteed. You will need to run PPM with elevated permissions (as Administrator), or run a PowerShell script to bulk modify the default security settings. That's not going to fix every problem either. There are still modules that will not install or work correctly if the Path includes white space. There is a workaround, which is to use an alternate module installation area on a per-user basis, but there can be only one alternate module installation area (at a time), which makes it incompatible with multiple Perls unless you're running batch files to reset your environment every time you switch Perls.

4). PPM is reporting that it can't modify existing files. The --force option will solve that problem, but --force will be destructive if there is a situation where PPM is working where you don't expect it to be, as it will be in this case.

The Better Way

A better way to deploy multiple versions is to install each one, in turn, into C:\Perl64. As you finish installing them, rename the folder. For example, you might end up with C:\Perl64522 C:\Perl64524, and C:\Perl64526. None of the Perls will work in this configuration (making mutual interference really difficult), but *any* of them will start working the minute you rename the desired folder back to C:\Perl64. This is rather like how PerlBrew works, without the PerlBrew helper scripts.




You may be having the same problem as

Mon, 04 Dec 2017 21:47:44 +0000

In reply to PerlCom.Script making issue with VB6 Application :

https://community.activestate.com/node/11371

The PerlCom Software has been obsolete for a long time.




Apt-get installs Linux O/S packages

Wed, 29 Nov 2017 19:03:40 +0000

In reply to Install other Packages:

If you use apt-get, you will modify a system resource; the python provided by the operating system. The need to use sudo tells you this is a system command, and is restricted to system administrators. ActivePython is not a system resource and should not be sharing resources with a system Python.

Python itself has tools for managing modules. Use one of those. We suggest pip (for Python 2) or pip3 (for Python 3).
http://docs.activestate.com/activepython/3.5/python/installing/index.html




La documentation d'ALM à ce

Mon, 27 Nov 2017 07:57:42 +0000

In reply to ActivePython in ALM VAPI-XP Script: La documentation d'ALM à ce sujet se résume à mettre un lien vers ActivePython. J'ai créé un script VBS qui lance mes scripts Python mais ça n'est pas idéal... Je le joint ci-dessous si ça peut aider quelqu'un. Ce script charge les fichiers stepx.py (x: le numéro de l'étape) et les exécute. ALM is not documented on this point, they just put a link to ActivePython ... I managed to create a VBS script wich load and run my Python script. Here it is : FUNCTION GenererChaineArgs(CurrentTSTest)   DIM chaineArgs   SET aParam = CurrentTSTest   chaineArgs=""   SET paramValueFct = aParam.ParameterValueFactory   SET listeparametres = paramValueFct.NewList("")   FOR EACH param in listeparametres         if param.ActualValue = "" then             chaineArgs = chaineArgs & " --" & Trim(param.Name) & " """ & preparerString(RemoveHTML(param.DefaultValue)) & """"         else             chaineArgs = chaineArgs & " --" & Trim(param.Name) & " """ & preparerString(RemoveHTML(param.ActualValue))  & """"         end if   NEXT   GenererChaineArgs=chaineArgs END FUNCTION 'Supprime les sauts de lignes et les espaces avant et après les mots FUNCTION preparerString(chaine)          preparerString=Trim(replace(replace(chaine,vbCrLf," ")," "," ")) END FUNCTION ' ---------------------------------------------------- ' Main Test Function ' Debug - Boolean. Equals to false if running in [Test Mode] : reporting to Application Lifecycle Management ' CurrentTestSet - [OTA COM Library].TestSet. ' CurrentTSTest - [OTA COM Library].TSTest. ' CurrentRun - [OTA COM Library].Run. ' ---------------------------------------------------- Sub Test_Main(Debug, CurrentTestSet, CurrentTSTest, CurrentRun)   ' *** VBScript Limitation ! ***   ' "On Error Resume Next" statement suppresses run-time script errors.   ' To handle run-time error in a right way, you need to put "If Err.Number <> 0 Then"   ' after each line of code that can cause such a run-time error.   On Error Resume Next   DIM chainearguments   ' clear output window   TDOutput.Clear   chainearguments = GenererChaineArgs(CurrentTSTest)   Set fso = CreateObject("Scripting.FileSystemObject")   Set shl = CreateObject("WScript.Shell")   path="c:\python3\" 'path to folder   IF NOT fso.FolderExists(path)  then      TDOutput.Print "[info] Dossier '" & path & "' introuvable"      path="c:\python34\"   END IF   IF NOT fso.FolderExists(path)  then      TDOutput.Print "[info] Dossier '" & path & "' introuvable"      path="c:\python35\"   END IF   IF NOT fso.FolderExists(path)  then      TDOutput.Print "[info] Dossier '" & path & "' introuvable"      path="c:\python36\"   END IF   If Not Debug Then     Set Steps = CurrentRun.StepFactory.NewList("")     For i =1 to Steps.count         dim tf         dim ts         set tf=TDconnection.testFactory         set ts=tf.item(currentTsTest.Field("TC_TEST_ID"))         atch=TDHelper.DownloadAttachment("step" & i &".py",ts)         If Err.Number <> 0 Then            [...]



Use Encode

Fri, 24 Nov 2017 19:34:15 +0000

In reply to Triggering non-english characters in regular expressions:

The fundamental issue is characters vs bytes:
http://www.perlmonks.org/?node_id=330567

Since RegEx matches "characters", in order to deal with UTF byte strings, you typically need to use the Encode module, as in this example:
http://www.perlmonks.org/?node_id=462670




Getting started with Python

Fri, 24 Nov 2017 19:17:01 +0000

In reply to ActivePython in ALM VAPI-XP Script:

I do not know how to integrate Python with HP ALM. That might be documented in the manuals for ALM. They might also be able to tell you if you must have 64-bit or 32-bit Python, and if you need Python 2.7 versus Python 3.5.

Either version of ActivePython will install the same way:
http://docs.activestate.com/activepython/2.7/get/windows/

Once you have ActivePython installed, you can test your installation with this:
http://docs.activestate.com/activepython/2.7/start/windows/

Python scripts must have a way to invoke the Python interpreter, or must be entered manually after the interpreter has been started. This is commonly done by starting Python and providing it with the filename for the Script. Eg:
python2 mypythonscript.py




Zip files are not available for Community Edition

Fri, 24 Nov 2017 19:00:24 +0000

In reply to How to extract or install headless?:

Customised installers, such as zip file, are available with an ActivePerl Enterprise license.

There are also a number of legacy products that have zip installers available. For these you need a Business Edition license.

All current free ActivePerls do not have zip installers, and are provided as .exe format only.

The options offered by the "help" from the .exe installer come from hooks provided by the installer wrapping tool which creates the .exe files. Most of these options are unimplemented inside the actual installation code. There are only a few that do anything.

See "Running the ActivePerl Setup Wizard on the command line" in the online docs:
http://docs.activestate.com/activeperl/5.26/get/windows/

Note: Most of our ActivePerl installers for 64-bit Windows will only allow you to extend the default installation path of \Perl64 . You cannot completely override it. This is a design limitation in place to allow side-by-side installations of both 32-bit and 64-bit Perls and minimize the chances that they will be installed in a way that will break both versions. This limitation will likely remain in place until we end support for 32-bit Windows.

Second Note: Make sure you are familiar with the terms of the current Community Edition EULA.
Headless installations are most often used in support of a use case that will require OEM or Business Edition licenses.




Wrong place

Fri, 24 Nov 2017 18:29:11 +0000

In reply to install of perl on win ce 6.0:

This is forum for ActivePerl. ActiveState does not provide either of those two binary versions. They have a mailing list for support. I think this is it:
https://sourceforge.net/p/perlce/mailman/perlce-user/?limit=100

ActiveState does not provide any products that are supported on Embedded Devices at this time.




AntiVirus?

Thu, 23 Nov 2017 19:40:00 +0000

In reply to Error 12007 ActiveTCL installation.:

ActiveTcl needs an updated version of the VisualC runtime, and will install
Microsoft Visual C++ 2015 Redistributable (x64) - 14.0.24212
from the Microsoft URL.

Something on your network is preventing this, so the installer should not proceed. It looks like the Microsoft URL may be redirected. In any case, the version that is available on your network does not match the expected CRC signature. You might be able to work around this by manually installing the correct version of the runtime.




Use package require....

Wed, 22 Nov 2017 00:19:48 +0000

In reply to Teapot? What Teapot?:

The new 8.6 installers are "fat" installers; like the old 8.4 installers used to be.

The 8607 installer includes iwidgets 4.1 and bwidget 1.9.10 pre-installed.