Package: python-ldtp Version: 0.8.0-2 Severity: normal Perhaps I just don't know how to use things (the documentation isn't very good, I found some wiki tutorial that described how to click some button if I know some magic application name or something, but I had no idea how to find that out so I tried getapplist().(*) But python-ldtp probably shouldn't just hang:
------------------------------------------------------------ $ env LDTP_DEBUG=1 python Python 2.4.4 (#2, Jan 13 2007, 18:15:24) [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from ldtp import * >>> from ldtputils import * >>> getapplist() 124 ( ) Wed Mar 7 03:01:33 2007: Client packet len: 88 i = 0 Data read 88, packet-len = 0, bytes read = 88, data: <?xml version="1.0"?><REQUEST><ACTION>124</ACTION><ID>2061316612512054792</ID></REQUEST> PACKET LENGTH: -88 i = 0 ---- [hangs forever, not breakable by ctrl-c] -------------- I run KDE (3.5.6) and I'm not even sure I have any at-enabled applications running, so perhaps that has something to do with this? I also tried LDTP_DEBUG=2 as suggested in http://ldtp.freedesktop.org/wiki/LDTP_20test_20scripts_20in_20python, but that way I still just get another ldtp server started by ldtp-python. Also a suggestion for the documentation: Explain that the `ldtp' binary is a daemon/server and that it is not supposed to be run manually (I think?) when using the python interface. I found out it's a daemon by strace()ing it to figure out what the heck it is supposed to do because it seemed to just hang there doing nothing after I started it ;) --help output does have an option for "Start[ing] LDTP scripting engine on TCP port", but it wasn't quite obvious that the ldtp binary itself IS (rather than includes or with this option starts) the scripting engine. Ok, so it's a tool for developers and people who have some idea about how to use Linux, so it's not so critical that it's hard to figure out, but anyway. I appreciate your packaging efforts! Sami (*) The page on recording tells to "check the application name in at-poke", but if I understood things correctly, python-ldtp (and specifically getapplist()) should make it redundant too? Also there's no at-poke in Debian. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages python-ldtp depends on: ii ldtp 0.8.0-2 GNU/Linux Desktop Testing Project ii python 2.4.4-2 An interactive high-level object-o ii python-support 0.5.6 automated rebuilding support for p python-ldtp recommends no packages. -- no debconf information
signature.asc
Description: Digital signature
