Re: [Metakit] Mk4py build test Q
Hello Jack, (thanks for your help on test.py vs. mktest.py) If you rename test.py to mktest.py you should be able to use both of them. I saw the mktest.py rename in CVS, and it almost works for me. I get the 'freebsd4' suite of tests (on debian linux) which tries to include a stdlib test module that only applies to freebsd. I haven't looked at it any closer, but I would guess something in CVS has a hard definition for freebsd. I've just checked in some more changes and a few files I missed for Mk4py testing. The tests now seem to work on Linux. I've not found anything specific for FreeBSD so far. It may be caused by something which is Mac OS X specific, which is also *BSD-ish. -jcw _ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
[Metakit] Mk4py build test Q
I have a question for Python experts, w.r.t. distutils: I'd like to try and get setup.py working on its own. Here's what I get right now (cvs HEAD, build dir wiped): $ python setup.py build running build running build_py creating ../builds/lib.linux-i686-2.3 copying metakit.py - ../builds/lib.linux-i686-2.3 running build_ext running config gcc -E -I/usr/include/python2.3 -o _configtest.i _configtest.c removing: _configtest.c _configtest.i building 'Mk4py' extension creating ../builds/temp.linux-i686-2.3 creating ../builds/temp.linux-i686-2.3/scxx g++ -fno-strict-aliasing -DNDEBUG -fPIC -DHAVE_UNICODEOBJECT_H=1 -Iscxx -I../include -I/usr/include/python2.3 -c PyView.cpp -o ../builds/temp.linux-i686-2.3/PyView.o [...] g++ -pthread -shared ../builds/temp.linux-i686-2.3/PyProperty.o ../builds/temp.linux-i686-2.3/PyRowRef.o ../builds/temp.linux-i686-2.3/PyStorage.o ../builds/temp.linux-i686-2.3/PyView.o ../builds/temp.linux-i686-2.3/scxx/PWOImp.o ../builds/column.o ../builds/custom.o ../builds/derived.o ../builds/fileio.o ../builds/field.o ../builds/format.o ../builds/handler.o ../builds/persist.o ../builds/remap.o ../builds/std.o ../builds/store.o ../builds/string.o ../builds/table.o ../builds/univ.o ../builds/view.o ../builds/viewx.o -lstdc++ -o ../builds/lib.linux-i686-2.3/Mk4py.so g++: ../builds/column.o: No such file or directory [...] g++: ../builds/viewx.o: No such file or directory error: command 'g++' failed with exit status 1 $ Is there a simple way to resolve this? The workaround is to first do: cd ../builds; ../unix/configure; make The other issue I ran into is testing: $ python setup.py test running test running build running build_py running build_ext running config gcc -E -I/usr/include/python2.3 -o _configtest.i _configtest.c removing: _configtest.c _configtest.i Traceback (most recent call last): File setup.py, line 184, in ? extra_objects=mkobjs, File /usr/lib/python2.3/distutils/core.py, line 149, in setup dist.run_commands() File /usr/lib/python2.3/distutils/dist.py, line 907, in run_commands self.run_command(cmd) File /usr/lib/python2.3/distutils/dist.py, line 927, in run_command cmd_obj.run() File setup.py, line 133, in run import test.regrtest ImportError: No module named regrtest $ (Am using 2.3.3 on Linux, btw) It went away when I disable the line in setup.py: #sys.path.insert(0, self.test_dir) But then it seems to get lost in finding other stuff: $ python setup.py test running test running build running build_py running build_ext running config gcc -E -I/usr/include/python2.3 -o _configtest.i _configtest.c removing: _configtest.c _configtest.i test_inttypes test_inttypes skipped -- No module named test_inttypes 1 test skipped: test_inttypes 1 skip unexpected on linux2: test_inttypes $ -jcw _ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
Re: [Metakit] Mk4py build test Q
On Sat, Apr 24, 2004 at 01:42:48PM +0200, Jean-Claude Wippler wrote: I have a question for Python experts, w.r.t. distutils: The other issue I ran into is testing: $ python setup.py test running test running build running build_py running build_ext running config gcc -E -I/usr/include/python2.3 -o _configtest.i _configtest.c removing: _configtest.c _configtest.i Traceback (most recent call last): File setup.py, line 184, in ? extra_objects=mkobjs, File /usr/lib/python2.3/distutils/core.py, line 149, in setup dist.run_commands() File /usr/lib/python2.3/distutils/dist.py, line 907, in run_commands self.run_command(cmd) File /usr/lib/python2.3/distutils/dist.py, line 927, in run_command cmd_obj.run() File setup.py, line 133, in run import test.regrtest ImportError: No module named regrtest $ There is a naming conflict between the stdlib test module and your test.py # python Python 2.3.3 (#2, Feb 24 2004, 09:29:20) Type help, copyright, credits or license for more information. import test test module 'test' from '/usr/lib/python2.3/test/__init__.pyc' # python Python 2.3.3 (#2, Feb 24 2004, 09:29:20) Type help, copyright, credits or license for more information. import sys sys.path.insert(0, './test/') import test test module 'test' from './test/test.pyc' If you rename test.py to mktest.py you should be able to use both of them. -jackdied _ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
