Title: Cygwin does not provide siginfo_t.si_band
Type: compile error Stage: resolved
Components: Build Versions: Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: zach.ware Nosy List: Decorater, dellair.jie, erik.bray, loewis, masamoto, python-dev, r.david.murray, rpetrov, vstinner, zach.ware
Priority: normal Keywords: patch

Created on 2014-03-28 15:17 by dellair.jie, last changed 2017-03-31 16:36 by dstufft. This issue is now closed.

File name Uploaded Description Edit
signalmodule.output.txt dellair.jie, 2014-03-31 15:56
cygwin_si_band.patch vstinner, 2014-04-01 12:28 review
3.4-issue21085-cygwin-struct_siginfo.patch masamoto, 2015-03-26 15:48
3.4-issue21085-struct_siginfo.patch masamoto, 2015-03-31 04:23 use configure script review
3.5-issue21085-struct_siginfo.patch masamoto, 2016-08-23 16:49 assigned zero into si_band field review
3.5-issue21085-struct_siginfo-2.patch masamoto, 2016-08-24 08:08 review
tip-issue21085-struct_siginfo-2.patch erik.bray, 2016-08-30 10:03 review
3.4-issue21085-struct_siginfo-2.patch erik.bray, 2016-08-30 10:03 review
3.3-issue21085-struct_siginfo-2.patch erik.bray, 2016-08-30 10:04 review
Pull Requests
URL Status Linked Edit
PR 552 closed dstufft, 2017-03-31 16:36
Messages (40)
msg215050 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-28 15:17

Is Cygwin supported by Python? We met the following error when compiling Python 3.3.2 on Cygwin 1.7.17:

gcc -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes     -I. -IInclude -I./Include    -DPy_BUILD_CORE -o Modules/main.o Modules/main.c
Modules/main.c:17:0: warning: "PATH_MAX" redefined
/usr/include/limits.h:336:0: note: this is the location of the previous definition
Modules/main.c: In function ‘Py_Main’:
Modules/main.c:561:5: warning: implicit declaration of function ‘_setmode’
gcc -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes     -I. -IInclude -I./Include    -DPy_BUILD_CORE -o Modules/gcmodule.o Modules/gcmodule.c
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes     -I. -IInclude -I./Include    -DPy_BUILD_CORE  -c ./Modules/_threadmodule.c -o Modules/_threadmodule.o
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes     -I. -IInclude -I./Include    -DPy_BUILD_CORE  -c ./Modules/signalmodule.c -o Modules/signalmodule.o
./Modules/signalmodule.c: In function ‘fill_siginfo’:
./Modules/signalmodule.c:745:5: error: ‘siginfo_t’ has no member named ‘si_band’
Makefile:1501: recipe for target `Modules/signalmodule.o' failed
make: *** [Modules/signalmodule.o] Error 1

Any lights would be appreciated.

msg215051 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-03-28 15:27
> ./Modules/signalmodule.c:745:5: error: ‘siginfo_t’ has no member named ‘si_band’

This code is conditional, it is surrounded by:


Does Windows support sigwaitinfo() or sigtimedwait()? I would be surprised. You used configure? Check pyconfig.h for these two constants.
msg215052 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2014-03-28 15:31
cygwin is not officially supported.  We do accept patches that improve cygwin support when they are narrowly targted and well motivated.
msg215055 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-28 15:55

I did do ./configure, without any parameters. Should I use it with "--without-signal-module" option? Will all signals be disabled if this option is specified?

From Python document, it mentions Windows support the following signals:
signal.SIGINT, signal.SIGTERM, signal.SIGABRT, signal.SIGFPE, signal.SIGILL, signal.SIGSEGV
The following are found in

 804 /* Define to 1 if you have the `sigtimedwait' function. */
 810 /* Define to 1 if you have the `sigwaitinfo' function. */

msg215183 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-30 14:45
dellair jie: would you like to work on a patch?

It's fine if not, but it may then be that there is no resolution to this issue for the coming months or years (unless somebody else volunteers to write a patch).

Running configure should have created pyconfig.h. Please report what this file has; is not configured.
msg215221 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-31 07:49
Yes, my pleasure. 

After configure on Cygwin, there is pyconfig.h generated, variables are as following:
/* #define HAVE_SIGWAITINFO 1 */

The error disappeared once changed HAVE_SIGWAITINFO to undef.
However, it encountered another issue mentioned here:

The patches provided seem only for 3.2.2, not sure if it is ok to apply them directly on 3.3.2?
msg215232 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-31 12:27
Applied the patch 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in case:

The build failed with parser module:
building 'parser' extension
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude -I/cygdrive/c/temp/Python-3.3.2/Include -I/cygdrive/c/temp/Python-3.3.2 -c /cygdrive/c/temp/Python-3.Modules/parsermodule.c -o build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.Modules/parsermodule.o
gcc -shared -Wl,--enable-auto-image-base build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.Modules/parsermodule.o -L. -L/usr/local/lib -lpython3.3m -o build/lib.cygwin-1.7.17-i686-3.3/parser.dll
build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.Modules/parsermodule.o: In function `parser_sizeof':
/cygdrive/c/temp/Python-3.Modules/parsermodule.c:371: undefined reference to `__PyNode_SizeOf'
collect2: ld returned 1 exit status

Could anyone shed some lights please?

msg215243 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-31 15:16
dellair jie: please focus on one issue at a time. The issue you reported here is the compile error with si_band; I will not discuss any other problems you bring up in this issue.

Note that editing pyconfig.h is not a solution. It's a generated file, so it must not be edited.

To diagnose this further, add the -dD option to the preprocessor output of signalmodule.c, i.e. run

gcc -dD -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes     -I. -IInclude -I./Include    -DPy_BUILD_CORE  -E ./Modules/signalmodule.c 

and attach the resulting file (or else study the output yourself).

BTW, please also understand that Python 3.3 is no longer maintained; it would be good if you could run this porting project on Python 3.4 instead.
msg215247 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-31 15:56

Certainly running on 3.4 now.
The output of the command is attached.

Will try to look into it tomorrow if no immediate follow up post.

msg215248 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-03-31 16:11
I found this patch:
msg215249 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-03-31 16:13
Can you try to comment si_band code in signalmodule.c, and then run test_signal to see if sigwaitinfo works on Windows? test_sigwaitinfo() uses signal.alarm(1): does it work on Windows (with Cygwin)? (sigwaitinfo doc says "Availability: Unix.")
msg215252 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-31 17:20
dellair: According to the compiler output, ./pyconfig.h has

#define HAVE_SIGWAIT 1


So why did you say (in msg215221) that the file had

/* #define HAVE_SIGWAITINFO 1 */

(i.e. where do the comment signs come from)
msg215257 - (view) Author: dellair jie (dellair.jie) Date: 2014-03-31 17:58

Thanks for the analysis!

The following values came from Python 3.3.2, the #define HAVE_SIGWAITINFO 1 was without comment sign, I commented it out for the build to go through.
/* #define HAVE_SIGWAITINFO 1 */

The output was from 3.4, haven't checked the values yet, might be different. Will check it tomorrow.

msg215266 - (view) Author: Roumen Petrov (rpetrov) * Date: 2014-03-31 20:45
STINNER Victor wrote:
> STINNER Victor added the comment:
> I found this patch:

Sure. It seems to me it is extracted from issue3871 .
msg215267 - (view) Author: Roumen Petrov (rpetrov) * Date: 2014-03-31 20:53
dellair jie wrote:
> dellair jie added the comment:
> Applied the patch 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in case:
> The build failed with parser module:
> building 'parser' extension
> gcc ......   .../parsermodule.o: In function `parser_sizeof':
> /cygdrive/c/temp/Python-3.Modules/parsermodule.c:371: undefined reference to `__PyNode_SizeOf'
> collect2: ld returned 1 exit status
> Could anyone shed some lights please?

See  issue18637
msg215302 - (view) Author: dellair jie (dellair.jie) Date: 2014-04-01 09:00

Here is the values presented on Python 3.4.0, in fact they are the same as 3.3.2, please note the key difference.
#define HAVE_SIGWAIT 1
The SIGTIMEDWAIT is undef while the SIGWAIT is defined.
The patch Victor found ( to modify sigalmodule.c works on both 3.3.2 and 3.4 (at least the build went through the sign failure.) 
So shall we close this issue?

Thanks a loot!
The patch you offered about parser works with 3.3.2 and 3.4. 
There is further issues with the build on Cygwin and I will raise it in a separate issue.

msg215303 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-04-01 09:08
> So shall we close this issue?

Nope. Could you please try the test described in msg215249?

We might integrate but it would be better to fix sigwaitinfo() if it works without si_band.
msg215308 - (view) Author: dellair jie (dellair.jie) Date: 2014-04-01 12:13

Would you please be more specific on test_signal?

msg215309 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-04-01 12:28
> Would you please be more specific on test_signal?

Please try to compile Python 3.4 with the attached cygwin_si_band.patch applied, and then run test_signal. I would like to know if all tests pass, and if not, which tests are failing. I also would like to know if test_sigwaitinfo() runs on Cygwin. I'm not sure that signal.alarm(1) is available on Windows, whereas test_sigwaitinfo() uses this function.

Or you can test manually sigwaitinfo(). Example on Windows using SIGINT and CTRL+c to send a signal:

>>> import signal
>>> info = signal.sigwaitinfo({signal.SIGINT})
>>> info
signal.struct_siginfo(si_signo=2, si_code=128, si_errno=0, si_pid=0, si_uid=0, si_status=3, si_band=0)

I don't know how to test sigwaitinfo() on Windows.
msg215319 - (view) Author: dellair jie (dellair.jie) Date: 2014-04-01 14:23

I suppose that Python needs to be built successfully before running test_signal.
Three patches were applied in Python 3.4.0. However, the build failed to build _struct module.

Should I open another Issue to track it?

As long as the build goes through completely on Cygwin, I will go back and do the signal test.

msg217518 - (view) Author: dellair jie (dellair.jie) Date: 2014-04-29 13:37
Finally got it compiled on Cygwin! :)


I am still having issue with the "make test" on Cygwin, hence can only do some manual testing:

>>> info = signal.sigwaitinfo({signal.SIGINT})
>>> info = signal.struct_siginfo((2, 128, 0, 0, 0, 3))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: signal.struct_siginfo() takes an at least 7-sequence (6-sequence given)
>>> info = signal.struct_siginfo((2, 128, 0, 0, 0, 3, 0))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: signal.struct_siginfo() takes an at most 6-sequence (7-sequence given)
>>> help(signal.struct_siginfo)
 |  ----------------------------------------------------------------------
 |  Data descriptors defined here:
 |  si_code
 |      signal code
 |  si_errno
 |      errno associated with this signal
 |  si_pid
 |      sending process ID
 |  si_signo
 |      signal number
 |  si_status
 |      exit value or signal
 |  si_uid
 |      real user ID of sending process
 |  ----------------------------------------------------------------------

Feel free to let me know if more testing is required.

msg239343 - (view) Author: Masayuki Yamamoto (masamoto) * Date: 2015-03-26 15:48
I wrote improved patch to remove the 'si_band'.  This patch modifies the 'n_in_sequence' to conform to the number of structure members.
And I tested manually for struct_siginfo.  struct_siginfo objects builds well.
That's all for now.

$ python3.4.exe
Python 3.4.3 (default, Mar  2 2015, 22:23:56)
[GCC 4.9.2] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import signal
>>> signal.struct_siginfo([1, 2, 3, 4, 5, 6])
signal.struct_siginfo(si_signo=1, si_code=2, si_errno=3, si_pid=4, si_uid=5, si_status=6)
>>> signal.sigwaitinfo({signal.SIGINT})
signal.struct_siginfo(si_signo=2, si_code=6, si_errno=0, si_pid=3352, si_uid=1000, si_status=0)
>>> signal.alarm(1); signal.sigwaitinfo({signal.SIGALRM})
signal.struct_siginfo(si_signo=14, si_code=4, si_errno=0, si_pid=5816, si_uid=1000, si_status=1629189728)
msg239345 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-03-26 17:23
Could you please use a define like SIGINFO_HAS_SI_BAND?

Something like:

#if defined(HAVE_SIGINFO) && !defined(__CYGWIN__)
   /* Issue #21085: In Cygwin, siginfo_t does not have si_band field. */

And please generate patches not the git format. Otherwise, Rietveld is unable to generated the "review" link.
msg239349 - (view) Author: Masayuki Yamamoto (masamoto) * Date: 2015-03-26 19:12

In that case, May I edit configure script to generate the HAVE_* defines?
I'd like to add a statement to check the si_band to

> And please generate patches not the git format. Otherwise, Rietveld is unable to generated the "review" link.
I see.  I use the mercurial repository from next time.
msg239350 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-03-26 19:42
> In that case, May I edit configure script to generate the HAVE_* defines?
> I'd like to add a statement to check the si_band to

Does Cygwin use configure? If yes, go for configure.

You can copy/paste my recent change for dirent.d_type field.

> I see.  I use the mercurial repository from next time.

Are you using git or hg? If you use hg, just change the config to not use
git format. If you use git, don't worry, I can review without the review
msg239663 - (view) Author: Masayuki Yamamoto (masamoto) * Date: 2015-03-31 04:23
New patch uses configure script to set the compile condition for struct_siginfo.si_band. 
The script was generated from using autoreconf.

Could you make sure of having the si_band in another platform?
msg273429 - (view) Author: Erik Bray (erik.bray) * Date: 2016-08-23 09:46
I've run into this recently.  Is there anything I can do to shepherd this issue toward a resolution status?
msg273445 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2016-08-23 13:42
Review the patch, confirm that it works for you (please indicate what cygwin and OS version, etc you test on).  Also review this issue and make sure all open concerns have been addressed by the current patch.
msg273488 - (view) Author: Masayuki Yamamoto (masamoto) * Date: 2016-08-23 16:49
Hello, I'm writer for past patch.
3.4-issue21085-struct_siginfo.patch removes si_band field from struct_siginfo if the C siginfo_t doesn't have si_band field.
This modification raises a incompatibility between platforms having struct_siginfo.
Now, I wrote another patch that doesn't change fields of struct_siginfo to avoid its incompatibility. 
And I built cpython 3.5.2+ on vista cygwin-x86 using this patch.
Murray, would you be able to tell me your idea?
Many thanks.

New patch changes:
If platform has the C siginfo_t structure, but it doesn't have si_band field, the struct_siginfo.si_band field is always assigned zero at function return value.
msg273537 - (view) Author: Masayuki Yamamoto (masamoto) * Date: 2016-08-24 08:08
Oh, I made a mistake that is checking the si_band field without signal header.
Here is a modified patch adding signal header at checking the si_band field.
I passed tests compiling cpython 3.5.2+ on ubuntu 16.04.1 (x86) using this patch.
msg273542 - (view) Author: Erik Bray (erik.bray) * Date: 2016-08-24 08:54
Thanks Masayuki for the updated patch.  I agree, the new approach looks better.  I will review the patch more carefully and test it soon.
msg273907 - (view) Author: Erik Bray (erik.bray) * Date: 2016-08-30 10:09
I've reviewed masamoto's last patch 3.5-issue21085-struct_siginfo-2.patch

It applies cleanly and allows the signals module to compile on Cygwin64 2.5.1 / Windows 10.  I attached versions of the patch that apply cleanly to tip, 3.4, and 3.3 as well.

However, even with this issue resolved it can't be fully tested because there are other open issues preventing a successful build on Cygwin, including issue25658 and issue13756

Would it be ok to commit this even though it doesn't resolve all build issues?  Or should I try to cobble together a meta-issue of current known build issues and make sure they all have working patches first?
msg273915 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2016-08-30 13:15
I think it would be reasonable to apply it, unless other devs object, given your confirmation that it solves this particular problem (and, looking at the code, it won't break anything...which the buildbots will confirm).

This will only be applied to 3.5 and 3.6, since this is not a security issue.  I've updated the versions accordingly.
msg277796 - (view) Author: Roundup Robot (python-dev) Date: 2016-10-01 05:48
New changeset 6874928eae4b by Zachary Ware in branch 'default':
Issue #21085: add configure check for siginfo_t.si_band
msg277797 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2016-10-01 05:52
Thanks for the patch, masamoto, and thanks for the review and rebase, erik.bray!

I only applied this to 3.7.  It's much more open to experimentation currently, and we have a way to go before Python can even be built on Cygwin.  Once we reach a more stable point (say, the full test suite can be run, even if not everything passes), we can evaluate whether backporting all the changes it took to get there is worthwhile.
msg277798 - (view) Author: Roundup Robot (python-dev) Date: 2016-10-01 06:07
New changeset 5673cf852daa by Zachary Ware in branch 'default':
Issue #21085: Fix accidental leading +'s in
msg278027 - (view) Author: Erik Bray (erik.bray) * Date: 2016-10-04 11:09
Thanks for the merge--targeting 3.7 for now and thinking about backporting later sounds fine to me.

I'm also in the process of getting a Cygwin buildbot for Python up and running, but it's been slow going.  That said, having a Cygwin buildbot is also high priority for my own (non-Python-specific) work.  So once I have that up I will happily maintain a buildbot for Python on Cygwin.
msg278037 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2016-10-04 13:51
When you're ready to get your bot set up, ping me and I'll get you set up on the master side.  Thanks!
msg286402 - (view) Author: Decorater (Decorater) * Date: 2017-01-28 06:30
In 3.6 and 3.7 The Same Error is back on line 960 with gcc 6.3.0 on cygwin64. This issue is not entirely fixed even with the absolute latest commits.

$ make
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-pro
totypes    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missin
g-field-initializers   -I. -I./Include    -DPy_BUILD_CORE  -c ./Modules/signalmo
dule.c -o Modules/signalmodule.o
In file included from ./Include/Python.h:85:0,
                 from ./Modules/signalmodule.c:6:
./Modules/signalmodule.c: In function ‘fill_siginfo’:
./Modules/signalmodule.c:960:60: error: ‘siginfo_t {aka struct <anonymous>}’ has
 no member named ‘si_band’; did you mean ‘si_pid’?
     PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
./Include/tupleobject.h:62:75: note: in definition of macro ‘PyTuple_SET_ITEM’
 #define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
./Modules/signalmodule.c:960:5: note: in expansion of macro ‘PyStructSequence_SE
     PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
make: *** [Makefile:1741: Modules/signalmodule.o] Error 1
msg286520 - (view) Author: Erik Bray (erik.bray) * Date: 2017-01-31 09:53
Decorater, since this issue was already closed, could you open a new one?  And when you do, please add me to the nosy list.

I'm still planning to get a Cygwin built bot up for Python, I've just had other various priorities.
Date User Action Args
2017-03-31 16:36:14dstufftsetpull_requests: + pull_request897
2017-01-31 09:53:48erik.braysetmessages: + msg286520
2017-01-28 06:30:21Decoratersetnosy: + Decorater
messages: + msg286402
2016-10-04 13:51:24zach.waresetmessages: + msg278037
2016-10-04 11:09:46erik.braysetmessages: + msg278027
2016-10-01 06:07:04python-devsetmessages: + msg277798
2016-10-01 05:56:18zach.waresettitle: compile error Python3.3 on Cygwin -> Cygwin does not provide siginfo_t.si_band
2016-10-01 05:52:54zach.waresetstatus: open -> closed

assignee: erik.bray -> zach.ware
versions: + Python 3.7, - Python 3.5, Python 3.6
nosy: + zach.ware

messages: + msg277797
resolution: fixed
stage: commit review -> resolved
2016-10-01 05:48:10python-devsetnosy: + python-dev
messages: + msg277796
2016-09-28 19:04:52r.david.murraylinkissue28305 superseder
2016-08-30 13:15:51r.david.murraysetmessages: + msg273915
versions: + Python 3.6, - Python 3.3, Python 3.4
2016-08-30 10:09:03erik.braysetmessages: + msg273907
stage: patch review -> commit review
2016-08-30 10:04:04erik.braysetfiles: + 3.3-issue21085-struct_siginfo-2.patch
2016-08-30 10:03:54erik.braysetfiles: + 3.4-issue21085-struct_siginfo-2.patch
2016-08-30 10:03:42erik.braysetfiles: + tip-issue21085-struct_siginfo-2.patch
2016-08-24 08:54:50erik.braysetassignee: erik.bray
2016-08-24 08:54:37erik.braysetmessages: + msg273542
stage: patch review
2016-08-24 08:08:44masamotosetfiles: + 3.5-issue21085-struct_siginfo-2.patch

messages: + msg273537
2016-08-23 16:49:35masamotosetfiles: + 3.5-issue21085-struct_siginfo.patch

messages: + msg273488
2016-08-23 13:42:13r.david.murraysetmessages: + msg273445
2016-08-23 09:46:22erik.braysetnosy: + erik.bray
messages: + msg273429
2015-03-31 04:23:48masamotosetfiles: + 3.4-issue21085-struct_siginfo.patch

messages: + msg239663
2015-03-26 19:42:14vstinnersetmessages: + msg239350
2015-03-26 19:12:45masamotosetmessages: + msg239349
2015-03-26 17:23:06vstinnersetmessages: + msg239345
2015-03-26 15:48:10masamotosetfiles: + 3.4-issue21085-cygwin-struct_siginfo.patch
versions: + Python 3.5
nosy: + masamoto

messages: + msg239343

type: compile error
2014-04-29 13:37:24dellair.jiesetmessages: + msg217518
2014-04-01 14:23:56dellair.jiesetmessages: + msg215319
2014-04-01 12:28:05vstinnersetfiles: + cygwin_si_band.patch
keywords: + patch
messages: + msg215309
2014-04-01 12:13:34dellair.jiesetmessages: + msg215308
2014-04-01 09:08:47vstinnersetmessages: + msg215303
2014-04-01 09:00:01dellair.jiesetmessages: + msg215302
2014-03-31 20:53:54rpetrovsetmessages: + msg215267
2014-03-31 20:45:32rpetrovsetnosy: + rpetrov
messages: + msg215266
2014-03-31 17:58:52dellair.jiesetmessages: + msg215257
versions: + Python 3.4
2014-03-31 17:20:21loewissetmessages: + msg215252
2014-03-31 16:13:28vstinnersetmessages: + msg215249
2014-03-31 16:11:27vstinnersetmessages: + msg215248
2014-03-31 15:57:25dellair.jiesetfiles: + signalmodule.output.txt

messages: + msg215247
2014-03-31 15:16:21loewissetmessages: + msg215243
2014-03-31 12:27:23dellair.jiesetmessages: + msg215232
2014-03-31 07:49:05dellair.jiesetmessages: + msg215221
2014-03-30 14:45:30loewissetnosy: + loewis
messages: + msg215183
2014-03-28 15:55:46dellair.jiesetmessages: + msg215055
2014-03-28 15:31:19r.david.murraysetnosy: + r.david.murray
messages: + msg215052
2014-03-28 15:27:57vstinnersetnosy: + vstinner
messages: + msg215051
2014-03-28 15:17:09dellair.jiecreate