Re: Some test fail on my new Python 2.6
Sorin Schwimmer wrote: > /usr/local/lib is in /etc/ld.so.conf. The files are real. However, > creating symlinks in /usr/lib targeting the libraries in /usr/local/lib, > then recompiling, solved the tkinter problem. So, the conclusion is that > only /usr/lib is consulted for the tcl/tk libraries. Hmm. That's an issue with your linux setup, then, since python uses system facilities to load the shared libraries. I'm wondering if you just needed to run ldconfig...it might be that it hadn't been run since you installed the libraries into /usr/local/lib...though I would think the install process would have done that. > multiprocessing - do I need it? Probably not. I can fork() a new process, > so I can manage. I don't know what am I loosing without multiprocessing. What you loose is the nice interprocesses communication facilities provided by multiprocessing. You might append your system details (including the fact that you have /dev/shm) to that ticket, especially if you think you are going to want to be running cooperating processes that need to do more than just communicate via stdin/out. > htttpservers is still failing the same. > > Everything is done as root. I got failures (different failures) when I tried running that test as root. You might try running it as a regular user, both before and after the install. > I'll move on with make install. > > Thanks for your help; I'm progressing :-) You are welcome. Glad to be able to help out. -- R. David Murray http://www.bitdamce.com -- http://mail.python.org/mailman/listinfo/python-list
Re: Some test fail on my new Python 2.6
Hello again, /usr/local/lib is in /etc/ld.so.conf. The files are real. However, creating symlinks in /usr/lib targeting the libraries in /usr/local/lib, then recompiling, solved the tkinter problem. So, the conclusion is that only /usr/lib is consulted for the tcl/tk libraries. multiprocessing - do I need it? Probably not. I can fork() a new process, so I can manage. I don't know what am I loosing without multiprocessing. socket was solved as suggested, by adding the host name in /etc/hosts, like this: 127.0.0.1 localhost dsr-1 sys doesn't fail anymore after recompilation (have no clue why). htttpservers is still failing the same. Everything is done as root. I'll move on with make install. Thanks for your help; I'm progressing :-) SxN __ Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/ -- http://mail.python.org/mailman/listinfo/python-list
Re: Some test fail on my new Python 2.6
Sorin Schwimmer wrote:
>
> Thanks for the pointers.
>
> Here are some answers:
>
> > Ok, so DBM wasn't built because it couldn't find the external symbol
> > 'dbm_firstkey'. I have no idea off the top of my head why that would
> > happen, but I don't think you really care at the moment since you are
> > trying to get tkinter working. If you do care we can come back to that.
>
> Although I can live without it, I do use sometime dbm. And then, again,
> there are other ways to accomplish the same, so it's not critical.
OK, so we'll come back to it later.
> >> *** WARNING: renaming "_tkinter" since importing it failed: libtk8.5.so:
> >> cannot open shared object file: No such file or directory
>
> > Now, this one is clear. It couldn't find libtk8.5.so when it tried to
> > use _tkinter.so. So either that symlink doesn't exist, or points to a
> > nonexistent library, or there's something wrong with your load library
> > path, so that python isn't finding it when it tries to do the load.
> > If you don't know what that last one means, check out 'man ldconfig'.
>
> # pwd
> /usr/local/lib
> # ls
> libpq.so.4libtcl8.4.so libtclstub8.4.a libtk8.4.so libtkstub8.4.a
> python2.4 tcl8.4 tclConfig.sh tk8.5
> libpq.so.4.0 libtcl8.5.so libtclstub8.5.a libtk8.5.so libtkstub8.5.a
> tcl8 tcl8.5 tk8.4 tkConfig.sh
>
> It's there!
Well, there is _something_ there. Maybe it's a symbolic link that
doesn't point anywhere? Do ls -l, and/or 'file' on it just to check.
The above message is what you would get if it were a symbolic link
that didn't point anywhere valid.
Oh, and make sure /usr/local/lib is in your /etc/ld.so.conf file. If
it isn't, then that's your problem. If you need to update that
file I'm pretty sure you need to run ldconfig afterwards.
> >> test_multiprocessing
> >> test_multiprocessing skipped -- OSError raises on RLock creation, see
> >> issue 3111!
> > According to the referenced bug, this may be a result of your not having
> > /dev/shm mounted, but in any case it is more a bug in the tests than a
> > bug in your system or setup.
>
> # mount
> /dev/hda3 on / type reiserfs (rw,noatime)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> udev on /dev type tmpfs (rw,nosuid)
> devpts on /dev/pts type devpts (rw)
> shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
> usbfs on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85)
>
> It's there, but if it is about a known bug in the test, maybe we should just
> ignore it?
Yeah. Or download 2.6.2c1 and see if that has the same problem. The bug
doesn't say that it was fixed in 2.6.2, and the conditional skip is
still there in the test, but I know Jesse was doing work in that area,
so it might get past it on 2.6.2.
On the other hand, if you aren't using multiprocessing you don't need
to worry about it.
> >> test_socket
> >> test test_socket failed -- Traceback (most recent call last):
> >> File "/install/Python-2.6.1/Lib/test/test_socket.py", line 474, in
> >> testSockName
> >> my_ip_addr = socket.gethostbyname(socket.gethostname())
> >> gaierror: [Errno -2] Name or service not known
> > This probably means that you haven't properly defined 'localhost'
> > in your /etc/hosts file.
>
> # cat /etc/hosts
> # /etc/hosts
> #
> # This file describes a number of hostname-to-address
> # mappings for the TCP/IP subsystem. It is mostly
> # used at boot time, when no name servers are running.
> # On small systems, this file can be used instead of a
> # "named" name server. Just add the names, addresses
> # and any aliases to this file...
> #
>
> 127.0.0.1 localhost
> # IPV6 versions of localhost and co
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
>
>
> There is a localhost definition. Is it not correct?
Yes, but...I just did the functions on my own machine and got this:
Python 2.6.1 (r261:67515, Mar 26 2009, 08:03:17)
[GCC 4.1.2 (Gentoo 4.1.2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> socket.gethostname()
'partner'
>>> socket.gethostbyname('partner')
'127.0.0.1'
So I suspect that you need to add your hostname to the 'localhost' line in
order to get that test to pass. Mine looks like this:
127.0.0.1 partner.bitdance.com partner localhost
I'm inclined to call that a bug in the tests. You could file a bug
report if you feel so moved :)
> >> test_sys
> >> test test_sys failed -- Traceback (most recent call last):
> >> File "/install/Python-2.6.1/Lib/test/test_sys.py", line 354, in
> >> test_43581
> >> self.assert_(sys.__stdout__.encoding == sys.__stderr__.encoding)
> >> AssertionError
> > This one is puzzling. Did you modify 'site.py'? Or perhaps you
> > redirected stdout and stderr to different places and they
> > wound up with different encodings for some reason.
Re: Some test fail on my new Python 2.6
Thanks for the pointers. Here are some answers: > Ok, so DBM wasn't built because it couldn't find the external symbol > 'dbm_firstkey'. I have no idea off the top of my head why that would > happen, but I don't think you really care at the moment since you are > trying to get tkinter working. If you do care we can come back to that. Although I can live without it, I do use sometime dbm. And then, again, there are other ways to accomplish the same, so it's not critical. >> building '_tkinter' extension >> gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall >> -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. >> -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include >> -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 >> -c /install/Python-2.6.1/Modules/_tkinter.c -o >> build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o >> gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall >> -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. >> -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include >> -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 >> -c /install/Python-2.6.1/Modules/tkappinit.c -o >> build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o >> gcc -pthread -shared >> build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o >> build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o >> -L/usr/X11R6/lib64 -L/usr/X11R6/lib -L/usr/local/lib -lBLT -ltk8.5 -ltcl8.5 >> -lX11 -o build/lib.linux-i686-2.6/_tkinter.so >> *** WARNING: renaming "_tkinter" since importing it failed: libtk8.5.so: >> cannot open shared object file: No such file or directory > Now, this one is clear. It couldn't find libtk8.5.so when it tried to > use _tkinter.so. So either that symlink doesn't exist, or points to a > nonexistent library, or there's something wrong with your load library > path, so that python isn't finding it when it tries to do the load. > If you don't know what that last one means, check out 'man ldconfig'. # pwd /usr/local/lib # ls libpq.so.4libtcl8.4.so libtclstub8.4.a libtk8.4.so libtkstub8.4.a python2.4 tcl8.4 tclConfig.sh tk8.5 libpq.so.4.0 libtcl8.5.so libtclstub8.5.a libtk8.5.so libtkstub8.5.a tcl8 tcl8.5 tk8.4 tkConfig.sh It's there! >> test_multiprocessing >> test_multiprocessing skipped -- OSError raises on RLock creation, see issue >> 3111! > According to the referenced bug, this may be a result of your not having > /dev/shm mounted, but in any case it is more a bug in the tests than a > bug in your system or setup. # mount /dev/hda3 on / type reiserfs (rw,noatime) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) udev on /dev type tmpfs (rw,nosuid) devpts on /dev/pts type devpts (rw) shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev) usbfs on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85) It's there, but if it is about a known bug in the test, maybe we should just ignore it? >> test_socket >> test test_socket failed -- Traceback (most recent call last): >> File "/install/Python-2.6.1/Lib/test/test_socket.py", line 474, in >> testSockName >> my_ip_addr = socket.gethostbyname(socket.gethostname()) >> gaierror: [Errno -2] Name or service not known > This probably means that you haven't properly defined 'localhost' > in your /etc/hosts file. # cat /etc/hosts # /etc/hosts # # This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. Just add the names, addresses # and any aliases to this file... # 127.0.0.1 localhost # IPV6 versions of localhost and co ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts There is a localhost definition. Is it not correct? >> test_sys >> test test_sys failed -- Traceback (most recent call last): >> File "/install/Python-2.6.1/Lib/test/test_sys.py", line 354, in test_43581 >> self.assert_(sys.__stdout__.encoding == sys.__stderr__.encoding) >> AssertionError > This one is puzzling. Did you modify 'site.py'? Or perhaps you > redirected stdout and stderr to different places and they > wound up with different encodings for some reason. In which > case that one would be a bug in the tests as well. No, I didn't, nor have I done anything with stdout, stderror. When I ran the test, I did a make test | tee test.rez, which in my mind should have been harmless. The output for individual test_httpservers was posted here: http://mail.python.org/pipermail/python-list/2009-April/708041.html Thanks again SxN __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark
Re: Some test fail on my new Python 2.6
Sorin Schwimmer wrote: > > I wanted to replace my old Python 2.4 and tcl/tk 8.4 with tcl/tk 8.5.6 and > Python 2.6, mainly so that I can enjoy ttk. tcl/tk was installed from sources > without any problem, I started a wish and worked. > > Now, for the Python, here are all the issues signaled by make test: > > running build > running build_ext > building 'dbm' extension > gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall > -Wstrict-prototypes -DHAVE_GDBM_NDBM_H -I. -I/install/Python-2.6.1/./Include > -I. -IInclude -I./Include -I/usr/local/include > -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 -c > /install/Python-2.6.1/Modules/dbmmodule.c -o > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/dbmmodule.o > gcc -pthread -shared > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/dbmmodule.o > -L/usr/local/lib -lgdbm -o build/lib.linux-i686-2.6/dbm.so > *** WARNING: renaming "dbm" since importing it failed: > build/lib.linux-i686-2.6/dbm.so: undefined symbol: dbm_firstkey Ok, so DBM wasn't built because it couldn't find the external symbol 'dbm_firstkey'. I have no idea off the top of my head why that would happen, but I don't think you really care at the moment since you are trying to get tkinter working. If you do care we can come back to that. > building '_tkinter' extension > gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall > -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. > -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include > -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 > -c /install/Python-2.6.1/Modules/_tkinter.c -o > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o > gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall > -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. > -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include > -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 > -c /install/Python-2.6.1/Modules/tkappinit.c -o > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o > gcc -pthread -shared > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o > build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o > -L/usr/X11R6/lib64 -L/usr/X11R6/lib -L/usr/local/lib -lBLT -ltk8.5 -ltcl8.5 > -lX11 -o build/lib.linux-i686-2.6/_tkinter.so > *** WARNING: renaming "_tkinter" since importing it failed: libtk8.5.so: > cannot open shared object file: No such file or directory Now, this one is clear. It couldn't find libtk8.5.so when it tried to use _tkinter.so. So either that symlink doesn't exist, or points to a nonexistent library, or there's something wrong with your load library path, so that python isn't finding it when it tries to do the load. If you don't know what that last one means, check out 'man ldconfig'. > Failed to find the necessary bits to build these modules: > _sqlite3 bsddb185 sunaudiodev Here you presumably don't have these libraries installed, so no real problem. > To find the necessary bits, look in setup.py in detect_modules() for the > module's name. > > > Failed to build these modules: > _tkinter dbm These we covered above. Most of the stuff you show from the test run is expected output for one reason or another. The ones that aren't... > test_multiprocessing > test_multiprocessing skipped -- OSError raises on RLock creation, see issue > 3111! According to the referenced bug, this may be a result of your not having /dev/shm mounted, but in any case it is more a bug in the tests than a bug in your system or setup. > test_socket > test test_socket failed -- Traceback (most recent call last): > File "/install/Python-2.6.1/Lib/test/test_socket.py", line 474, in > testSockName > my_ip_addr = socket.gethostbyname(socket.gethostname()) > gaierror: [Errno -2] Name or service not known This probably means that you haven't properly defined 'localhost' in your /etc/hosts file. > test_sys > test test_sys failed -- Traceback (most recent call last): > File "/install/Python-2.6.1/Lib/test/test_sys.py", line 354, in test_43581 > self.assert_(sys.__stdout__.encoding == sys.__stderr__.encoding) > AssertionError This one is puzzling. Did you modify 'site.py'? Or perhaps you redirected stdout and stderr to different places and they wound up with different encodings for some reason. In which case that one would be a bug in the tests as well. > test_tcl > test_tcl skipped -- No module named _tkinter This is a result of the build failure. > 320 tests OK. > 3 tests failed: > test_httpservers test_socket test_sys So we understand test_socket and maybe test_sys. You'll have to show me the output of test_httpsservers run in verbose mode again to see if I can make sense of that one, if you care. > 38 tests skipped: > test_aepack test_al test_applesingle test_bsddb185 tes
Re: Some test fail on my new Python 2.6
I wanted to replace my old Python 2.4 and tcl/tk 8.4 with tcl/tk 8.5.6 and Python 2.6, mainly so that I can enjoy ttk. tcl/tk was installed from sources without any problem, I started a wish and worked. Now, for the Python, here are all the issues signaled by make test: running build running build_ext building 'dbm' extension gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DHAVE_GDBM_NDBM_H -I. -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 -c /install/Python-2.6.1/Modules/dbmmodule.c -o build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/dbmmodule.o gcc -pthread -shared build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/dbmmodule.o -L/usr/local/lib -lgdbm -o build/lib.linux-i686-2.6/dbm.so *** WARNING: renaming "dbm" since importing it failed: build/lib.linux-i686-2.6/dbm.so: undefined symbol: dbm_firstkey building '_tkinter' extension gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 -c /install/Python-2.6.1/Modules/_tkinter.c -o build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11R6/include -I. -I/install/Python-2.6.1/./Include -I. -IInclude -I./Include -I/usr/local/include -I/install/Python-2.6.1/Include -I/install/Python-2.6.1 -c /install/Python-2.6.1/Modules/tkappinit.c -o build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o gcc -pthread -shared build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/_tkinter.o build/temp.linux-i686-2.6/install/Python-2.6.1/Modules/tkappinit.o -L/usr/X11R6/lib64 -L/usr/X11R6/lib -L/usr/local/lib -lBLT -ltk8.5 -ltcl8.5 -lX11 -o build/lib.linux-i686-2.6/_tkinter.so *** WARNING: renaming "_tkinter" since importing it failed: libtk8.5.so: cannot open shared object file: No such file or directory Failed to find the necessary bits to build these modules: _sqlite3 bsddb185 sunaudiodev To find the necessary bits, look in setup.py in detect_modules() for the module's name. Failed to build these modules: _tkinter dbm running build_scripts find ./Lib -name '*.py[co]' -print | xargs rm -f ./python -E -tt ./Lib/test/regrtest.py -l test_aepack test_aepack skipped -- No module named aepack test_al test_al skipped -- No module named al test_applesingle test_applesingle skipped -- No module named macostools test_bsddb185 test_bsddb185 skipped -- No module named bsddb185 test_bsddb3 test_bsddb3 skipped -- Use of the `bsddb' resource not enabled test_cd test_cd skipped -- No module named cd test_cl test_cl skipped -- No module named cl test_codecmaps_cn test_codecmaps_cn skipped -- Use of the `urlfetch' resource not enabled test_codecmaps_hk test_codecmaps_hk skipped -- Use of the `urlfetch' resource not enabled test_codecmaps_jp test_codecmaps_jp skipped -- Use of the `urlfetch' resource not enabled test_codecmaps_kr test_codecmaps_kr skipped -- Use of the `urlfetch' resource not enabled test_codecmaps_tw test_codecmaps_tw skipped -- Use of the `urlfetch' resource not enabled test_curses test_curses skipped -- Use of the `curses' resource not enabled test_dbm test_dbm skipped -- No module named dbm test_gl test_gl skipped -- No module named gl test_httpservers test test_httpservers failed -- errors occurred; run in verbose mode for details test_imgfile test_imgfile skipped -- No module named imgfile test_kqueue test_kqueue skipped -- test works only on BSD test_linuxaudiodev test_linuxaudiodev skipped -- Use of the `audio' resource not enabled test_macos test_macos skipped -- No module named MacOS test_macostools test_macostools skipped -- No module named macostools test_multiprocessing test_multiprocessing skipped -- OSError raises on RLock creation, see issue 3111! test_normalization test_normalization skipped -- Use of the `urlfetch' resource not enabled test_ossaudiodev test_ossaudiodev skipped -- Use of the `audio' resource not enabled test_pep277 test_pep277 skipped -- test works only on NT+ test_py3kwarn test_py3kwarn skipped -- test.test_py3kwarn must be run with the -3 flag test_scriptpackages test_scriptpackages skipped -- No module named aetools test_socket test test_socket failed -- Traceback (most recent call last): File "/install/Python-2.6.1/Lib/test/test_socket.py", line 474, in testSockName my_ip_addr = socket.gethostbyname(socket.gethostname()) gaierror: [Errno -2] Name or service not known test_socketserver test_socketserver skipped -- Use of the `network' resource not enabled test_sqlite test_sqlite skipped -- no sqlite available test_startfile test_startfile skipped -- cannot import name startfile t
Re: Some test fail on my new Python 2.6
Sorin Schwimmer wrote: > > > Run 'make test' instead of running them one by one. > > I did it *before* going one by one. I then tried individual tests in hope of > getting hints of what to look for. Actualy, for the first three tests, the > "make test" script commented that it is unusual for them to fail on my > platform (linux2). Oh, yeah, I forgot that bit. The _tkinter error means you don't have TCL/TK installed. Not a problem unless you want to use tkinter. Unfortunately I forget what your other errors were. Can you just post the Skip messages (and any real errors) from the make test run? I can run through them quickly for you then, and then we can focus on the ones that are the real errors. -- R. David Murray http://www.bitdance.com -- http://mail.python.org/mailman/listinfo/python-list
Re: Some test fail on my new Python 2.6
> Run 'make test' instead of running them one by one. I did it *before* going one by one. I then tried individual tests in hope of getting hints of what to look for. Actualy, for the first three tests, the "make test" script commented that it is unusual for them to fail on my platform (linux2). SxN __ Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/ -- http://mail.python.org/mailman/listinfo/python-list
