[Python-3000] Solaris support in 3.0? (original) (raw)
Nicholas Bastin nick.bastin at gmail.com
Wed Sep 5 09:17:39 CEST 2007
- Previous message: [Python-3000] bytes C API in 2.6 for easy transition to 3.0?
- Next message: [Python-3000] Solaris support in 3.0?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This is a combination question-and-status-report email. The question would be, what does the "somewhat" tag mean on Solaris support in the release notes for 3.0a1, and does someone have a list of things that don't work, or does that just mean it hasn't been tested?
I built 3.0a1 on Sparc Solaris (5.8), and except for those things that didn't build for lack of the required dependencies (_bsddb, _hashlib, _ssl, _tkinter, gdbm, ossaudiodev, readline, _curses, _curses_panel), everything claims to have built fine (with gcc 3.4.6).
Unit tests reveal the following failures:
test_cookielib (no _md5) test_fileio test_nis test_pickletools test_pipes test_pty test_str test_unicode test_userstring test_uuid (no _md5)
And the following unexpected (according to it) skips:
test_hashlib (no _md5) test_hmac (no _md5) test_urllib2_localnet (no _md5) test_urllib2net (no _md5) test_urllib2 (no _md5) test_tcl (no tcl on my system) test_sundry (no _md5) test_ssl (no SSL in my configuration) test_tarfile (no _md5) test_unicodedata (no _md5)
If anyone wants more data on any of these particular failures, let me know, otherwise I'm going to start working through the ones that fail in 3.0 that don't fail in 2.6. All of the _md5 failures are because of the lack of SSL, so I'm not sure that the tests should be 'failing' in this configuration.
-- Nick
- Previous message: [Python-3000] bytes C API in 2.6 for easy transition to 3.0?
- Next message: [Python-3000] Solaris support in 3.0?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]