File: notes.rst

package info (click to toggle)
python-tubes 0.2.1-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 740 kB
  • sloc: python: 3,215; makefile: 149
file content (126 lines) | stat: -rw-r--r-- 4,450 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
In the interst of making this branch more accessible to additional contributors, here are some thoughts that we have about what's going on right now.

We should be at 100% test coverage.

Framing needs a ton of tests.
It hasn't changed a whole lot so documenting and testing this module might be a good way to get started.

``tubes.protocol`` is pretty well tested and roughly complete but could really use some docstrings, and improve the ones it has.
See for example the docstring for flowFountFromEndpoint.

The objects in ``tubes.protocol``, especially those that show up in log messages, could really use nicer reprs that indicate what they're doing.
For example ``_ProtocolPlumbing`` and ``_FlowFactory`` should both include information about the flow function they're working on behalf of.

Similarly, ``tubes.fan`` is a pretty rough sketch, although it's a bit less self-evident what is going on there since it's not fully implemented.
(*Hopefully* it's straightforward, but let's not count on hope.)

There are a bunch of un-covered `__repr__`s, probably.

`tubes.tube.Diverter` could use some better docstrings, as could its helpers `_DrainingFount` and `_DrainingTube`.

There are some asserts littered around the code.
They all need to be deleted.
Some of them should be replaced with real exceptions, because they're a result of bad inputs, and some of them should be replaced with unit tests that more convincingly prove to us that the internal state can never get into that bad place.

The adapter registry in ``_siphon.py`` is probably silly.
It used to contain a lot more entries, but as the code has evolved it has boiled down into 20 or 30 lines of code and docstrings that might be more easily expressed as a single providedBy check.
Unless more entries show up, we want to delete it and fix ``series`` to just do ``ITube.providedBy`` and inline the implementation of ``tube2drain``.

things that we might want to change
===================================

Currently the contract around flowStopped / stopFlow and then more calls to flowTo / flowingFrom is vague.  We might want to adjust this contract so that a fount that has been stopped or a drain that has received a flowStopped is simply "dead" and may not be re-used in any capacity.  For things like real sockets, this is a fact of life; however, it might just as well be communicated by an instant stopFlow() or flowStopped() upon hook-up.

STATK MAECHINES
---------------

With flowTo in FLOWING (current state, sort of, it's not really implemented all
the way):


Fount
~~~~~

::

    INITIAL -flowTo(None)->    INITIAL,
            -flowTo()->        FLOWING,
            -actuallyPause()-> PAUSED_INITIAL,
            -stopFlow()->      STOPPED;

    PAUSED_INITIAL -actuallyUnpause()-> INITIAL,
                   -actuallyPause()->   PAUSED_INITIAL,
                   -stopFlow()->        STOPPED;

    FLOWING -flowTo(other)->   FLOWING,
            -flowTo(None)->    INITIAL,
            -actuallyPause()-> PAUSED,
            -stopFlow()->      STOPPED;

    PAUSED  -flowTo(other)->    FLOWING,
            -flowTo(None)->     INITIAL,

            ^ note that these are problematic, because you have to re-set the
            pause state, which means you have to discard previous pause tokens,
            which we don't currently do

            -actuallyResume()-> FLOWING,
            -actuallyPause()->  PAUSED,
            -stopFlow()->       STOPPED;

    STOPPED.


Drain
~~~~~

::

    INITIAL -flowingFrom()-> FLOWING,
            -flowingFrom(None)-> INITIAL;

    FLOWING -receive()->     FLOWING,
            -flowingFrom(None)-> INITIAL,
            -flowingFrom(other)-> FLOWING,
            -flowStopped()-> STOPPED;

    STOPPED.


Without flowTo in FLOWING (desired state):


Fount
~~~~~

::

    INITIAL -flowTo()->        FLOWING,
            -actuallyPause()-> PAUSED_INITIAL,
            -stopFlow()->      STOPPED;

    PAUSED_INITIAL -actuallyUnpause()-> INITIAL,
                   -actuallyPause()->   PAUSED_INITIAL,
                   -stopFlow()->        STOPPED;

    FLOWING -actuallyPause()-> PAUSED,
            -stopFlow()->      STOPPED;

    PAUSED  -actuallyResume()-> FLOWING,
            -actuallyPause()->  PAUSED,
            -stopFlow()->       STOPPED;

    STOPPED.


Drain
~~~~~

::

    INITIAL -flowingFrom()-> FLOWING;

    FLOWING -receive()->     FLOWING,
            -flowStopped()-> STOPPED;

    STOPPED.