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

Re: [Pythonmac-SIG] writing binary files with MacPython
by Jack Jansen Feb. 19, 2001

Feb. 19, 2001

> I'm using MacPython 2.0 under Mac OS 8.5.1 and I'm having trouble with > creating binary files of short ints using MacPython. As a small > example: > > >>> from array import array > >>> a = array('h', [2678, 2689, 2699]) > >>> open('tmp', 'w').write(a.tostring()) If you open a binary file you should specify 'wb' as the flag (or 'rb' for reading). On Unix this isn't important, but on Mac and Windows it is. -- 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

Re: [Pythonmac-SIG] MacPython 2.1a2 available
by John W Baxter Feb. 19, 2001

Feb. 19, 2001

At 17:04 -0800 2/17/01, Corran Webster wrote: >At 11:28 PM +0100 17/2/01, Jack Jansen wrote: >>Please try this version and report your findings here to >>pythonmac-sig, including the full version info of your OS and >>MacPython (needed because I expect to release alfas often). > >I just downloaded the 2.1 alpha, but can't get it to run at all - >when I try t start any of the Python applications (IDE, Interpreter, >whathever), I get am error dialog saying that the application could >not be opened because "»CarbonLib«" could not be found. > >I'm running OS 9.1 on a Blue G3, with CarbonLib 1.1.1, which is >properly installed and running, as far as I can tell. I'm not using >the OS X Beta at all. I'm getting the same error (except that the wording is »CarbonLib« could not start up). Mac OS 9.1 with CarbonLib 1.2. 8100/80. Something was absorbing most available cycles after the installer claimed to have finished. I think we've done this before. The error starting up the Interpreter was after the forced restart and resultant cleanup. (Going away for long time would probably have avoided the forced restart.) --John -- John Baxter jwblist(a)olympus.net Port Ludlow, WA, USA

1 0

writing binary files with MacPython
by Jon Moody Feb. 17, 2001

Feb. 17, 2001

I'm using MacPython 2.0 under Mac OS 8.5.1 and I'm having trouble with creating binary files of short ints using MacPython. As a small example: >>> from array import array >>> a = array('h', [2678, 2689, 2699]) >>> open('tmp', 'w').write(a.tostring()) Then if I open this file using another Mac app (like RSI's Transform or IPLab), the file contains the numbers: 3446, 3457, 3467 The problem is not consistent; depending on what numbers are written to the file, sometimes they're correct, sometimes they're not when the file is opened by the external app. And the same thing happens if I write Numeric arrays to a binary file. What am I doing wrong? --- Jon

1 0

Numbers, strings
by Erik van Blokland Feb. 17, 2001

Feb. 17, 2001

Hi, This question is probably only half python-related. Is there a way to find out in Python what the local settings for numbers are in python? the values specified in MacOS control panel 'Numbers'. Background: I'm working on a python application that works alongside Filemaker Pro, floating point values are converted back and forth, works fine as long as everyone agrees on the Numbers format. The users of this app can have the 1,000.00 or 1.000,00 settings (or any other). The python app needs to find out how to interpret the imported values, and export them again. I can guess, but it's better to rely on system info. MacOS 9.0.4, python 1.5.2 Erik -- www.letterror.com Type & Typography

2 1

Re: [Pythonmac-SIG] Distributing modules, extensions & packages
by Tom Loredo Feb. 16, 2001

Feb. 16, 2001

Jack- > The short answer: Distutils, Yes, site-packages, yes, yes, no, no. Thanks a lot for the quick and informative response. > The long answer: distutils works and is fully supported from > MacPython2.1, for which an alpha will be available shortly. I currently use 2.0; I have also built some of the extensions for 1.5.2. I know many people are still using 1.5.2. What would be the appropriate distribution method for 1.5.2 and 2.0? Thanks, Tom

1 0

Re: [Pythonmac-SIG] Distributing modules, extensions & packages
by Jack Jansen Feb. 16, 2001

Feb. 16, 2001

Recently, Tom Loredo <loredo(a)spacenet.tn.cornell.edu> said: > I currently use 2.0; I have also built some of the extensions for > 1.5.2. I know many people are still using 1.5.2. What would be the > appropriate distribution method for 1.5.2 and 2.0? Hmm, difficult to say. You could try porting the new EasyDialogs and the mkcwproject module to 1.5.2. Otherwise a stuffit archive with sources and a CW projectfile is probably best. -- 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

Re: [Pythonmac-SIG] Distributing modules, extensions & packages
by Jack Jansen Feb. 16, 2001

Feb. 16, 2001

Recently, Tom Loredo <loredo(a)spacenet.tn.cornell.edu> said: > > Hi folks- > > How should one best go about distributing modules, extensions, and > packages for MacPython? Will distutils work with MacPython? If so, > where will intalled files be placed? (I would guess in > site-packages.) Is there any facility for handling extensions > distributed as source code (e.g., scripting of the CodeWarrior IDE)? > Since distutils is designed to work from a command line, I suspect it > would be awkward to use with MacPython. Is simply distributing Python > source and extension binaries in a folder with directions on where to > place them the preferred distribution method for MacPython? The short answer: Distutils, Yes, site-packages, yes, yes, no, no. The long answer: distutils works and is fully supported from MacPython2.1, for which an alpha will be available shortly. The command-line problem has been solved with the new EasyDialogs.GetArgv() which works very nice with the distutils style of commandline arg processing (and reasonable with other packages). The one thing that I haven't had time to test yet is the bdist stuff. If that works well on the Mac I may take Numeric, img and PIL out of the standard distribution, or at the very least make it a lot easier to replace them with more recent versions when they become available (by putting them in the site-python folder). -- 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

Distributing modules, extensions & packages
by Tom Loredo Feb. 16, 2001

Feb. 16, 2001

Hi folks- How should one best go about distributing modules, extensions, and packages for MacPython? Will distutils work with MacPython? If so, where will intalled files be placed? (I would guess in site-packages.) Is there any facility for handling extensions distributed as source code (e.g., scripting of the CodeWarrior IDE)? Since distutils is designed to work from a command line, I suspect it would be awkward to use with MacPython. Is simply distributing Python source and extension binaries in a folder with directions on where to place them the preferred distribution method for MacPython? I ask because I have some numerical extensions that may be of some general interest, and I also appear to have the ZODB and DocumentTemplate parts of Zope working with MacPython2.0 (but not very well tested yet). Thanks, Tom Loredo

1 0

Re: [Pythonmac-SIG] Numbers, strings
by Jack Jansen Feb. 16, 2001

Feb. 16, 2001

The conversion routines and such are in the Text Utilities manager. I think you should be able to call these through calldll. If you try this and it works: it would also be a much better example of calldll than what we have now (changing LMGetMenuFlash), so I wouldn't mind a donation of example code... If you don't want to do it this way you may be able to parse the "itl" resources, but I've never looked at this. -- 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

Re:[Pythonmac-SIG] project with embedded python
by Etienne Antoniutti Di Muro Feb. 14, 2001

Feb. 14, 2001

Jared, > > Subject: [Pythonmac-SIG] project with embedded python > Date: Tue, 13 Feb 2001 17:09:27 -0500 > From: Jared Schiffman <jarfish(a)media.mit.edu> > To: pythonmac-sig(a)python.org > > I'm trying to embed Python in a full fledge > C++ Mac application. Even without calling Python > code, just including the PythonCore makes things > crash. Python 2.0 or previous?? I'm using Python 1.5.2 and works fine. > > If anyone has a CodeWarrior project which uses > regular Mac libraries and includes PythonCore > (or a static Python lib), I would thoroughly > appreciate seeing it. > I included in my project the following folders: :Include :Mac:Include of the Pythoin1.5.2 distribution and I linked the PythonCore against the CW prj. As I can remember (it happened more than a year ago) I build the Python Core on my own (a pretty damned job) with those folders. Later I used the same PythonCore with different include folders, and crashed. I had to rebuild the PythonCore with the upgraded include folders to get the project compiled,linked ......and running. Think this is quite obvious. hope this can help regards etienne -- it's time to leave this town it's time to steal away let's go get lost anywhere in the U.S.A. (RHCP)

1 0