No buildbot to test wide unicode?
Hello, It seems that there is no buildbot to test a wide unicode build. On http://www.python.org/dev/buildbot/3.x/ all outputs of the "configure" steps show this message:: checking what type to use for str... unsigned short which looks like a ucs2 build to me. Since wide unicode is the standard chosen by some Linux distributions, it would make sense to have at least one buildbot running with --with-wide-unicode (3.x) or --enable-unicode=ucs4 (2.x). -- Amaury Forgeot d'Arc
It seems that there is no buildbot to test a wide unicode build.
On http://www.python.org/dev/buildbot/3.x/ all outputs of the "configure" steps show this message:: checking what type to use for str... unsigned short which looks like a ucs2 build to me.
Since wide unicode is the standard chosen by some Linux distributions, it would make sense to have at least one buildbot running with --with-wide-unicode (3.x) or --enable-unicode=ucs4 (2.x).
Can you propose some (one? two? more?) systems that might be best as candidates? I'd then setup two (sets of) builders; they would share the slave lock, so builds would run sequentially (unless the slave operator agrees to setup two slaves on one machine). Regards, Martin
Le Wed, 04 Nov 2009 20:08:58 +0100, Martin v. Löwis a écrit :
Since wide unicode is the standard chosen by some Linux distributions, it would make sense to have at least one buildbot running with --with-wide-unicode (3.x) or --enable-unicode=ucs4 (2.x).
Can you propose some (one? two? more?) systems that might be best as candidates? I'd then setup two (sets of) builders; they would share the slave lock, so builds would run sequentially (unless the slave operator agrees to setup two slaves on one machine).
I would certainly agree to setup two slaves on mine. There are ample resources available. Regards Antoine.
On Thu, 5 Nov 2009 at 16:06, Antoine Pitrou wrote:
Le Wed, 04 Nov 2009 20:08:58 +0100, Martin v. Löwis a écrit :
Since wide unicode is the standard chosen by some Linux distributions, it would make sense to have at least one buildbot running with --with-wide-unicode (3.x) or --enable-unicode=ucs4 (2.x).
Can you propose some (one? two? more?) systems that might be best as candidates? I'd then setup two (sets of) builders; they would share the slave lock, so builds would run sequentially (unless the slave operator agrees to setup two slaves on one machine).
I would certainly agree to setup two slaves on mine. There are ample resources available.
I could do so as well. Gentoo is one of the distributions that uses the wide build by default, so that would make it a good test candidate as well. --David
I would certainly agree to setup two slaves on mine. There are ample resources available.
I could do so as well. Gentoo is one of the distributions that uses the wide build by default, so that would make it a good test candidate as well.
I have now setup two slaves, murray-gentoo-wide and pitrou-ubuntu-wide, same passwords. They configure with the option "--with-wide-unicode" (if I did that correctly). I think this means that the 2.x branches will have to grow this option also (although configure should ignore the option, so it should still build). Regards, Martin
participants (4)
-
"Martin v. Löwis" -
Amaury Forgeot d'Arc -
Antoine Pitrou -
R. David Murray