🌐 Mailman 3 February 2001 - Pythonmac-SIG - python.org

BuildApplication in MacPython 2.0
by Nathen Hinson Feb. 7, 2001

Feb. 7, 2001

To the list subscribers When running the BuildApplication program that is included in the MacPython 2.0 distribution I receive a 'terminated' window with the following output Traceback (most recent call last): File "Macintosh HD:SWdev:Jack:Python:Mac:scripts:BuildApplication.py", line 147, in ? File "Macintosh HD:SWdev:Jack:Python:Mac:scripts:BuildApplication.py", line 51, in main File "Macintosh HD:SWdev:Jack:Python:Mac:scripts:BuildApplication.py", line 73, in buildapplication ValueError: unpack sequence of wrong size Is this a known issue ? or is something wrong locally with my config ? Any help would be greatly appreciated. Sincerely Nathen Hinson UHS - ITS

1 0

Curiouser and curiouser... About OSX
by Andrew Robbins Feb. 6, 2001

Feb. 6, 2001

I've been using Python for the Mac for awhile now, and I'm wondering If, and when there are plans to add support for OSX's GUI. It seems like you'd just need to make a python module in ObjC or Java. I'm really interested, and I have the beta, so I'd help if need be. My programming skills are pretty bad, even tho i convince myself that I'm a programmer sometimes. I read more than i write, but if theres anything I can do, or if you need a tester, I'm your man... The point of this was to see how OSX's GUI/Frameworks support was comming along... Andrew Robbins __________________________________________________ Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/

2 1

Re: [Pythonmac-SIG] Curiouser and curiouser... About OSX
by Jack Jansen Feb. 6, 2001

Feb. 6, 2001

MacOSX support is probably going to happen along two lines. First of all I'm busy with getting MacPython to run under Carbon, which is now 99% done (I hope to release a MacPython 2.1 alfa later this week or early next week). I would expect this to be the basis for MacPython for the next year or so, for as long as MacOS9 machines are still predominant. Eventually I expect the standard MacPython to be based on the Unix Python, with the MacOS extension modules thrown in. Some people are already working on getting the extensions to work, with reasonable success (if I understand correctly). -- 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

3 3

Re: [Pythonmac-SIG] Solved: problem with socket library in 2.0?
by Jack Jansen Feb. 4, 2001

Feb. 4, 2001

> I found the answer in the socket HowTo, which I didn't know about > until I saw one of my students reading it this afternoon. I was using > '127.0.0.1' as the address of the server socket, thereby rendering it > invisible to other machines. > > This is new in 2.0. Is this another one of those cases where the > behavior in 1.5.2 was convenient but incorrect? The old behaviour was probably because Python 1.5.2 used GUSI 1 for socket I/O, which was implemented with MacTCP, which didn't understand about multiple network addresses per machine, so a listen() ignored the source IP address. Python 2 uses GUSI 2 which is implemented with Open Transport, which does know about multihoming, so the source IP address is suddenly important. Note that the normal way to do a listen(), on both 1.5.2 and 2.0, is not to pass any source IP address at all, in which case the listen() will happen on all IP addresses of the machine automatically. -- 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

2 1

Numeric on OS X
by Tim Lahey Feb. 3, 2001

Feb. 3, 2001

I'm trying to get Numeric to run on OS X (and Multipack for that matter). I've managed to get it to compile but when I run it I get the following: Python 2.0 (#10, 11/12/00, 02:11:28) [GCC Apple DevKit-based CPP 5.0] on Darwin1.2 Type "copyright", "credits" or "license" for more information. >>> from Numeric import * dyld: python multiple definitions of symbol _PyArray_API /usr/local/lib/python2.0/site-packages/Numeric/multiarray.so definition of _PyArray_API /usr/local/lib/python2.0/site-packages/Numeric/umath.so definition of _PyArray_API <exit to shell> Any suggestions on fixing this problem ? Thanks, Tim Lahey

1 0

Canvas PhotoImage
by mark brady Feb. 3, 2001

Feb. 3, 2001

I find some strange things happening with PhotoImages. The line of code below should display a PhotoImage item on a canvas but it doesn't. imageItem = myFrame.draw.create_image( sizex, sizey, image=tkIm ) where myFrame is a frame, draw is a canvas, and tkIm is a PhotoImage. A similar line works elsewhere when the frame is created. Just to be sure everything else was OK with my context I tried creating an oval item on the canvas at the same point in my program that the above line appears, using the same frame, canvas, etc. That appeared just fine. So there seems to be some difference in behavior between ovals and PhotoImages. Has anyone else tried this? -Mark

1 0

findertools.copy()
by Jon Moody Feb. 2, 2001

Feb. 2, 2001

The module documentation says that findertools.copy(src,destdir) returns an Alias object pointing to the new file, but what I'm getting instead looks like an ObjectSpecifier object (File('filename')). Is there an Alias object buried somewhere in there? How does one retrieve the raw Alias data from this thing?

1 0

Re: [Pythonmac-SIG] Writing
by Jack Jansen Feb. 2, 2001

Feb. 2, 2001

Recently, mark brady <brady(a)mmm.com> said: > I am attempting to write text to a file. I've opened the file (I think) > using macfs StandardPutFile. Here are my questions: Does this > actually open a file? What method can the FSSpec file use to actually > write? write() doesn't seem to work. The FSSpec is only the name of the file, not the open file. Moreover, it's in a funny MacOS-specific form, and to open the file it's easiest to have the full pathname. Something like this: file = open(fsspec.as_pathname(), "w") # or "wb" if you want to write # binary data The file object has the expected read/write/seek methods. -- 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

1 0

Writing
by mark brady Feb. 1, 2001

Feb. 1, 2001

I am attempting to write text to a file. I've opened the file (I think) using macfs StandardPutFile. Here are my questions: Does this actually open a file? What method can the FSSpec file use to actually write? write() doesn't seem to work. -Mark

2 1

problem with socket library in 2.0?
by James B. Wilkinson Feb. 1, 2001

Feb. 1, 2001

Last year I wrote a rudimentary client/server pair using dgramsockets. I used it in my networking class as a demo. Today I installed Macpython 2.0 on my Mac, and that seems to have broken the server. Things just hang as if the packet from the client is not being delivered. If I drag the server onto the 1.5.2 interpreter, it still works fine with the same client. Can anybody else confirm this? Thanks #Datagram server from socket import * import struct HOST = '127.0.0.1' PORT = 50007 def serve(): s = socket(AF_INET, SOCK_DGRAM) s.bind((HOST, PORT)) test(s) s.close() def test(s): data, addr = s.recvfrom(1024) print 'Connected by', addr, "got: ", data s.sendto(data, addr) if __name__ == '__main__': serve() #Datagram client from socket import * HOST = 'burton.cs.cofc.edu' PORT = 50007 s = socket(AF_INET, SOCK_DGRAM) s.sendto('Hello, world.', (HOST, PORT)) data, addr = s.recvfrom(1024) s.close() print 'Received:', `data`, 'from', addr -- ------------------------------------------------------------- Jimmy Wilkinson | Perfesser of Computer Science jimmy(a)cs.CofC.edu | The College of Charleston (843) 953-8160 | Charleston SC 29424 If there is one word to describe me, that word would have to be "profectionist". Any form of incompitence is an athema to me.

1 1