Mailman 3 January 2001 - Pythonmac-SIG

Building mxDateTime for Python 2.0
by Vincent Marchetti Sept. 24, 2001

Sept. 24, 2001

I am trying to re-compile the mxDateTime shared library to let me use DateTime in Python 2.0 -- the shared library provided throws exception on import about using the wrong version. I have never compiled any type of shared library before, so girding my loins and firing up CW 5 I set up a shared library project and: 1. included the mxDateTime.c code 2. included stub libraries PythonCore and MSL ShLibRuntime.Lib Result: -- Link failure, could not find function 'floor' I knew this is a standard C function, so I threw the stub MathLib into the pot and cooked. Got a bunch of warnings about duplicate definitions of math functions (in PythonCore and MathLib). Decided to ignore warnings. Successfully made the shared library, successfully imported DateTime into Python 2.0 (actually 2.0b1). However, the test script for mxDateTime failed an assertion. Basically, a function DateTimeFromTicks, which uses the floor function, fails to give predicted results. My question: Am I including the correct library in my project to get the "right" version of floor? Thanks, Vince Marchetti

4 3

Re: [Pythonmac-SIG] Embedding Python w/o SIOUX popping up
by Jack Jansen April 18, 2001

April 18, 2001

> I am embedding Python in a Code Resource that loads as an extension to the > program Igor. My extension loads the PythonCore Shared Library. When I > call my command from the Igor command window and the code in my extension > calls PyMac_Initialize() a SIOX window pops up and another apple menu is > added at the top of the screen. There is porbably some way to use the > funcitonality of PythonCode without loading the Window/menubar, and if > there is, I would love any advice anyone may have on this > situation. Thanks. Your application needs python preferences resources (a "Popt" and a "GU<sigma> I" resource). The easiest way to get these is dropping your application on EditPythonPrefs. An alternative (often handier because you don't have to do it after every build) is to create a resource file that includes the Popt and GUSI resource and include this in your build. -- 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] Re: Pythonmac-SIG digest, Vol 1 #455 - 5 msgs
by Anthony Ingraldi March 6, 2001

March 6, 2001

> B) is the TK stuff needed to use Gnuplot, or is just what you used to > create your "GUI-driven" solution. > You can drive Mac Gnuplot from python via the "standard" Gnuplot.py module. The module is available at http://monsoon.harvard.edu/~mhagger/Gnuplot/Gnuplot.html. The latest version includes support for the Mac. Also, the Mac gnuplot distribution contains a simple console written in python. You can obtain the Mac port of gnuplot at http://users.ece.gatech.edu/~schooley/gnuplot.html. It looks like it hasn't been updated in over 2 years. -- Tony Ingraldi A.M.INGRALDI(a)LaRC.NASA.GOV Phone : (757) 864-3039 Fax : (757) 864-7892

2 1

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

Re: [Pythonmac-SIG] Qdoffs (was Qd question)
by Jack Jansen Jan. 30, 2001

Jan. 30, 2001

The gworld object is automatically disposed of when the last reference to the Python object goes away. This is the general philosophy of the Python Toolbox interfaces, but unfortunately there are some necessary exceptions, such as Res objects (which can be either Handles or Resources, which need to be disposed in different ways) or Ctl objects, which should be disposed if Python created them, but not if Python obtained them through, say, GetDialogItemAsControl (because they're owned by the dialog in that case, and disposing of the control because we no longer reference it from Python is definitely not what we want). The interfaces are slowly being updated to a new scheme, whereby each object carries a pointer to the disposal routine. Initially the modules will set this pointer "correct", i.e. to the MacOS dispose routine for objects that were created by Python and to an empty routine for objects that Python obtains through other means. There will be an interface to change this disposal behaviour from Python code. -- 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

Re: [Pythonmac-SIG] Qd question
by Jack Jansen Jan. 30, 2001

Jan. 30, 2001

> [...] I see in the QuickDraw docs on > apple's site that you can draw to offscreen "worlds", but the corresponding > methods don't seem to be available to python. Yes, they are, as of MacPython 2.0. But they're not in the Qd module, they're in Qdoffs (MacPython modules tend to more-or-less follow the Universal Header file structure). There isn't any documentation, but :Mac:Lib:videoreader.py is an example of how you could use this. But maybe you could donate an example of doing double-buffered drawing once you have it working? Oh yes, something else to remember is that under MacOSX you can disable all this code, as windows will be double-buffered automatically by default, so it may be a good idea to have your code be ready for that. -- 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 2

Qd question
by Nick Collier Jan. 29, 2001

Jan. 29, 2001

Hi, I've been doing some simple animation using the Qd module - press arrow key and a shape gets larger or smaller. This has worked well when I've used Qd.Frame*, but when I try and draw a filled shape with Qd.Paint* there is lots of shearing and flicker in the animation. I see in the QuickDraw docs on apple's site that you can draw to offscreen "worlds", but the corresponding methods don't seem to be available to python. Any suggestions how to get better animation would be appreciated. thanks, Nick -- Nick Collier Social Science Research Computing University of Chicago http://repast.sourceforge.net

1 0

Bug in unicode?
by Peter Stirling Jan. 29, 2001

Jan. 29, 2001

Hi, I was trying out the Tk stuff under python 2.0 on OS 9.0.4, I ran the Tkinter test and it opened up a window with the line: "This should be a cedilla: " and instead it was a german double s and a delta or something, I'm not at my machine at the moment, so I'm not sure. Whatever it was it wasn't a cedilla. PJs

1 0

Tkinter bug
by mark brady Jan. 25, 2001

Jan. 25, 2001

There seems to be bug in Tkinter regarding canvas cursor locations. The following code prints the cursor location when the mouse is clicked in a scrollable canvas which is in a frame: def drawCallback(event): canvas = event.widget x = canvas.canvasx(event.x) y = canvas.canvasy(event.y) print "clicked at", int(x+.5), int(y+.5) Before scrolling there seems to be an offset of about 4 form the actual canvas location. Maybe the frame location is being used. I suspect this because there is a blank border of about 4 pixels between the frame and the canvas. After scrolling, the error goes away. -Mark

1 0