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.
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.
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.
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.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1172
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://pyserial.sourceforge.
| |net/
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1172
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.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1172
Summary: pySerial support
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
Add a pySerial wrapper.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.