|
Size: 1066
Comment:
|
Size: 1299
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * where are we w/ the header files ? * testing strategy: pyhglib uses nose, https://nose.readthedocs.org/en/latest/ |
* where are we w/ the header files (i.e. [[https://bitbucket.org/istana/c-hglib/issue/6/write-header-file-w-declarations-for-level|issue 6]] ? * testing strategy: pyhglib uses nose, https://nose.readthedocs.org/en/latest/ . What about test first (see [[https://bitbucket.org/istana/c-hglib/issue/8/write-tests-first-its-a-trick-to-sketch|issue 8]]) |
Wed June 26th 2013, 14h00 UTC+2
partecipants: iulians, ggherdov, idank, marmoute (maybe)
meeting agenda (proposal)
Random items from ggherdov, in no particular order
communitation btween C and hg serve --cmdline. It is via FIFO (unix pipe) and not socket, do we agree?
- question to idank: what other MODE where planned if any?
- supposed to work on windows?
list of python hglib functionalities (extended tutorial ?) I mean: list of commands implemented by python-hglib? I guess c-hglib gotta do the same.
where are we w/ the header files (i.e. issue 6 ?
testing strategy: pyhglib uses nose, https://nose.readthedocs.org/en/latest/ . What about test first (see issue 8)
- can I "attack" a "living" server as I would do with one that offer a socket as IPC? I mean can different programs talk to the same commandserver ?
looks like python-hglib open a subprocess for each command,