🌐 Mailman 3 November 2000 - Pythonmac-SIG - python.org

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

pyobjc-dev mailing list at SourceForge (fwd)
by Steven D. Majewski Dec. 1, 2000

Dec. 1, 2000

There seems to now be a pyobjc-dev mailing list on SourceForge. http://lists.sourceforge.net/mailman/listinfo/pyobjc-dev Except for the occasional progress report, pyobjc discussion will move there. -- Steve Majewski <sdm7g(a)Virginia.EDU>

2 1

Indentation Styles
by Tom Fetherston Nov. 29, 2000

Nov. 29, 2000

Hi all, Having opened a few of the files in the distribution, it seems to me that the indenting of statements is using "only-tabs" style, is this (or should this be) the default behavior on the Mac? Some of the contributions use the "all-spaces" form of indentation, but that seems to be just the their preference. Does ide/idle have one of this set as the default? There is a "Warn about inconsistent tab usage" check box in the pythonInterpreter run options dialog, could someone elaborate on what python does to check this (and/or point me to module that does this if it isn't hard coded in C?). I tried the above with what I thought should have been legal indenting -- "unix-like" where one indent is four spaces, multiple indents are made up of tabs (equivalent to eight spaces) for the even portion of the indent, and an actual four spaces make up the the odd remainder (if any). Seems that the above setting complained about this. I'm looking at all this to set up how my editor handles python files. I figure that I should make the default behavior be to have all file with mac line endings use tabs for indentation, and have tabs display as the equivalent of four spaces. Opening files with other styles/line-endings that have consistant indentation would present a dialog asking if you wish to convert them. Inconsistant styles would just open with a warning fix the indentation. To simplfy things for those working on files that are intended for other systems, the path name will be parsed, and if one of the folders is the path is either "unix" or "ibm" then the defualt behavoir will be over-riden, and the file will open for editing in that style/line-endings. What should the default style be for ibm stuff. Any comments or suggestion would be appreciated. Tom

5 6

Re: Building PythonMac
by Jack Jansen Nov. 28, 2000

Nov. 28, 2000

Recently, "Christian Reyes" <christian(a)rocketnetwork.com> said: > Hey Jack, > Not sure if you recall the thread we shared last week about the exception > handling across code fragments. But I'm still working on the issue and > could use some more advice. Right now I'm looking at two alternatives to > addressing the problem. My first alternative involves building the 1.5.2 > code against the MSL shared runtime dll. But before I attempt that I need > to be able to build the distributed source. Which brings me to my first > issue. > I'm trying to build the 1.5.2 source using Code Warrior 5.3 and am having > some difficulty. > You were right, most of my problems are from conflicts with the GUSI (2.12) > headers and the MSL headers from 5.3. > Do you remember what version of CW you used to build the 1.5.2 pythoncore > and can you give me some suggestions on how to handle building GUSI? Is > there another version of Gusi that might be more agreeable with the CW5.3 > MSL headers? It is long ago, so I'm not 100% sure what I say here is correct, but I think that 1.5.2 was built with CW Pro 5.0 or 5.1. The :Mac:Demo:building.html document should have the details. I used a modified CWGUSI 1.5.2, which you can still find on the ftp site, in ftp://ftp.cwi.nl/pub/jack/python/mac/old . > My second question is, what version of CW did you use to build the 2.0 > source? And would you anticipate the 2.0 release having compile issues with > the GUSI headers? The 2.0 source distribution should build with CW Pro 5.3 and GUSI 2.1.1. Building with CW Pro 6 shouldn't be much of a problem, except for GUSI. You'll need a modified GUSI 2.1.3. I'll put one up on the ftp site later tonight. -- 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] Indentation Styles
by Jack Jansen Nov. 28, 2000

Nov. 28, 2000

The Official Python Way is to use spaces for indentation, because Guido says so. However, Just and myself being the people we are, and both abhorring spaces used in places where tabs should be used have so far refrained from converting te Mac-specific parts of MacPython, so these are still tab-indented. And the contributions will follow either the space or the tab-convention, depending on the taste of the contributor. We should really adopt the official python convention, but I'm rather reluctant to do so. I mainly use BBEdit for my editing, and while it has the "auto-convert tabs to spaces" option this is only half the job, I want to have an easier way of undenting that typing four backspaces. Moreover, selecting a whole line is a pain in the behind, because my hand consistently seems to manage to miss the first space on the line:-( -- 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] Carbon modules (for OSX and also OS8|9)
by Jack Jansen Nov. 28, 2000

Nov. 28, 2000

> But the other question was whether it might be a good idea NOT to > hide the packaging. Two things come to mind: > > [1] Possible Module name clashes -- > ... You're absolutely right. Let's leave the modules in the Carbon package (and then it's a question whether we should put them in sys.modules, I think not). It's much cleaner. -- 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

BuildApplet issue
by Francois Granger Nov. 28, 2000

Nov. 28, 2000

I am in the group of french translator for Python doc. They did a script for preparing LaTex source. I used to use previous versions without much problem. With this one, when I drag&drop it on BuildApplet, this one complains : 'Syntax error in script "HD:PyDoc:prepare_tex15.py"' I hacked it to have a file open dialog instead. But this seems strange. #!/usr/bin/env python """ SYNOPSIS Usage: prepare_tex [-h/-?/--h/--help] [-d] [--version=value/-v value...] \ [--translator=value/-t value...] [-lang=value...] [--output_file=value/-o \ value...] latex_src_file **-h/-?/--help/--h** Show this little help **-d** Show the whole doc string of this script **--version=value (-v)** *default version=2.0* Set the version of the translation **--output_file (-o)** *default outputfile=inputfile+_+lang* Set the output file destination **--translator=value (-t)** *default translator='unknown'* Set the name of the translator **-lang=value(-l)** *default lang=FR* Prepare for French(fr) or other, as you want For most parameters an interactive input will be given if the arg is not in the command line. Except output_file which is STDOUT by default. Result of this script : For each paragraph of the source file given in the command line: %%% TRANSLATION ORIG % original lines % of the paragraph %%% TRANSLATION FR # ready to write here %%% /TRANSLATION And we add a translation INFO paragraph in the header: %%% TRANSLATION INFO :\n") % Original : release 2.0 % Translation : CVS Id % Translator : Unknow % Language : FR FILE $Id: prepare_tex.py,v 1.5 2000/10/24 20:25:25 olberger Exp $ DESCRIPTION *Prepare_tex* Generate to output a new Latex file with comments and tokens for translation. AUTHOR Odile Bénassy, developped for the French Python Translation Workgroup. Contributions by Olivier Berger and Regis Leroy LICENCE GNU General Public License HISTORY $Log: prepare_tex.py,v $ Revision 1.5 2000/10/24 20:25:25 olberger Typo et correction mineure Revision 1.4 2000/10/24 14:36:14 olberger Ajout version améliorée encore par Régis Leroy - Revision 1.4 2000/10/24 15:30:00 rage o All args can be given in command line, if an arg is missing there is an interactive input. o To get the doc string the command line arg is now -d o add --help and --h to command line args. o add a TODO section - Revision 1.3 2000/10/22 10:22:25 rage o Doc strings corrections, gendoc compatibility, cosmetic changes. o command line parser o add possibility of changing the 'FR' token - Revision 1.2 2000/10/23 obenassy o Interactive input of header parameters o Header generation - Revision 1.1 2000/10/18 15:47:07 oberger o some improvements on limit cases o CVS integration - Version 1.0 2000/10/18 15:47:07 Original author : Odile Bénassy, developped for the French Python Translation Workgroup. (http://sourceforge.net/project/frpython). TODO - a --reverse function to get the original copy ? - verifying existence of the output file before writing on it. - add a space after 'release' in the output? """ ######### # IMPORTS import sys, string, re, os, getopt ######### # GLOBALS BLANK = re.compile('^[%s]*$' % string.whitespace) LANG_TOKEN = "" TRANSLATOR = "" VERSION = "" OUTPUTFILE = "" __author__ = "Odyle Benassy" # CVS crud __version__ = "$Revision: 1.5 $" # $Source: /cvsroot/frpython/translation/fr/outils/prepare_tex.py,v $ __usage__ = """ Usage: prepare_tex [-h/-?/--h/--help] [-d] [--version=value/-v value...] \ [--translator=value/-t value...] [-lang=value...] [--output_file=value/-o \ value...] latex_src_file **-h/-?/--help/--h** Show this little help **-d** Show the whole doc string of this script **--version=value (-v)** *default version=2.0* Set the version of the translation **--output_file (-o)** *default outputfile=inputfile+_+lang* Set the output file destination **--translator=value (-t)** *default translator='unknown'* Set the name of the translator **-lang=value(-l)** *default lang=FR* Prepare for French(fr) or other, as you want For most parameters an interactive input will be given if the arg is not in the command line. Except output_file which is STDOUT by default. Result of this script : For each paragraph of the source file given in the command line: %%% TRANSLATION ORIG % original lines % of the paragraph %%% TRANSLATION FR # ready to write here %%% /TRANSLATION """ ########### # FUNCTIONS def handle_line(para, line, converted_lines): """ handle a line in the input. if inside a paragraph, adds it to the current paragraph : para. Else, if terminates the current paragraph (blank line), return the converted paragraph into converted_lines. *para* -- The current paragraph *line* -- the original line, should be a text line without '\n'. *converted_lines* -- the addition of all the converted lines made by this function before. **Warning** : para and converted_lines must be changed in place (with append()). """ # if it's a blank line, ending the paragraph # dump the converted paragraph if BLANK.match(line): if para: # insert header converted_lines.append("%%% TRANSLATION ORIG\n") # insert converted paragraph for lineOfPar in para : lineOfPar = '% ' + lineOfPar lineOfPar = lineOfPar + '\n' converted_lines.append(lineOfPar) # end the current paragraph (changed in place) para[:] = [] # insert footer converted_lines.append("%%% TRANSLATION ") converted_lines.append(LANG_TOKEN) converted_lines.append("\n \n") converted_lines.append("%%% /TRANSLATION\n") # then add back the original blank line line = line + "\n" converted_lines.append(line) # case of a line inside a paragraph # just add it to the current paragraph else: para.append(line) def prepare_para_orig_tex(lines): """ Converts paragraphs (from arg lines) in commented blocks. Return all the converted lines. Use handle_line to treat each line and to create the converted lines text. *lines* -- The whole text to handle """ # current paragraph para = [] # result of conversion of lines of the file converted_lines = [] # header converted_lines.append("%%% TRANSLATION INFO :\n") converted_lines.append("%% Original : release %s\n" % VERSION) converted_lines.append("%% Translation : $%s$\n" % "Id") converted_lines.append("%% Translator : %s\n" % TRANSLATOR) converted_lines.append("%% Language : %s\n\n" % LANG_TOKEN) # loop through the file for line in lines: # handle correctly a file not terminated with \n, not to # truncate last char if line[-1] == '\n' : line = line[:-1] handle_line(para, line, converted_lines) # handle the last paragraph properly (termination of the last # paragraph) # check if the last line is not blank, which means that the last # paragraph needs to be copied on the output. line = lines[-1] if not BLANK.match(line): handle_line(para, '', converted_lines) converted_lines = converted_lines[:-1] return converted_lines def main_parseopts(): """ Handle args given in the command line. Return the file name or exit the script if there is none or if a -h, -v or -? was given. -l or --lang can change the LANG_TOKEN used in the output of the script. """ global LANG_TOKEN global TRANSLATOR global VERSION global OUTPUTFILE # Process command line arguments try: optlist, args = getopt.getopt(sys.argv[1:], 'd?hl:v:t:o:',('lang=','version=','translator=','output_file=','h','he lp')) except getopt.error, str: sys.stderr.write('prepare_tex: %s\n' % str) sys.stderr.write(__usage__) sys.exit(-1) for opt in optlist: if opt[0] == '-d': print __version__ print print __doc__ sys.exit(0) elif (opt[0] == '-h') or (opt[0] == '--h') or(opt[0] == '--help') \ or (opt[0] == '-?'): print __usage__ sys.exit(0) elif (opt[0] == '-t') or (opt[0]=='--translator'): TRANSLATOR = opt[1] elif (opt[0] == '-o') or (opt[0]=='--output_file'): OUTPUTFILE = opt[1] elif (opt[0] == '-v') or (opt[0]=='--version'): VERSION = opt[1] elif (opt[0] == '-l') or (opt[0]=='--lang'): LANG_TOKEN = opt[1] if not args: sys.stderr.write\ ('\nError: prepare_tex: You must pass at least one Latex file.\n') sys.stderr.write(__usage__) sys.exit(1) else: return args[0] def run(): global TRANSLATOR global VERSION global OUTPUTFILE global LANG_TOKEN inputfile = main_parseopts() if not LANG_TOKEN: LANG_TOKEN = raw_input('Language: [FR] ') if not LANG_TOKEN: LANG_TOKEN = "FR" if not VERSION: VERSION = raw_input\ ('Release of the original on which you apply the translation: [2.0]? ') if not VERSION: VERSION = "2.0" if not TRANSLATOR: TRANSLATOR = raw_input('Your name: ') if not TRANSLATOR: TRANSLATOR = "Unknown" lines = open(inputfile).readlines() # if the file is empty, need to do nothing if lines : res = prepare_para_orig_tex(lines) if not OUTPUTFILE: OUT = sys.stdout else: OUT = open(OUTPUTFILE,'w') for line in res : OUT.write(line) if __name__=='__main__': run() # $Log: prepare_tex.py,v $ # Revision 1.5 2000/10/24 20:25:25 olberger # Typo et correction mineure # # Revision 1.4 2000/10/24 14:36:14 olberger # Ajout version améliorée encore par Régis Leroy # # Revision 1.3 2000/10/23 21:45:32 olberger # Intégration des contributions de Régis Leroy # # Revision 1.1.2.1 2000/10/23 21:00:30 olberger # Intégration contribution Regis Leroy basé sur révision 1.1 # # Revision 1.2 2000/10/23 20:36:08 olberger # Intégration V1.2 d'Odile # # Revision 1.1 2000/10/18 17:45:45 olberger # Ajout scripts pour gestion des commentaires dans les documents traduits # -- "Faites des phrases courtes. Un sujet, un verbe, un complément. Quand vous voudrez ajouter un adjectif, vous viendrez me voir." - Georges Clemenceau, 1841-1929, médecin et homme politique français. Consignes aux journalistes de "L'Aurore". d'après <http://www.sit.ulaval.ca/pagespersonnelles/phf/pensee.html>

3 3

Re: Fix for time in 1.5.2c1
by Vincent Marchetti Nov. 28, 2000

Nov. 28, 2000

Russell Owen wrote: ------------------------------- I'm just starting to try to read file creation times and things aren't working as expected. For a file created Jul 5, 2000: >>> ap = "RussMain:Desktop Folder:test" >>> ct = os.stat(ap)[stat.ST_CTIME] >>> ct 3045641098.0 >>> time.localtime(ct) (1996, 7, 6, 11, 24, 58, 5, 188, -1) >>> time.gmtime(ct) (1996, 7, 6, 19, 24, 58, 5, 188, -1) I looked back and found a discussion that was probably about this same problem, but no solution. Any suggested patches? ... ----------------------------------- It was unclear from the post whether you knew that this problem was fixed in Python 2.0, (it is), but apparently you can't use 2.0 because of Tk problems. The solution is to add to the 'ct' variable the number of seconds in 4 years (i.e. 4 * 365 *24 *60 *60) Apparently, the "stat" clock is starting at Jan 1, 1904, while the time.localtime conversion is assuming a start date of Jan 1, 1900. Vince Marchetti

1 0