🌐 Mailman 3 November 1999 - Python-list - python.org

About RedHat 6.1 install program
by johndoe0521＠my-deja.com Nov. 2, 1999

Nov. 2, 1999

I think this might be python's problem. I copy all the files from the CD of RedHat 6.1 to the harddisk, and make under /misc/src/anaconda, and some errors occur. Should it happen? And if I make some changes of the install source, how can I put the new install program into boot image? Thanks! Sent via Deja.com http://www.deja.com/ Before you buy.

3 2

RE: Need Berkley DB!!
by Adrian Eyre Nov. 2, 1999

Nov. 2, 1999

FWIW the version of BSDDB used to build Win32 Python is available at: ftp://squirl.nightmare.com/pub/python/python-ext/misc/bsddbmodule.zip -------------------------------------------- Adrian Eyre <mailto:a.eyre@optichrome.com> Optichrome Computer Solutions Ltd Maybury Road, Woking, Surrey, GU21 5HX, UK Tel: +44 1483 740 233 Fax: +44 1483 760 644 http://www.optichrome.com --------------------------------------------

1 0

Re: Printing strings
by François Pinard Nov. 2, 1999

Nov. 2, 1999

Matthew Hirsch <meh9(a)cornell.edu> writes: > a=4.0 > b=2.0 > print '2(%3.1f)' % a,b > where I really mean > print '%3.1f %3.1f' % a,b > but it's printing > 2(4.0) 2.0 > Is there a way of doing this so I don't have to write out %3.1f, > multiple times? Maybe you could play around this idea? >>> a, b = 4.0, 2.0 >>> print '%4.1f' * 2 % (a, b) 4.0 2.0 I changed `%3.1f' into `%4.1f' because `4.02.0' would not look nice.) -- François Pinard http://www.iro.umontreal.ca/~pinard

1 0

Caps in doc strings (was: Re: Default indentation of 4 columns)
by François Pinard Nov. 2, 1999

Nov. 2, 1999

Paul Foley <mycroft(a)actrix.gen.nz> écrit: [about using capitals or not in documentation strings] > Interestingly, I use both conventions, but for different reasons (I > didn't even know that the use of capitals _was_ a GNU convention; did know > Knuth uses |vertical bars| for literals, but hadn't even considered that). [I wanted to include the Python list in this reply, and for doing so, took the liberty of quoting most of your message, which I found interesting and instructive, to provide enough context.] In Texinfo, @var{xyz} is for documenting variables, and is rendered with slanted fonts on a laser printer. When converting to Info (that is, ASCII), there is no slanted fonts, and capitals are used instead. In fact, exactly how various @style{...} are represented in ASCII is well documented. The informal convention for doc strings is letting ourselves think Texinfo (@code{...} for code elements, @samp{...} for string fragments, @var{...} for variables or non-terminal symbols, @emph{...} for emphasis, etc.) and just doing the Info rendering "by hand", following the standards set by the Texinfo to Info conversion. > I use capitals because that's the common case in Common Lisp; I use > vertical bars for lowercase symbols for the same reason (Common Lisp uses > vertical bars to read in a case-preserving manner). Hence, I use vertical > bars for Python variables and functions, because they're case-dependent and > case-preserving, and capitals in languages that are either case-insensitive > (e.g., Pascal) or that standardize on upper-case (e.g., Lisp). I thought that, in Python, usual local variables, and formal arguments among them, are to be conventionally set in lower case anyway, so the mixed case difficulty does not apply in actual practice, even the language itself would allow more variance. No doubt that a coding style is a set of restrictions over what a language permits, that we choose to follow for various reasons. There is a lot of commonality (or at least, very little clash) between Guido's recommendations and GNU standards about the naming convention for identifiers, and it was part of my pleasure, reading the details of Python coding style, to see that I had so little to change in my long lasting habits. (The main change was to learn how to use a bit less whitespace at some specific places, like between a function and its argument list, or around the `=' introducing keyword arguments -- and surprisingly, it was very easy to get some speed on this). I consider that Guido's recommendations and GNU standards enlighten each other to a good extent. Besides Emacs LISP, I have little recent exposure to various dialects of LISP. What I've seen from others' Scheme code (but that is not much) seems to favour lower-case as well, and capitals for systemic constants, nothing unusual for me. Scheme ignores case in identifiers, but this never precluded me to write exactly as if case was significant. DSSSL, if I remember well, is a case-sensitive implementation of Scheme. (So is Guile, the last I heard, but since Guile was not meant to be very respectful of standards when initially designed, I return the favour by not being very respectful of Guile; what Guile does do not matter much. :-) > I think the "use caps" standard is a pretty bad idea in a case-sensitive > case-preserving language like Python, since it doesn't let you distinguish > between names that the same in all but case (common to make the distinction > between class names and variable names, in Python). Python and C (and Emacs LISP, for that matter) are quite similar in what they permit for capitalisation, and what people actually use while writing these. I quite understand what you mean by "use caps" standard being a pretty bad idea, and I remember feeling uncomfortable when I started to use it, thinking about those constants we always write in all capitals, before even speaking of them in doc strings, and all the confusion that might result. But I followed the capitalisation convention in doc strings for more than a dozen years, being often quite active at programming, and I can ensure you from experience that my fears were not justified. That convention is quite workable, it does not raise any real problem on the wide average. I'm rather convinced, by now, that it is a legible way to write doc strings. If we simultaneously follow the rest of naming conventions, that is! :-) -- François Pinard http://www.iro.umontreal.ca/~pinard

1 0

Tcl82.dll not found
by Art Goldhammer Nov. 2, 1999

Nov. 2, 1999

I've just installed Python 1.5.2 on a Win98 machine that already had Tcl8.2 installed, so I didn't install the Tcl8.0 that came with Python. Unfortunately, Tkinter doesn't work. I've traced the problem to FixTk.py, which is looking for Tcl80.dll, which of course it doesn't find, because Tcl82.dll is the file in the directory where it's looking. Do I really have to install an older version of Tcl to get Tkinter working? Thanks, Art

3 3

vector?
by Mona Wong Nov. 2, 1999

Nov. 2, 1999

Hi: I am new to python ... I'm sure you've heard that too many times before ... Anyway, to make vectors using python, is there a module or should I just make it out of arrays? I searched the archive but didn't see any info related to vectors. Thanks, in advance, for your help. Sincerely, Mona -- ================================================================== Mona Wong graphics / visualization programmer wanna-be & web fool-arounder National Center for Microscopy and Imaging Research University of California, San Diego http://www-ncmir.ucsd.edu/ "The truth shall set you free, but first it will piss you off" A Landmark instructor ==================================================================

3 2

Re: ANN: small vector operation module
by Konrad Hinsen Nov. 2, 1999

Nov. 2, 1999

Fuming Wang <fuming(a)venus.radsci.uci.edu> writes: > I wrote a small module that does vector operations. It's quite useful for > processing lab data. Comments are welcome. Looks OK, but why don't you just use Numerical Python? It offers much more and is more efficient as well. -- ------------------------------------------------------------------------------- Konrad Hinsen | E-Mail: hinsen(a)cnrs-orleans.fr Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.55.69 Rue Charles Sadron | Fax: +33-2.38.63.15.17 45071 Orleans Cedex 2 | Deutsch/Esperanto/English/ France | Nederlands/Francais -------------------------------------------------------------------------------

1 0

os.popen() and (IDLE, PythonWin) ?
by M.-A. Lemburg Nov. 2, 1999

Nov. 2, 1999

[os.popen('ver') fails under IDLE and PythonWin, yet works under "normal" Python] Karl Putland wrote: > > Good call it is breaking under IDLE and Pythonwin. It works under vanilla > Python though. > > ****************************Pythonwin************************************ > PythonWin 1.5.2 (#0, Apr 13 1999, 10:51:12) [MSC 32 bit (Intel)] on win32 > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > Portions Copyright 1994-1999 Mark Hammond (MHammond(a)skippinet.com.au) > >>> import platform > >>> platform.platform() > 'win32-4.0-1381-SP4' > >>> > > ****************************Vanila Python******************************** > Microsoft(R) Windows NT(TM) > (C) Copyright 1985-1996 Microsoft Corp. > > C:\>python > Python 1.5.2 (#0, Apr 13 1999, 10:51:12) [MSC 32 bit (Intel)] on win32 > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > >>> import os > >>> os.popen('ver') > <open file 'ver', mode 'r' at 7f6f90> > >>> os.popen('ver').read() > '\012Windows NT Version 4.0 \012' > >>> import platform > >>> platform.platform() > 'Windows-NT-4.0-1381-SP4' > >>> Any idea how to get this working with PythonWin and IDLE ? I know there are some issues with pipes on Windows, but why should PythonWin and IDLE fail when vanilla Python works ? -- Marc-Andre Lemburg ______________________________________________________________________ Y2000: 63 days left Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/

3 4

Doing network traffic in the 'background' from Tkinter app??
by Andrew Markebo Nov. 2, 1999

Nov. 2, 1999

I have a Tkinter application that I would like to be able to download data from the internet.. possibly from more than one socket at a time.. How do yo do this?? I have been experimenting with a module that on call checks the active connectons (with select) and downloads data if there are any, and if it is done calls a callback.. The check-function is called from Tkinter's after_idle.. but the application freezes.. Any other hints?? /andy -----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==---------- http://www.newsfeeds.com The Largest Usenet Servers in the World! ------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==-----

3 5

Changing cursors...
by Xtian Muirhead Nov. 2, 1999

Nov. 2, 1999

Hello - I've been having a play with Tkinter, and I've ported across a program that I wrote while learning VB, but I've had one problem. There's one step that has a chunk of processing which takes a few seconds to complete. In the old program, I changed the cursor to an hourglass at the start, and reset when the program finished. Trying to do the same in the new version doesn't seem to work: self.btnIterate['state'] = DISABLED # after the call to self.btnClear['state'] = DISABLED # update_idletasks, # the buttons are # disabled, but... self.root['cursor'] = 'wait' # ...this doesn't happen. self.root.update_idletasks() # do some processing... (cursor is an arrow) self.btnIterate['state'] = NORMAL self.btnClear['state'] = NORMAL self.root['cursor'] = 'arrow' # after the callback processing is finished the cursor is # still the arrow - if I comment this out, the cursor # does change, but not until the callback processing # finishes. It looks like update_idletasks() doesn't do cursors - is this correct? (I looked in all the answer-type places of which I could think.) Xtian xtian(a)regurgitator.zzn.com

3 3