Mailman 3 January 2003 - Pythonmac-SIG

one fallout of cr/lf code
by Magladry, Stephen March 21, 2003

March 21, 2003

It is nice to be able to run PC Python code unchanged thanks to the code change made to handle cr/lf within the Mac Python code. I have run into one problem through. The cr/lf is view as two separate lines. The following code, --test.py from a pc---- import sys <cr><lf> sys.blah<cr><lf> --test.py from a pc---- returns the following error: File "test.py", line 3 in ? AttributeError: 'module' object has no attribute 'blah' Okay I can deal with doubling of the line number, that's not much of a problem. The real problem is with line continuations. --test2.py from a pc---- x = x\ <cr><lf> +1<cr><lf> --test2.py from a pc---- This code is not able to execute. The line continuation "works" on the <lf>. The <cr> is seen as a new line. Now without a continuation, Mac Python isn't able to correctly process it. I can "fix" my problems my doing the following. --fixedTest2.py from a pc---- x = (x <cr><lf> +1)<cr><lf> --fixedTest2.py from a pc---- Since an expression gets started with the "(", line continuation come for free. This is fine and dandy for cross platform code that I own and work with. It might be more of a problem with Python code one would get from some PC user, though. Don't know if we can do anything about this. If not, consider this as a FYI for those people working in a cross platform environment. Sincerely, Stephen Magladry

4 5

Re: [Pythonmac-SIG] ObjC stuff
by Jack Jansen March 20, 2003

March 20, 2003

Recently, Steve Spicklemire <steve(a)spvi.com> said: > So it's in CVS somewhere? I'll do a check-out and see if I can find it. I don't know, Steven Majewski may know (I think he is the one who looked at it). If it isn't in the repository it probably should be, preferrably in the Modules directory (because it is useful for non-Mac users) but if there's objections against that we'll put it in the Mac/Modules dir. > I just ordered CW-6 today so I might be able to pitch in a bit. While very useful for other things (like MacPython development) you don't need it for OSX unix-Python development: this is all make and gcc-based (and you have those on your OSX developer disc). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

5 4

Building Mac extensions for Apple Python
by Kevin Ollivier Feb. 10, 2003

Feb. 10, 2003

Hi all, I've taken some time out to try out the new MacPython extensions to Apple's included Python, but I'm getting errors when trying to build. I'm on a TiBook 1 GHz running 10.2.3 and I do have the MachOPython 2.2 framework install for wxPython support. I'm wondering if this could be interfering in some way, and if so, should I remove the framework MachOPython completely or build the latest version? Following the steps in README.jaguar and running make -f Makefile.jaguar gives the following output: /usr/bin/install -c -d -m 755 /./Applications/MacPython-OSX-2.2 /usr/bin/install -c -d -m 755 /./Applications/MacPython-OSX-2.2/python-additions /usr/bin/install -c -d -m 755 /./Applications/MacPython-OSX-2.2/python-additions/lib-dynload /usr/bin/python ../../Mac/OSX/setup.jaguar.py install --install-lib=/./Applications/MacPython-OSX-2.2/python-additions/lib- dynload running install running build running build_ext building 'OverrideFrom23._AE' extension gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp -I../../Mac/Include -I/usr/include/python2.2 -c ../../Mac/Modules/ae/_AEmodule.c -o build/temp.darwin-6.3-Power Macintosh-2.2/_AEmodule.o ../../Mac/Modules/ae/_AEmodule.c:922: `PyObject_Del' undeclared here (not in a function) ../../Mac/Modules/ae/_AEmodule.c:922: initializer element is not constant ../../Mac/Modules/ae/_AEmodule.c:922: (near initialization for `AEDesc_Type.tp_free') error: command 'gcc' failed with exit status 1 Any help/advice would be greatly appreciated! Thanks, Kevin

4 6

New MacPython-OSX 2.3a1 binary
by Robin Dunn Jan. 31, 2003

Jan. 31, 2003

Ok, I've just uploaded a new MacPython binary to https://sourceforge.net/project/showfiles.php?group_id=10718 This one should fix the link problem with the _bsddb module, and also includes the (ug!) tkinter extension module. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!

4 11

threads & sockets crash MacPython 2.2.2 (was ...2.2.1)
by Marcus Mendenhall Jan. 31, 2003

Jan. 31, 2003

My previous message about a crash in MacPython 2.2.1 was really in 2.2.2, if it makes any difference. Sorry. Marcus Mendenhall

1 0

threads & sockets crash MacPython 2.2.1
by Marcus Mendenhall Jan. 31, 2003

Jan. 31, 2003

I am experimenting with multithreaded code and sockets to consider building a distributed control system for our Free Electron Laser using python. The following fairly straightforward snippet causes a crash and traceback, which it doesn't do with the Unix build of python. from threading import * import time import socket import SocketServer import traceback socketno=8000 def request_handler(request, client, server_self): print client, request class myserver(SocketServer.UDPServer): allow_reuse_address=1 def serve(self): try: print "threaded server running." while(1): self.handle_request() except: traceback.print_exc() server=myserver(('',socketno), request_handler) try: server_thread=Thread(target=server.serve, name="Server") server_thread.start() time.sleep(0.1) print "server up!" s=socket.socket(socket.AF_INET, socket.SOCK_DGRAM) s.connect(('127.0.0.1',socketno)) for i in range(20): s.send('packet %d\n' % i) time.sleep(0.001) finally: time.sleep(0.1) #allow threads to rationalize server.socket.close() #force server down del server the crash happens when I try to force the server down with the server.socket.close(). Here is the traceback: ********** Date/Time: 2003-01-31 09:24:11 -0600 OS Version: 10.2.3 (Build 6G30) Host: mendenhall.fel.Vanderbilt.Edu Command: Python IDE PID: 6018 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000058 Thread 0: #0 0x90073c48 in mach_msg_trap #1 0x90005f90 in mach_msg #2 0x9022a75c in SwitchContexts #3 0x90225008 in YieldToThread #4 0x9022abbc in YieldToAnyThread #5 0x001cdf44 in 0x1cdf44 #6 0x0020c168 in 0x20c168 #7 0x0020c070 in 0x20c070 #8 0x0020bfe8 in 0x20bfe8 #9 0x0020cb64 in 0x20cb64 #10 0x002111f4 in 0x2111f4 #11 0x002381c0 in 0x2381c0 #12 0x00238134 in mac_1str #13 0x002380a8 in mac_chdir #14 0x001fc004 in PyCFunction_Call #15 0x00259ea8 in 0x259ea8 #16 0x00256278 in PyEval_EvalCodeEx #17 0x0025d3dc in fast_function #18 0x00259f94 in 0x259f94 #19 0x00256278 in PyEval_EvalCodeEx #20 0x0025d3dc in fast_function #21 0x00259f94 in 0x259f94 #22 0x00256278 in PyEval_EvalCodeEx #23 0x0025597c in function_call #24 0x001da51c in PyObject_Call #25 0x00255238 in instancemethod_call #26 0x001da51c in PyObject_Call #27 0x001d59e4 in PyEval_CallObjectWithKeywords #28 0x002b8024 in builtin_apply #29 0x001fc004 in PyCFunction_Call #30 0x00259ea8 in 0x259ea8 #31 0x00256278 in PyEval_EvalCodeEx #32 0x0025d3dc in fast_function #33 0x00259f94 in 0x259f94 #34 0x00256278 in PyEval_EvalCodeEx #35 0x0025d3dc in fast_function #36 0x00259f94 in 0x259f94 #37 0x00256278 in PyEval_EvalCodeEx #38 0x0025d3dc in fast_function #39 0x00259f94 in 0x259f94 #40 0x00256278 in PyEval_EvalCodeEx #41 0x0025d3dc in fast_function #42 0x00259f94 in 0x259f94 #43 0x00256278 in PyEval_EvalCodeEx #44 0x0025d3dc in fast_function #45 0x00259f94 in 0x259f94 #46 0x00256278 in PyEval_EvalCodeEx #47 0x0025d3dc in fast_function #48 0x00259f94 in 0x259f94 #49 0x00256278 in PyEval_EvalCodeEx #50 0x0025d3dc in fast_function #51 0x00259f94 in 0x259f94 #52 0x00256278 in PyEval_EvalCodeEx #53 0x0025d3dc in fast_function #54 0x00259f94 in 0x259f94 #55 0x00256278 in PyEval_EvalCodeEx #56 0x0025597c in function_call #57 0x001da51c in PyObject_Call #58 0x00255238 in instancemethod_call #59 0x001da51c in PyObject_Call #60 0x001d59e4 in PyEval_CallObjectWithKeywords #61 0x00296078 in PyInstance_New #62 0x001da51c in PyObject_Call #63 0x0025d000 in do_call #64 0x00259fac in 0x259fac #65 0x00256278 in PyEval_EvalCodeEx #66 0x0025eb70 in PyEval_EvalCode #67 0x002a7638 in PyImport_ExecCodeModuleEx #68 0x002a6060 in load_source_module #69 0x00217d24 in load_module #70 0x00217760 in import_submodule #71 0x00217198 in load_next #72 0x00216a38 in import_module_ex #73 0x001d6704 in PyImport_ImportModuleEx #74 0x002b7e64 in builtin___import__ #75 0x001fc004 in PyCFunction_Call #76 0x001da51c in PyObject_Call #77 0x001d59e4 in PyEval_CallObjectWithKeywords #78 0x002599dc in 0x2599dc #79 0x00256278 in PyEval_EvalCodeEx #80 0x0025eb70 in PyEval_EvalCode #81 0x002a7638 in PyImport_ExecCodeModuleEx #82 0x002bf824 in PyImport_ExecCodeModule #83 0x002c9578 in run_main_resource #84 0x002c9440 in PyMac_InitApplet #85 0x0019c1cc in main Thread 1: #0 0x9003eaa8 in semaphore_wait_signal_trap #1 0x9003e8c4 in _pthread_cond_wait #2 0x90233368 in TSWaitOnSemaphoreCommon #3 0x90248a10 in AsyncFileThread(void*) #4 0x90020d48 in _pthread_body Thread 2: #0 0x90042688 in semaphore_timedwait_signal_trap #1 0x9003e8b4 in _pthread_cond_wait #2 0x9022ffd4 in MPWaitOnQueue #3 0x90736fc4 in TNodeSyncTask::SyncTaskProc(void*) #4 0x9025e3dc in PrivateMPEntryPoint #5 0x90020d48 in _pthread_body Thread 3: #0 0x9000514c in syscall #1 0x90515d6c in BSD_waitevent #2 0x9051573c in CarbonSelectThreadFunc #3 0x90020d48 in _pthread_body Thread 4: #0 0x9003eaa8 in semaphore_wait_signal_trap #1 0x9003e8c4 in _pthread_cond_wait #2 0x9051dc30 in CarbonOperationThreadFunc #3 0x90020d48 in _pthread_body Thread 5 Crashed: #0 0x00000058 in 0x58 #1 0x00288b24 in 0x288b24 #2 0x00288960 in PySocketSock_recvfrom #3 0x001fc004 in PyCFunction_Call #4 0x00259ea8 in 0x259ea8 #5 0x00256278 in PyEval_EvalCodeEx #6 0x0025d3dc in fast_function #7 0x00259f94 in 0x259f94 #8 0x00256278 in PyEval_EvalCodeEx #9 0x0025d3dc in fast_function #10 0x00259f94 in 0x259f94 #11 0x00256278 in PyEval_EvalCodeEx #12 0x0025597c in function_call #13 0x001da51c in PyObject_Call #14 0x00255238 in instancemethod_call #15 0x001da51c in PyObject_Call #16 0x001d59e4 in PyEval_CallObjectWithKeywords #17 0x002b8024 in builtin_apply #18 0x001fc004 in PyCFunction_Call #19 0x00259ea8 in 0x259ea8 #20 0x00256278 in PyEval_EvalCodeEx #21 0x0025d3dc in fast_function #22 0x00259f94 in 0x259f94 #23 0x00256278 in PyEval_EvalCodeEx #24 0x0025597c in function_call #25 0x001da51c in PyObject_Call #26 0x00255238 in instancemethod_call #27 0x001da51c in PyObject_Call #28 0x001d59e4 in PyEval_CallObjectWithKeywords #29 0x0028bf1c in t_bootstrap #30 0x0028c84c in 0x28c84c #31 0x9023bdac in CooperativeThread #32 0x90020d48 in _pthread_body Thread 6: #0 0x9003eaa8 in semaphore_wait_signal_trap #1 0x9003e8c4 in _pthread_cond_wait #2 0x90233368 in TSWaitOnSemaphoreCommon #3 0x9023c170 in TimerThread #4 0x90020d48 in _pthread_body PPC Thread State: srr0: 0x00000058 srr1: 0x4000f030 vrsave: 0x00000000 xer: 0x20000000 lr: 0x00285ca4 ctr: 0x0000005a mq: 0x00000000 r0: 0x0000005a r1: 0xf0283ff0 r2: 0x003f3344 r3: 0x01fa2860 r4: 0x004ca860 r5: 0x00000000 r6: 0x1a47d000 r7: 0x00000000 r8: 0x87c26960 r9: 0x00000000 r10: 0x0000a832 r11: 0x00000000 r12: 0x004e40b0 r13: 0x00000001 r14: 0x024995f0 r15: 0x02416420 r16: 0x02417200 r17: 0x02416578 r18: 0x00000000 r19: 0x00000001 r20: 0x024ff8c0 r21: 0x00000000 r22: 0x00000000 r23: 0x02438640 r24: 0x02417200 r25: 0x01fa2860 r26: 0xf02840b8 r27: 0xf0284148 r28: 0xf0284138 r29: 0x00000000 r30: 0x0006074c r31: 0x0043ae48 Is anyone out there enough of an expert in MacPython's threading code to see why this should melt down? From the "Thread 6 crashed" dump, it looks as if the socket being closed is not returning an error correctly. Thanks in advance. Marcus Mendenhall

1 0

wxPythonOSX for Python 2.3a1
by Robin Dunn Jan. 30, 2003

Jan. 30, 2003

I've uploaded an evaluation release of wxPythonOSX 2.4.02 for MacPython-OSX 2.3a1. You can get it from the bottom of the SF wxPython files page: http://sf.net/project/showfiles.php?group_id=10718 In addition to building for Python 2.3a1 I've greatly changed how the distribution itself is made and now the demo, PyShell, (and others in the future) are now installed as their own App bundles using the new bundlebuilder.py tool. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!

2 9

getting 2.3 working with Tkinter
by Tom Jan. 30, 2003

Jan. 30, 2003

> From: Tom <ranch1(a)earthlink.net> > Date: Thu Jan 30, 2003 11:46:40 AM US/Eastern > To: Robin Dunn <robin(a)alldunn.com> > Subject: Re: [Pythonmac-SIG] getting 2.3 working with Tkinter > > > On Thursday, January 30, 2003, at 11:29 AM, Robin Dunn wrote: > >> >> If you're talking about my MacPython binary (in the wxPython files >> area at SF) then it's simply because I don't have TclTk installed and >> so when I built Python it skipped the _tkinter module. >> > > Darn, I thought that might be the case (given that the binary was on > an alternative GUI sit.e). > > I don't suppose I can just drop in a few modules, I sue would like to > run leo, X11 is too slow on this G4 400, and I don't seem to be smart > enough to get things working if I try to compile things myself (plus > source download over dailup is insane). > > Tom >

1 0

getting 2.3 working with Tkinter
by Tom Jan. 30, 2003

Jan. 30, 2003

I'm trying to get 2.3 and tkinter working (now that a binary showed up on sourceforge). Installed TclTkAquaBI8.4.1 Trying to work through all the unix stuff to get this working. get this: [Toms-Computer:/usr/local/bin] tom% pythonw /Volumes/80\ Gig\ Stuff/Download_IE/leo-3.10/leo.py Traceback (most recent call last): File "/Volumes/80 Gig Stuff/Download_IE/leo-3.10/leo.py", line 35, in ? from leoGlobals import * File "/Volumes/80 Gig Stuff/Download_IE/leo-3.10/leoGlobals.py", line 8, in ? import exceptions,os,re,string,sys,time,types,Tkinter File "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/lib- tk/Tkinter.py", line 38, in ? import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter Any Ideas? Tom

2 1

MachoPython2.3 and wxpython2.4.0.2
by boyle5＠llnl.gov Jan. 30, 2003

Jan. 30, 2003

I have a framework build of python2.3.1a on my OS X 10.2.3 box and would like to install wxPython2.4.0.2. From my efforts so far it appears that the installer wxPythonOSX-2.4.0.2 at sourceforge wants to install with python2.2(which I also have). Can I coerce the installer to use python2.3? (my knowledge of frameworks is quite meager). Or should I wait for a new installer? Thanks, Jim

2 1