pip install --pre pypubsub
Added regression unit test that showed failure. All regression tests now pass for 2.6, 2.7, 3.2, 3.3, and 3.4a4. I will release 3.3.0 mid-January unless there is any major problem identified via user testing. Cheers,
Oliver
--
You received this message because you are subscribed to the Google Groups "pypubsub" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pypubsub+u...@googlegroups.com.
To post to this group, send email to pypu...@googlegroups.com.
Visit this group at http://groups.google.com/group/pypubsub.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Jerome, thanks for the update. This is strange. The output shows three errors, one from each of three files, with the same stacktrace at lowest level:File "/Users/fraca7/BuildslavePubsub/osx/build/src/pubsub/__init__.py", line 8
SyntaxError: Non-ASCII character '\xc3' in file /Users/fraca7/BuildslavePubsub/osx/build/src/pubsub/__init__.py on line 9, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
However, I checked the pubsub/__init__.py in lines 8 and 9 and there is no character that starts with \xc3 AFAICT from notepad++ "show all characters" with ASCII encoding. Also, why would this happen in only some cases, since the error is unicode related.Can you post the file (as an attachment) as it is on the server?
No need to, I found the culprit. The « $Date$ » is expanded to something containing a localized short date on checkout. Since my system is in French, that introduces non-ASCII characters depending on the month of the last file modification; November was OK (« Novembre ») but not December (« Décembre »)…Specifying an encoding will not do the trick since the different slaves are not guaranteed to use the same one by default… I’ll try to force the build slaves to run with an English locale instead.It works… Except for Windows, where I had to change the whole system date preferences, but whatever. Not the first time it happens to somebody either:CheersJérôme
There seems to be a problem on the buildbot:Doesn’t happen on the Fedora and OpenSuse slaves but those are old and running Python 2.6 I think.Speaking of the buildbot, it should send a mail notification to this list when a build fails but this doesn’t seem to work. I just changed the From: field to the address I used to subscribe, maybe that will fix it.CheersJérôme
There seems to be a problem on the buildbot:Doesn’t happen on the Fedora and OpenSuse slaves but those are old and running Python 2.6 I think.Speaking of the buildbot, it should send a mail notification to this list when a build fails but this doesn’t seem to work. I just changed the From: field to the address I used to subscribe, maybe that will fix it.CheersJérômeHi Jerome, just wanted to update you that I just released some posts by you that had somehow been blocked by the pypubsub_dev server, strange because you were listed as a member. Anyways, that's probably why you didn't see the buildbot results posted, hopefully next time these posts will go through without delay.
BTW would it be possible to get an email when the build succeeds? I only see emails about build failures ;)
Cheers
Jérôme