🌐 Mailman 3 August 1999 - Pythonmac-SIG - python.org

Mac PIL
by Bill Bedford Aug. 13, 1999

Aug. 13, 1999

Is there a version of PIL that doesn't use Ghostscript to manipulate EPS images? -- Bill Bedford billb(a)mousa.demon.co.uk History has to be observed, otherwise its not history, It's just.... well one thing happening after another.

1 0

Re: [Pythonmac-SIG] Status of MacPython?
by Jim Harrison Aug. 11, 1999

Aug. 11, 1999

Jeffrey Shell wrote: >Getting Python compiled on MacOS X is not a high priority for me, but MacOS >X Server may become one if DC Customers want to deploy Zope on that >platform, so I'm interested in getting that up and running again. I'd be interested in hearing from you in the future if you deploy Zope on MacOS X Server and/or MacOS X. My current project is a Linux Zope deployment on a G3 with Linux and Mac partitions, for intranet development. It would be interesting to take a look at performance and management requirements for MacOS X [Server or not] vs. Linux. If I could revert to a simpler setup in the future it would be an advantage. Jim ________________________________________________________________________ James H. Harrison, Jr., MD, PhD Associate Director, Division of Pathology Informatics Department of Pathology, Univ. of Pittsburgh Health System C920 PUH, 200 Lothrop Street Pittsburgh, PA 15213 jhrsn(a)pop.pitt.edu | voice: 412-647-5529 | fax: 412-647-9588 "If you want sense, you'll have to make it yourself!!"-Norton Juster ________________________________________________________________________

2 1

Re: [Pythonmac-SIG] Using Spaces for indentation in IDE
by Oliver Steele Aug. 11, 1999

Aug. 11, 1999

Joseph J. Strout <joe(a)strout.net> writes: > At 1:45 PM -0700 07/23/99, Chris Barker wrote: >>Can the IDE be set up to use just spaces for indentation? I'd like it to >>be just like Emacs mode. > > If you must continue down this evil path, I think this is your most likely > bet. Hack the IDE code that loads and saves files. On loading, have it > convert spaces to tabs. On saving, have it convert tabs to spaces. I needed a solution for this too. (In addition to wanting to work with the many sources I download from the web, I'm doing cross-development work with people using other IDEs on Windows and UNIX.) I've put a patch that does this at http://www.cs.brandeis.edu/~steele/sources/python.html, at PyIDESpacesToTabsPatch.py. 'import' this file, and it'll patch the IDE to change spaces to tabs, and back. This is only minimally tested, but if you desperately need to edit space-indented files you might see whether it actually solves your problem -- if it's useful for enough people, maybe something like it can go in the IDE. > This will be far easier than trying to get the text engine (WASTE) to > understand that a tab isn't really a tab, but some variable number of > spaces, and that when you hit delete, sometimes you don't want to delete > just one space, but 2 or 3 or 4. This was my first approach (getting PythonIDE to understand that spaces and tabs both indent) -- it avoids PyIDESpacesToTabsPatch's problem of figuring out which tabs used to be spaces and which ones used to be tabs, and it copies the spec of python-mode.el, which seemed like a Good Thing -- but it's annoying to click in the middle of an indentation level, and to have to arrow or backspace multiple times, so I prefer the other solution. --- >From PyIDESpacesToTabsPatch: "This is a work in progress; use it at your own risk. Patches PyIDE's edit windows so that an editor opened onto a file indented with spaces will have represent the spaces as tabs. Saving such a file will write it back out with spaces. Usage: Put this file in Python's search path, and after PythonIDE has launched, type 'import PyIDESpacesToTabsPatch' at its command line. To turn off the feature: import PyEdit PyEdit.Editor.CONVERT_SPACES_TO_TABS = 0 To turn it back on: PyEdit.Editor.CONVERT_SPACES_TO_TABS = 1 To do: - auto-detect 2- and 8-space indents - save a new buffer as space-indented - only tabify *.py files? - let you see whether the file you're editing is space-indented"

1 0

Re: [Pythonmac-SIG] Status of MacPython?
by Jeffrey P Shell Aug. 10, 1999

Aug. 10, 1999

> I'm not sure what the best choice is for MacOS X. One possibility would be to > start with plain-old-unix-Python and add the Mac modules we want. The other > would be to start with MacPython, make it carbon-compliant and start with > that. Each of the approaches has its merits: The unix-approach would bring > MacPython more in line with the other platforms, but the mac-approach would > make it easier to keep things like the current preferences stuff, > PYC-resources and the dynamic module scheme. > > Maybe we could start off with two distributions (or one distribution with two > binaries?) and work towards one binary from there, I don't know... Of course, > things that third parties (like CodeWarrior) do could also have great impact > on this question. The new version of ProjectBuilder in MacOS X (Developer Preview) has the ability to import projects, and (I believe) it can import CodeWarrior projects so work can be done to carbon-ify them. I think I was able to bring in the MacPython sources this way, but I didn't know my way around near-well enough to go any further. I'm getting a new 8 gig hard drive today whose purpose is to let me install a few alternate OS's and not wipe my main hard drive out again *waaa!*. Getting Python compiled on MacOS X is not a high priority for me, but MacOS X Server may become one if DC Customers want to deploy Zope on that platform, so I'm interested in getting that up and running again. Would a carbon-complient MacPython mean it would support threads? That's the most important thing to me. I always end up compiling Python on XXX platforms because any "shipped" Pythons tend not to be threaded. .jPS

1 0

Re: [Pythonmac-SIG] Status of MacPython?
by Jack Jansen Aug. 10, 1999

Aug. 10, 1999

> It would be really useful to me to see some brief comments on the future > of Mac Python from Jack and/or Just, even though I know that crystal-ball > stuff is inexact. Is it anticipated that standard python will compile for > Mac OS X or will a special distribution be required? Will Mac Python > continue as a separate entity? Are additional Mac Python releases (i.e., > the 1.5.2 final) anticipated? If MacPython will continue in the future, > what's the prognosis of the current development effort? I'm not sure what the best choice is for MacOS X. One possibility would be to start with plain-old-unix-Python and add the Mac modules we want. The other would be to start with MacPython, make it carbon-compliant and start with that. Each of the approaches has its merits: The unix-approach would bring MacPython more in line with the other platforms, but the mac-approach would make it easier to keep things like the current preferences stuff, PYC-resources and the dynamic module scheme. Maybe we could start off with two distributions (or one distribution with two binaries?) and work towards one binary from there, I don't know... Of course, things that third parties (like CodeWarrior) do could also have great impact on this question. And 1.5.2 final is alive and kicking, the problem is that I'm fiendishly busy, and so is Just, and the final packing up of a distribution just doesn't seem to happen. Actually, if I have to pack something up right now it'll be 1.5.2+, as my sources track the CVS repository and these have gone past 152 (and I don't have the time to retrieve the old stuff, adapt the projects, etc). -- 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] Status of MacPython?
by Jeffrey P Shell Aug. 9, 1999

Aug. 9, 1999

> It would be really useful to me to see some brief comments on the future > of Mac Python from Jack and/or Just, even though I know that crystal-ball > stuff is inexact. Is it anticipated that standard python will compile for > Mac OS X or will a special distribution be required? Will Mac Python > continue as a separate entity? Are additional Mac Python releases (i.e., > the 1.5.2 final) anticipated? If MacPython will continue in the future, > what's the prognosis of the current development effort? It wasn't terribly difficult building Python 1.5.2 on MacOS X Server, but Mac OS X was quite a different story, mostly due to it being so new and in development stage that none of the configuration scripts would catch the right things. I tried and tried and hacked away at these, but it is something that is nowhere near my realm of expertise and when I finally got Python to compile without breaking, the compiled code wasn't always in the right place (it seems that some stuff went into the .dylib file, while a majority went into the .a). At this point, I gave up. I don't think it will be too hard getting (normal) Python to compile on MacOS X, it'll just require someone smarter than I am about configuration script programming and all the wild new features of MacOS X's Unix side. (I bet it's a fair amount of trickery getting a good Python built on Darwin too). MacPython will run, but it would be in the "Blue Box" area until someone takes the time to make it Carbon complient. As I'm not a MacOS Developer (just a long-time-happy-user), I don't know the difficulty in this. Tip Top (www.tiptop.com) makes a product called Objective Everything which opens up OpenStep/YellowBox/Cocoa (whatever flavor NeXT's old rockin framework is called this month) to Python, Perl, and TCL. It runs on MacOS X and Server, but currently is only Python 1.4. There is supposed to be a new release sometime (hopefully soon) that uses Python 1.5. Of interest is that TipTop says that Objective Everything says (and I quote): "Carbon development and scripting. Objective-Everything is Carbon-ready! It lets you leverage the Carbon API from any of the Objective languages." (from the MacOS X Server press release for OE). So there is another option for MacOS X and Python development for Mac OS (Carbon) applications, and presumably it'll be an alternative to jumping-through-appleevents to script other applications via Python. That's all I know on the MacOS X side. I think MacPython will continue to be MacOS "Classic" (I think that's the official term from Apple) based. A unixy build of Python for MacOS X's BSDI underbelly will be a different beast, and there'll also be the commercial-but-free-for-some-uses Objective Everything for Cocoa/Carbon development in MacOS X and Python. (As a note: when installing LinuxPPC, don't get too cocky reordering your partitions with pdisk. *sigh*. Especially, don't say "I hope my regular MacOS Partition has survived all this" jokingly, because, well, it didn't).

1 0

Duplicate items in a list
by Pieter Claerhout Aug. 9, 1999

Aug. 9, 1999

Hello, does anyone know an easy way to delete duplicate items from a list? What I want to accomplish is something like this: - original list: ("A", "A", "B", "A", "C", "C", "C") - new list: ("A", "B", "C") Kind regards, Pieter Pieter Claerhout - PClaerhout(a)creo.be Response Center - Applications Support Creo Europe - Excelsiorlaan 21 - 1930 Zaventem - Belgium Tel: +32 (2) 711 14 00 - Fax: +32 (2) 720 96 71

3 2

Re: [Pythonmac-SIG] Duplicate items in a list
by Anthony M. Ingraldi Aug. 9, 1999

Aug. 9, 1999

On Monday, August 9, 1999, Pieter Claerhout wrote: > does anyone know an easy way to delete duplicate items from a list? > This may not be the most efficient way, but anyway... def remove_duplicates(aList): newList = [] for item in aList: if not (item in newList): newList.append(item) return newList -- Tony Ingraldi A.M.INGRALDI(a)LaRC.NASA.GOV Phone : (757) 864-3039 Fax : (757) 864-7892

1 0

NavServices, GWorlds: you want 'em, I got 'em
by Joseph J. Strout Aug. 6, 1999

Aug. 6, 1999

FYI, I've made little helper modules for Navigation Services and GWorlds (offscreen graphics) in MacPython. If anybody wants 'em, just let me know. Cheers, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Biocomputing -- The Salk Institute | | joe(a)strout.net http://www.strout.net | `------------------------------------------------------------------'

1 0