rc1 available

11 views
Skip to first unread message

Oliver

unread,
Dec 29, 2013, 3:44:17 PM12/29/13
to pypu...@googlegroups.com
Following the user feedback for 3.3.0dev1, only needed one patch for a regression: could no longer add/remove listeners while sendMessage in progress. No other mods. Latest is 3.3.0rc1 available via 

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


Jérôme Laheurte

unread,
Jan 4, 2014, 8:39:47 AM1/4/14
to pypu...@googlegroups.com
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.

Cheers
Jérôme

oliver

unread,
Jan 4, 2014, 10:53:04 AM1/4/14
to PyPubSub
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? 

Oliver


 



Oliver
Contributor to Open Source: PyPubSub, Lua-iCxx, iof
Contributor to StackOverflow



--
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.

Jérôme Laheurte

unread,
Jan 4, 2014, 11:12:24 AM1/4/14
to pypu...@googlegroups.com

Le 4 janv. 2014 à 16:53, oliver <oliver.s...@gmail.com> a écrit :

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.

Cheers
Jérôme

Jérôme Laheurte

unread,
Jan 4, 2014, 12:12:05 PM1/4/14
to pypu...@googlegroups.com
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:


Cheers
Jérôme


oliver

unread,
Jan 5, 2014, 9:32:27 AM1/5/14
to PyPubSub

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:


Cheers
Jérôme


Good find. I read that bug report and associated threads. Rather unnerving to think that an SVN checkout can become invalid because of SVN keyword expansion, and it depends in what month you did the checkout! I removed them (only one file affected): the inconvenience outweighs the benefit. Thanks for looking into this. Cheers, 
Oliver

oliver

unread,
Jan 7, 2014, 11:09:40 AM1/7/14
to PyPubSub

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.

Cheers
Jérôme


Hi 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 Laheurte

unread,
Jan 9, 2014, 2:50:44 PM1/9/14
to pypu...@googlegroups.com
Le 7 janv. 2014 à 17:09, oliver <oliver.s...@gmail.com> a écrit :



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.

Cheers
Jérôme


Hi 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. 

Yep, just saw them.


BTW would it be possible to get an email when the build succeeds? I only see emails about build failures ;)

Of course. It should work now.

Cheers
Jérôme


oliver

unread,
Jan 11, 2014, 12:05:31 AM1/11/14
to PyPubSub
Great. Not seeing the success email yet, but perhaps because there hasn't been a mod to SVN. Is there a way to force a re-test without creating a bogus edit to repo? (and I don't remember what it looks at to determine when test required, is it just the tests folder, or are there others)

Oliver
Contributor to Open Source: PyPubSub, Lua-iCxx, iof
Contributor to StackOverflow



Jérôme Laheurte

unread,
Jan 11, 2014, 5:19:22 AM1/11/14
to pypu...@googlegroups.com

Le 11 janv. 2014 à 06:05, oliver <oliver.s...@gmail.com> a écrit :

> Great. Not seeing the success email yet, but perhaps because there hasn't been a mod to SVN. Is there a way to force a re-test without creating a bogus edit to repo? (and I don't remember what it looks at to determine when test required, is it just the tests folder, or are there others)

A build is launched on each commit, whatever the changes. You can force a build when you’re logged on; I’ll send you the credentials by e-mail. When logged in, click on a builder (third line in the waterfall’s headers), fill in your name and click the ‘force’ button.

Cheers
Jérôme

oliver

unread,
Jan 11, 2014, 11:12:21 PM1/11/14
to PyPubSub
Thanks I logged on and forced rebuild and it worked, message is on the pypubsub_dev group, awesome! 

Oliver
Contributor to Open Source: PyPubSub, Lua-iCxx, iof
Contributor to StackOverflow




Cheers
Jérôme

Reply all
Reply to author
Forward
0 new messages