pcl-expect-qa

pcl-expect-qa@lists.lysator.liu.se

13 discussions

[Bug 1694] Use built in set type instead of deprecated sets module
by bugzilla-daemon＠cvs.lysator.liu.se 13 Oct '11

13 Oct '11

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1694 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Target Milestone|--- |0.2.0 -- Configure bugmail: http://bugzilla.lysator.liu.se/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1694] New: Use built in set type instead of deprecated sets module
by bugzilla-daemon＠cvs.lysator.liu.se 28 Sep '11

28 Sep '11

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1694 Summary: Use built in set type instead of deprecated sets module Product: pcl-expect Version: 0.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: other AssignedTo: ceder(a)lysator.liu.se ReportedBy: qha(a)lysator.liu.se QAContact: pcl-expect-qa(a)lists.lysator.liu.se I'm trying to run an application built with pcl-expect on Python 2.6.5 and I get messages like: /usr/lib/python2.6/site-packages/pcl_expect/__init__.py:23: DeprecationWarning: the sets module is deprecated import sets I've fixed this by applying the following patch: % diff -u pcl-expect-0.1.0/pcl_expect/__init__.py pcl-expect-0.1.0.liu/pcl_expect/__init__.py --- pcl-expect-0.1.0/pcl_expect/__init__.py 2003-10-26 23:49:17.000000000 +0100 +++ pcl-expect-0.1.0.liu/pcl_expect/__init__.py 2011-09-28 10:55:53.010092373 +0200 @@ -20,7 +20,6 @@ FIXME: more doc needed. """ -import sets import os import re import errno @@ -266,8 +265,8 @@ """ self.__first = True - self.__inputs = sets.Set() - self.__readable = sets.Set() + self.__inputs = set() + self.__readable = set() self.__timeout = timeout self.__timeout_raises_exception = timeout_raises_exception self.__timeout_active = False @@ -328,7 +327,7 @@ self.__acted = False - self.__readable = sets.Set(r) + self.__readable = set(r) if len(self.__readable) == 0: if timeout_possible: debug("Processing timeout event") -- Configure bugmail: http://bugzilla.lysator.liu.se/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1545] Raise an exception on uhandled EOF
by bugzilla-daemon＠cvs.lysator.liu.se 04 Mar '05

04 Mar '05

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1545 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Target Milestone|--- |0.2.0 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1545] New: Raise an exception on uhandled EOF
by bugzilla-daemon＠cvs.lysator.liu.se 04 Mar '05

04 Mar '05

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1545 Summary: Raise an exception on uhandled EOF Product: pcl-expect Version: 0.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: other AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: pcl-expect-qa(a)lists.lysator.liu.se It would be better if an unhandled EOF raised an exception. Today, it simply blocks forever (the timeout isn't even triggered!) Care should be taken to raise pcl_expect.EOFError only as a last resort. If there is matching input (without blocking, but possibly after doing some I/O) on any other action, that action should be taken instead. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1445] test
by bugzilla-daemon＠cvs.lysator.liu.se 06 Dec '04

06 Dec '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1445 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1445] New: test
by bugzilla-daemon＠cvs.lysator.liu.se 06 Dec '04

06 Dec '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1445 Summary: test Product: pcl-expect Version: (cvs) Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: other AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: pcl-expect-qa(a)lists.lysator.liu.se please erase me ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1180] Let the Expectable define new actions
by bugzilla-daemon＠cvs.lysator.liu.se 27 Oct '03

27 Oct '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1180 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |0.2.0 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1180] Let the Expectable define new actions
by bugzilla-daemon＠cvs.lysator.liu.se 26 Oct '03

26 Oct '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1180 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1180] New: Let the Expectable define new actions
by bugzilla-daemon＠cvs.lysator.liu.se 26 Oct '03

26 Oct '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1180 Summary: Let the Expectable define new actions Product: pcl-expect Version: (cvs) Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: other AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: pcl-expect-qa(a)lists.lysator.liu.se With the current API, the Controller class defines which actions that are available: - re - eof - timeout It would be better if the actions could be decoupled from the Controller object. Some actions are only relevant for certain Expectable subclasses. For instance, a hypotetical TcpServer class would probably support a single action: "accept". It would set an attribute to the newly accepted TCP connection (which would probably be a TcpBase object). Other actions, such as "glob" or "ex"/"exact", could be implemented in terms of the re action (or some sort of generic "match" action). In order to implement "interact" semantics, where no input is passed to the process until it is certain that it cannot match a previous pattern, all patterns for a particular Expectable must probably know about each other. This complicates things even further. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1172] pySerial support
by bugzilla-daemon＠cvs.lysator.liu.se 23 Oct '03

23 Oct '03

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1172 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From ceder(a)lysator.liu.se 2003-10-23 23:54 ------- Done. All it took was 17 lines of Python code (plus blank lines and comments, for a total of 67 lines). There is even an 11-line demo program that can read raw input from the CT-1 Bar Code Reader. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

pcl-expect-qa