15 |
16 |
17 | paper template
18 |
19 |
20 |
21 |
22 | Michael McLay
23 |
24 |
25 | Last modified: Tue Oct 8 18:06:32 EDT
26 |
27 |
28 |
29 |
--------------------------------------------------------------------------------
/conferences/2000-01/hadar.html:
--------------------------------------------------------------------------------
1 | Open Source and Venture Capital
2 |
3 | Keynote by Hadar Pedhazur.
4 |
5 |
Open Source and Venture Capital have found each
6 | other. Witness the detailed article in the January 2000
7 | issue of Linux Magazine. However, in this case, not only has
8 | Venture Capital found a Python company, but to a large
9 | degree, Python created a Venture Capitalist!
10 |
11 |
This talk begins with the history of Hadar Pedhazur's
12 | discovery and use of Python at the Union Bank of Switzerland
13 | (UBS), which led to his discovery of Digital Creations. From
14 | that, the leap to Venture Capitalist was natural and obvious
15 | :-).
16 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr9.html:
--------------------------------------------------------------------------------
1 |
2 |
Using OO-Browser
3 |
4 |
5 |
6 | 
7 |
8 | Using OO-Browser
9 |
10 |
11 | Building an environment
12 |
13 | Common commands
14 |
15 |
16 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr5.html:
--------------------------------------------------------------------------------
1 |
2 |
Class browsing
3 |
4 |
5 |
6 |
7 |
8 | Class browsing
9 |
10 | Classes are viewed in a list format, with one class per list line.
11 | Class children and parents can be expanded by hitting 'c' or 'p' keys
12 | respectively. Multiple inheritance is fully supported.
13 |
14 |
15 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/papers/tismers/spcpaper-Dateien/filelist.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/index.html:
--------------------------------------------------------------------------------
1 |
2 |
Abstract
3 |
4 |
5 |
6 |
7 |
8 | Abstract
9 |
10 |
11 | This document presents a tool for browsing Python source code. An
12 | existing powerful browser, OO-Browser, has been extended to support
13 | Python. An introduction to its usage is given, and the current
14 | limitations are described.
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr1.html:
--------------------------------------------------------------------------------
1 |
2 |
Abstract
3 |
4 |
5 |
6 |
7 |
8 | Abstract
9 |
10 |
11 | This document presents a tool for browsing Python source code. An
12 | existing powerful browser, OO-Browser, has been extended to support
13 | Python. An introduction to its usage is given, and the current
14 | limitations are described.
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/posters/bak/tismer.html:
--------------------------------------------------------------------------------
1 |
2 | Index of /IPC8/posters/tismer
3 |
4 | Index of /IPC8/posters/tismer
5 | 
Name Last modified Size Description
6 |
7 | ![[DIR]](/icons/back.gif)
Parent Directory 02-Feb-00 00:20 -
8 | ![[ ]](/icons/unknown.gif)
tismer.doc 14-Feb-00 16:53 28k
9 | ![[TXT]](/icons/text.gif)
tismer.htm 14-Feb-00 16:53 4k
10 | ![[ ]](/icons/layout.gif)
tismer.pdf 14-Feb-00 16:53 15k
11 |
12 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/posters/bak/wilson.html:
--------------------------------------------------------------------------------
1 |
2 | Index of /IPC8/posters/wilson
3 |
4 | Index of /IPC8/posters/wilson
5 | Name Last modified Size Description
6 |
7 | Parent Directory 02-Feb-00 00:20 -
8 | wilson.doc 14-Feb-00 16:53 39k
9 | wilson.htm 14-Feb-00 16:53 2k
10 | wilson.pdf 14-Feb-00 16:53 6k
11 |
12 |
--------------------------------------------------------------------------------
/conferences/1994-11/spam-vars.html:
--------------------------------------------------------------------------------
1 | Python pseudo vars convention:-)
2 |
3 | Part of the report on the NIST Python
4 | workshop software management session
5 |
6 |
ken.manheimer@nist.gov, 301 975-3539
7 | Original 20-Nov-1994, last mod 24-Nov-1994.
8 |
9 |
Code Fragment Example Vars
10 |
11 | We resolved that, in order to better represent the true python ethic,
12 | we should avoid nonsensical pseudo-variable names like foo
13 | and bar, and instead use more circus-conformant names, like
14 | spam and eggs. (The possibilities are endless.
15 | Those of you that don't like spam could always just use spam,
16 | spam, spam, spam, eggs, spam, and sausage...-)
17 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/posters/bak/karlsson.html:
--------------------------------------------------------------------------------
1 |
2 | Index of /IPC8/posters/karlsson
3 |
4 | Index of /IPC8/posters/karlsson
5 | Name Last modified Size Description
6 |
7 | Parent Directory 02-Feb-00 00:20 -
8 | karlsson.doc 14-Feb-00 16:52 28k
9 | karlsson.htm 14-Feb-00 16:52 5k
10 | karlsson.pdf 14-Feb-00 16:52 13k
11 |
12 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr6.html:
--------------------------------------------------------------------------------
1 |
2 | Class method browsing
3 |
4 |
5 |
6 |
7 |
8 | Class method browsing
9 |
10 | In OO-Browser terminology, browsing class methods is called displaying class
11 | features. To a class' features belong all the methods specific to the class,
12 | all the inherited classes and their methods, all the way to the root of the
13 | class tree.
14 |
15 |
16 |
--------------------------------------------------------------------------------
/conferences/1995-05/lutz.html:
--------------------------------------------------------------------------------
1 |
2 |
Mark Lutz Papers
3 |
4 | Papers by Mark Lutz
5 | Mark Lutz has contributed two documents for the
6 | workshop proceedings. The first paper, in Postscript format, is on KEL: C++/Python Integration. This
8 | is a review of Mark's experience with using Python as an embedded
9 | language.
10 |
11 | We asked Mark to provide a sneak preview of his book on Python.
12 | He obliged with an encapsulated Postscript format submission that
13 | contains a book preview for Using
14 | Pyton. The book should be ready for the publisher by the
15 | fall of 1995.
16 |
17 |
18 | We'll try to get an HTML version of the documents added to the
19 | proceeedings after the workshop.
20 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr19.html:
--------------------------------------------------------------------------------
1 |
2 |
If you already have OO-Browser
3 |
4 |
5 |
6 |
7 |
8 | If you already have OO-Browser
9 |
10 | Python support is in files python-browse.el, br-python.el and br-python-ft.el.
11 | You can just add these to your OO-Browser directory.
12 | Additionally, you need to replace br-env.el and br-init.el.
13 | Remove br-env.elc and br-init.elc.
14 | Then just setup you .emacs.
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr12.html:
--------------------------------------------------------------------------------
1 |
2 |
Limitations, bugs and future directions
3 |
4 |
5 |
6 |
7 |
8 | Limitations, bugs and future directions
9 |
10 |
11 | Limitations
12 |
13 | OO-Browser oddities
14 |
15 | Python specific bugs
16 |
17 | Future
18 |
19 |
20 |
--------------------------------------------------------------------------------
/conferences/1994-11/kickers.html:
--------------------------------------------------------------------------------
1 |
Session Kickers -- Python Workshop
2 |
3 | Session Kickers
4 |
5 |
6 | Tuesday
7 |
8 |
9 |
10 | - A Standard GUI API: Dave Brennan
11 |
12 |
- Interfacing to C++ and inheriting built-in types: Skip Montanaro
14 |
15 |
16 |
17 |
18 | Wednesday
19 |
20 |
21 |
22 | - Persistent Objects: Guido van Rossum
23 |
24 |
- Safe-Python: Steve Majewski
25 |
26 |
- Steering Committee Meeting: Michael McLay
27 |
28 |
29 |
30 |
31 | Thursday
32 |
33 |
34 |
35 | - Optimization, Static checks, and Compilation: Steve Majewski
36 |
37 |
- Software Management: Ken Manheimer
38 |
39 |
- Python and the World Wide Web: Paul Everitt
41 |
42 |
43 |
--------------------------------------------------------------------------------
/conferences/1994-11/vrsn-prop.html:
--------------------------------------------------------------------------------
1 | Python module versioning proposal
2 |
3 | Part of the report on the NIST Python
4 | workshop software management session
5 |
6 |
ken.manheimer@nist.gov, 301 975-3539
7 | Original 20-Nov-1994, last mod 24-Nov-1994.
8 |
9 |
Module Versioning
10 |
11 | While it does not particularly affect the intrinsic language
12 | structure, we found it easy and quick (and sensible:) to agree that
13 | module producers should assign a distinct version identifier to a
14 | conventionally named variable - i think we agreed on
15 | __version__ - within their modules. Sidestepping a
16 | slightly hairy (and probably premature) issue, we also agreed that it
17 | was not yet necessary to decide on a common format for the value,
18 | leaving that up to the module implementer.
19 |
20 | We left other python programming conventions and standards for another
21 | time.
22 |
--------------------------------------------------------------------------------
/conferences/1995-12/papers/bshomer/references.html:
--------------------------------------------------------------------------------
1 |
A Generic data collection system through WWW forms
2 |
3 |
4 | A Generic data collection system through WWW forms, based on a
5 | Python OOD program.
6 |
7 | References
8 |
9 |
10 |
11 | -
12 |
13 |
-
14 |
15 |
-
16 |
17 |
-
18 |
19 |
-
20 |
21 |
-
22 |
23 |
-
24 |
25 |
-
26 |
27 |
-
28 |
29 |
-
30 |
31 |
-
32 |
33 |
-
34 |
35 |
-
36 |
37 |
-
38 |
39 |
-
40 |
41 |
42 |
43 |
44 | Written by Benny shomer, The EBI.
45 | bshomer@ebi.ac.uk
46 |
47 |
48 |
49 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr15.html:
--------------------------------------------------------------------------------
1 |
2 | Python specific bugs
3 |
4 |
5 |
6 |
7 |
8 | Python specific bugs
9 |
10 | The Python browsing support is new, and may contain bugs. A carefully
11 | crafted multiline string can easily throw the parser out of sync, even
12 | if the source would still be valid Python code. Luckily Python syntax
13 | is easy to parse and write - most source code should be handled just
14 | fine. Incorrect parse will result in wrong results, but usually
15 | should not crash the program.
16 |
17 |
18 |
19 |
--------------------------------------------------------------------------------
/conferences/2000-01/tut/Beazley.txt:
--------------------------------------------------------------------------------
1 | From: David Beazley
2 | To: rmasse@cnri.reston.va.us
3 | Subject: Re: SWIG tutorial?
4 | Date: Thu, 19 Aug 1999 14:52:47 -0500 (CDT)
5 | Message-Id: <199908191952.OAA09659@gargoyle.cs.uchicago.edu>
6 | Mime-Version: 1.0 (generated by tm-edit 7.78)
7 | Content-Type: text/plain; charset=US-ASCII
8 | Content-Length: 527
9 |
10 | Roger Masse writes:
11 | >
12 | > After reviewing the evaluation forms, your tutorial rating was
13 | > perfect! You received all "very good" rating which was the
14 | > highest available.
15 | >
16 |
17 | Hmmm. That's excellent. Great news.
18 |
19 | > I anticipate the compensation package to be similar to last
20 | > year (a small honorarium and waived conference fees).
21 | >
22 | > Can I convince you to teach us about SWIG (V2)?
23 | >
24 |
25 | I can probably do a tutorial. As for Version 2.0, we'll see if I can
26 | get it written first (I'm not promising anything :-).
27 |
28 | Cheers,
29 |
30 | Dave
31 |
--------------------------------------------------------------------------------
/conferences/1994-11/BuiltInClasses/BuiltInClasses_9.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | 3. Current Status
5 |
6 |
7 |
8 | [Next] [Previous] [Top]
9 | Deriving Built-In Classes in Python
10 |
3. Current Status
11 | The vast majority of the code needed to implement the Object System Enhancements described in Section 2 has already been completed and is already being used extensively here at V.I. Corporation. The portions which have not already been completed are currently under development. I expect that entire system will be completed no later than January, 1995.
12 |
13 |
14 | Deriving Built-In Classes in Python - 22 DEC 94
15 | [Next] [Previous] [Top]
16 | Generated with CERN WebMaker
17 |
18 |
19 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr3.html:
--------------------------------------------------------------------------------
1 |
2 |
Supported languages
3 |
4 |
5 |
6 |
7 |
8 | Supported languages
9 |
10 | OO-Browser v02.09.11 claims support for all popular OO Languages on
11 | UNIX, giving the following list:
12 |
13 |
14 | - Eiffel
15 |
- C++
16 |
- Objective-C
17 |
- Common Lisp and its object system (CLOS)
18 |
- Java
19 |
- Smalltalk
20 |
- Info documentation
21 |
22 |
23 | A notable exception in this list is Python. This is now corrected, as
24 | I have taken the 02.09.11 source, and added support for Python,
25 |
26 |
27 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr8.html:
--------------------------------------------------------------------------------
1 |
2 |
Graphical views
3 |
4 |
5 |
6 |
7 |
8 | Graphical views
9 |
10 | Class hierarchy and features can also be displayed graphically using an
11 | external program xoobr. Multiple views can be open simultaneously.
12 | Figure 3.2 shows an example of xoobr display.
13 | Mouse clicks on the tree items will automatically display the corresponding
14 | source in the Emacs window.
15 |
16 |
17 | Figure 3.2: Graphical view of the classes. Selecting nodes will bring the
18 | corresponding source to editor window.
19 |
20 |
21 |
22 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr_contents.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
A Short Introduction to OO-Browser with Python<BR>
4 | Version 1.0
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | A Short Introduction to OO-Browser with Python
16 | Version 1.0
17 |
18 |
19 |
Harri Pasanen
20 |
21 |
May 1996
22 |
23 |
24 |
25 |
26 |
27 |
Contents
28 |
44 |
45 |
46 |
47 |
48 |
49 |
--------------------------------------------------------------------------------
/conferences/1994-11/BuiltInClasses/BuiltInClasses_1.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | Deriving Built-In Classes in Python
5 |
6 |
7 | [Next]
8 |
Deriving Built-In Classes in Python
9 |
10 | Donald Beaudry
11 |
12 | V.I. Corporation
13 | 47 Pleasant Street
14 | Northampton, MA 01060
15 |
16 | don@vicorp.com
17 |
18 |
19 | - 1. - Introduction
-
20 |
- 2. - Object System Enhancements
-
21 |
- 3. - Current Status
-
22 |
23 |
24 |
25 | Deriving Built-In Classes in Python - 22 DEC 94
26 | [Next]
27 | Generated with CERN WebMaker
28 |
29 |
30 |
--------------------------------------------------------------------------------
/conferences/1997-10/panel.htp:
--------------------------------------------------------------------------------
1 | Title: Panel on Commercial Opportunities for Python
2 |
3 |
Panel on Commercial Opportunities for Python
4 |
5 | The panelists were:
6 |
7 |
8 |
9 |
Al Vezza
Vice President
10 | CNRI
11 | Reston, VA
12 |
13 |
Jim Fulton
14 | Senior Programmer
15 | Digital Creations
16 | Fredricksburg, VA
17 |
18 |
Mark Lutz
19 | Python Writer/Trainer
20 | Boulder, CO
21 |
22 |
Robin Friedrich
23 | Representing Python Professional Sercives, Inc.
24 |
25 |
Jody Winston
26 | Representing Halliburton Energy Services, Inc.
27 |
28 |
Christian Tismer
29 | Applied Biometrics, Inc.
30 |
31 |
Dr. Chris Wright
32 | Deputy Director, ICU
33 | Director, Medical Informatics
34 | Monash Medical Centre, CLAYTON, VIC. Australia
35 | (unfortunately Dr. Wright couldn't make it at the last moment)
36 |
37 |
38 |
39 |
If you're interested in contributing a summary of the panel
40 | discussion, please send email to the program committee chairs at ipc6@python.org.
42 |
43 |
44 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/posters/bak/prescod.html:
--------------------------------------------------------------------------------
1 |
2 | Index of /IPC8/posters/prescod
3 |
4 | Index of /IPC8/posters/prescod
5 | Name Last modified Size Description
6 |
7 | Parent Directory 02-Feb-00 00:20 -
8 | prescod-power.doc 14-Feb-00 16:52 34k
9 | prescod-power.htm 14-Feb-00 16:52 4k
10 | prescod-power.pdf 14-Feb-00 16:52 11k
11 | prescod-types.doc 14-Feb-00 16:53 23k
12 | prescod-types.htm 14-Feb-00 16:53 3k
13 | prescod-types.pdf 14-Feb-00 16:53 9k
14 |
15 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr16.html:
--------------------------------------------------------------------------------
1 |
2 | Future
3 |
4 |
5 |
6 |
7 |
8 | Future
9 |
10 | OO-Browser is currently not supported software. The original author, Bob Weiner, has left Motorola, and no longer appears to support it. The latest official release (2.9.12) was actually built by yours truly, but I'm not maintaining the OO-Browser code outside of Python specific parts.
11 | This is my ToDo list for possible future versions:
12 |
13 |
14 | - Fix all remaining bugs
15 |
- See if I can get this to work on Windows NT Emacs
16 |
- Add better module support (I've thought about adding [modules] as another pseudo class, thus giving easy access to available modules and their documentation strings)
17 |
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/conferences/1997-10/program.htp:
--------------------------------------------------------------------------------
1 | Title: Program Information, Sixth International Python Conference
2 | Author: ipc6@python.org
3 |
4 |
Conference Program
5 |
6 | See the separate programs for details on each of the three
7 | conference sections:
8 |
9 |
10 |
11 |
Tuesday: Tutorials
12 |
13 |
14 | There are four parallel tracks, each consisting of a morning and an
15 | afternoon session. See the Tuturial
16 | Program for the full program.
17 |
18 |
Tuesday night, attendees are invited to the Reception.
19 |
20 |
21 |
22 |
Wednesday and Thursday: Paper
23 | Sessions
24 |
25 | Refereed papers, invited talks, short talks, and a panel
27 | on commercial opportunities for Python.
28 |
29 |
Wednesday night, attendees are invited to the Conference
30 | Banquet.
31 |
32 |
33 |
34 |
Friday: Developers' Day
35 |
36 | We are now open for suggestions for specific topics to be discussed
37 | on the Developers' Day - see the program.
38 |
39 |
40 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr4.html:
--------------------------------------------------------------------------------
1 |
2 |
OO-Browser features
3 |
4 |
5 |
6 |
7 |
8 | OO-Browser features
9 |
10 | OO-Browsers functionality can be divided into Class browsing,
11 | Class method browsing, Function browsing, and Graphical views.
12 | Python browsing supports all of these.
13 | The main components of OO-Browser's XEmacs user interface are visible in the
14 | figure 3.1
15 |
16 |
17 | Figure 3.1: XEmacs user interface
18 |
19 |
20 |
21 | Class browsing
22 |
23 | Class method browsing
24 |
25 | Function browsing
26 |
27 | Graphical views
28 |
29 |
30 |
--------------------------------------------------------------------------------
/conferences/1994-11/attendees.html:
--------------------------------------------------------------------------------
1 |
Attendees -- Python Workshop
2 |
3 | Python Workshop Attendees
4 |
5 |
6 | brennan@hal.com (Dave Brennan)
7 | bwarsaw@CNRI.Reston.VA.US (Barry A. Warsaw)
8 | cbs@ascinc.com (Casper B. Stoel)
9 | cugini@speckle.ncsl.nist.gov (John Cugini)
10 | don@vicorp.com (Donald Beaudry)
11 | ebouck@qvarsx.er.usgs.gov (Eric Bouck)
12 | friedric@rsoc.rockwell.com (Robin Friedrich)
13 | guido.van.Rossum@cwi.nl (Guido van Rossum)
14 | jfulton@qvarsx.er.usgs.gov (Jim Fulton)
15 | jimstp@eeel.nist.gov (Jim St. Pierre)
16 | ken.manheimer@nist.gov (Ken Manheimer)
17 | lynch@osg.saic.com (Jim Lynch)
18 | mclay@eeel.nist.gov (Michael McLay)
19 | nick@osg.saic.com (Nick Seidenman)
20 | paul@cminds.com (Paul Everitt)
21 | rmasse@cnri.reston.va.us (Roger Masse)
22 | sdm7g@virginia.edu (Steven D. Majewski)
23 | skip@automatrix.com (Skip Montanaro)
24 | stoakley@server.cs.virginia.edu (Richard Stoakley)
25 | tnb2d@server.cs.Virginia.EDU (Tommy Burnette)
26 |
27 | Canceled:
28 |
29 | hantman_barry@caemac4.msd.ray.com (Hantman Barry)
30 | paisley@boulder.nist.gov (Scott Paisley)
31 | parks@eeel.nist.gov (Curt Parks)
32 | waterbug@epims1.gsfc.nasa.gov (Steve Waterbury)
33 |
34 |
35 | Python Workshop Info
36 |
--------------------------------------------------------------------------------
/conferences/1997-10/shorties.htp:
--------------------------------------------------------------------------------
1 | Title: Wanted: Short Talks
2 |
3 | Wanted: Short Talks
4 |
5 | Not everybody who's got an interesting project and would like to
6 | tell the world about it is willing to sit down and write a long paper.
7 | And not all projects are in a describable stage several months before
8 | the conference. Therefore, we have left space in the paper sessions program for short talks.
10 |
11 |
We have reserved an hour and a half, enough for 15 talks of 10
12 | minutes each. The rules are simple: you submit a one-page abstract
13 | (absolutely not longer!) in plain text via email to the program
14 | committee by September 19. You receive notification of acceptance two
15 | weeks later. At the conference, you can present for 7 minutes, after
16 | which you are cut off and the audience is given three minutes for
17 | questions. No live demos please (use the breaks!); plain overhead
18 | transparencies only.
19 |
20 |
Content-wise, anything goes, as long as it is deemed interesting
21 | for a room full of Python users and developers, and as long as the
22 | content is technical, not marketing material.
23 |
24 |
Send your submissions by September 19 to: ipc6-papers@python.org.
26 |
27 |
28 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr18.html:
--------------------------------------------------------------------------------
1 |
2 |
Complete install
3 |
4 |
5 |
6 |
7 |
8 | Complete install
9 |
10 | If you have no previous installation of OO-Browser, or wish to upgrade
11 | all of the files to the latest version, you should follow the
12 | installation instructions in BR-README file.
13 | If you just want to give it a test drive, you can take the following
14 | steps.
15 |
16 | tar xzvf oo-br-2.9.12.tar.gz
17 |
18 | If you want to have the graphical tree view of your classes, you must
19 | build the auxiliary program xoobr. If you are on a Solaris machine,
20 | you are in luck, just do make xoobr. Otherwise you will have to
21 | modify your makefile. Copy the resulting executable, xoobr
22 | somewhere to your path. Again, if you are running XEmacs, chances are
23 | that xoobr is already installed, and you can skip this step.
24 |
25 |
26 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr2.html:
--------------------------------------------------------------------------------
1 |
2 |
Introduction to OO-Browser
3 |
4 |
5 |
6 |
7 |
8 | Introduction to OO-Browser
9 |
10 | OO-Browser is an object oriented browser for multiple programming languages,
11 | implemented under Emacs editor, mainly in Elisp.
12 | As Bob Weiner says in the documentation:
13 |
14 | The OO-Browser is a multi-windowed, interactive object-oriented
15 | class browsersimilar in use to the well-known Smalltalk browsers. It is
16 | unique in a number of respects foremost of which is that it works well with a
17 | multiplicity of object-oriented languages. It provides both textual
18 | views within an editor and graphical views under the X window system.
19 |
20 | OO-Browser was developed during 1990-95 by Bob Weiner at Motorola Inc.
21 | Motorola has donated the program to the Free Software Foundation under the
22 | terms of the GNU Public License.
23 |
24 |
25 |
--------------------------------------------------------------------------------
/conferences/1994-11/wwwpapers.html:
--------------------------------------------------------------------------------
1 |
WWW Papers -- Python Workshop
2 |
3 | WWW Papers
4 |
5 | Here are some papers from the WWW Conference that might be of use
6 | in developing the Python WWW interface.
7 |
8 |
24 |
25 | The common code paper references a WWW page, Status
27 | of the World-Wide Web Library of Common Code" In this page the
28 | paper,
30 | "Multi Threaded Clients" is presented.
31 |
32 | A set of papers that were my personal favorites from the WWWF'94
33 | conference is available here .
35 |
36 |
37 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr14.html:
--------------------------------------------------------------------------------
1 |
2 |
OO-Browser oddities
3 |
4 |
5 |
6 |
7 |
8 | OO-Browser oddities
9 |
10 | Sometimes OO-Browser may end up in a state, where there are variables
11 | and structures incorrectly initialized in the memory. Then it will
12 | cease to function correctly, displaying seemingly unrelated error
13 | messages. This can happen if you interrupt an operation, jump to a
14 | buffer not expected by OO-Browser, and for other reasons. Sometimes
15 | the only remedy is to exit Emacs and start again. Sometimes a
16 | combination of C-c C-r, C-c C-l keystrokes will recover from the
17 | situation.
18 | OO-Browser seems to work best with XEmacs, especially the mouse
19 | support is better. I have tried it with FSF Emacs as well, with mixed
20 | results. Under Emacs 19.29 on Alpha-OSF 3.2, I managed to get FSF
21 | Emacs to dump core. Under Linux however, Emacs 19.29 seems to work
22 | fine.
23 |
24 |
25 |
--------------------------------------------------------------------------------
/conferences/1994-11/agenda.html:
--------------------------------------------------------------------------------
1 |
Short Agenda -- Python Workshop
2 |
3 | Short Agenda
4 |
5 | See also the annotated agenda.
6 |
7 | Tuesday November 1, 1994
8 |
9 |
10 | 8:30AM The "It's..." Man
11 | 8:35AM Donuts, coffee, and introduction
12 | 9:00AM Welcome Speech by the Workshop Chair
13 | 9:30AM "Position Statements" by all attendees
14 | 11.30AM Discussion of the Agenda
15 |
16 | 12:00AM Lunch
17 |
18 | 1:30PM A Standard GUI API
19 | 3:00PM Interfacing to C++ and inheriting built-in types
20 | 4.55PM The Spanish Inquisition
21 | 5:00PM Adjourn for the day
22 |
23 | 6:30PM Dinner and discussion over a beer or two -- TBD
24 |
25 |
26 | Wednesday November 2, 1994
27 |
28 |
29 | 8:30AM Donuts, coffee, and discussion
30 | 9:00AM Persistent Objects
31 | 10:30AM Safe-Python
32 |
33 | 12:00AM Lunch
34 |
35 | 1:30PM Steering Committee Meeting
36 | 5:00PM Adjourn for the day
37 |
38 | 6:30PM Spam -- TBD
39 |
40 |
41 | Thursday November 3, 1994
42 |
43 |
44 | 8:30AM Donuts, coffee, and discussion
45 | 9:00AM Optimization, Static checks, and Compilation
46 | 10:30AM Software Management
47 |
48 | 12:00AM Lunch
49 |
50 | 1:30PM Python and the World-Wide Web
51 | 3:30PM Adjourn and informal discussion
52 | 5:00PM And Now For Something Completely Different
53 |
54 |
55 | Python Workshop Info
56 |
--------------------------------------------------------------------------------
/conferences/2002-02/papers/toc.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 | Python 10
4 |
20 |
21 |
22 |
37 |
38 |
39 |
40 |
--------------------------------------------------------------------------------
/conferences/2000-01/tut/Mc_Grath.txt:
--------------------------------------------------------------------------------
1 | From: Sean Mc Grath
2 | To: rmasse@cnri.reston.va.us (Roger E. Masse)
3 | Subject: Re: XML tutorial?
4 | Date: Fri, 20 Aug 1999 09:17:54 +0100
5 | Message-Id: <3.0.6.32.19990820091754.00a69e40@gpo.iol.ie>
6 | Mime-Version: 1.0
7 | Content-Type: text/plain; charset="us-ascii"
8 | Content-Length: 1056
9 |
10 | Roger,
11 |
12 | Thank you very much for the invite back.
13 | Yes, I will do it. My book "XML Processing with Python"
14 | may even be on the shelves by then.
15 |
16 | regards,
17 | Sean
18 |
19 |
20 | At 03:52 PM 8/19/99 -0400, you wrote:
21 | >
22 | >Hello Sean and Paul,
23 | >
24 | > I again have been tasked with being tutorial chair for
25 | >the upcoming Python conference to be held in the DC area during
26 | >the last week in Jan 2000. After discussions with Guido,
27 | >we've decided to invite back the highest rated tutorial
28 | >presentors to either re-deliver a polished up version last years
29 | >tutorial, or possibly a brand new tutorial.
30 | >
31 | >After reviewing the evaluation forms, your tutorial rating was
32 | >perfect! You received all "very good" rating which was the
33 | >highest available.
34 | >
35 | >I anticipate the compensation package to be similar to last
36 | >year (a small honorarium and waived conference fees).
37 | >
38 | >Can I convince you to teach the XML tutorial again?
39 | >
40 | > -Roger
41 | >
42 | >
43 | >
44 |
45 | Developers Day co-Chair WWW9, April 2000, Amsterdam
46 | http://www.www9.org
47 |
48 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr17.html:
--------------------------------------------------------------------------------
1 |
2 | Appendix: Installation instructions
3 |
4 |
5 |
6 |
7 |
8 | Appendix: Installation instructions
9 |
10 | OO-Browser with Python support is available at
11 | location
12 | If you are an XEmacs user, the yet to be released XEmacs 19.14
13 | distribution should have an OO-Browser with Python support built in.
14 | (Current release date at the time of writing is June 7)
15 |
16 | All the documentation, including the Python specific usage, is
17 | available in the info pages of XEmacs.
18 | Older versions of XEmacs have OO-Browser installed by default but do
19 | not contain Python support. However, you will have the generic
20 | OO-Browser manuals available on-line in the info-pages, and Python
21 | usage is very similar to the general usage.
22 |
23 | Complete install
24 |
25 | If you already have OO-Browser
26 |
27 | Your .emacs setup
28 |
29 |
30 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr20.html:
--------------------------------------------------------------------------------
1 |
2 |
Your .emacs setup
3 |
4 |
5 |
6 |
7 |
8 | Your .emacs setup
9 |
10 | Put the following into your .emacs
11 |
12 | ;; OO-Browser setup
13 |
14 | (defvar br-directory "/usr/local/lib/xemacs-19.13/lisp/oobr/")
15 | ; Directory where the OO-Browser executable code is kept. It must end with a directory separator character.
16 |
17 | ;;; For FSF Emacs that does not have hyperbole uncomment the following
18 | ;; (setq load-path (cons (concat br-directory "hypb")) load-path)
19 |
20 | (autoload 'oo-browser (expand-file-name "br-start" br-directory)
21 | "Invoke the OO-Browser" t)
22 | (autoload 'br-env-browse (expand-file-name "br-start" br-directory)
23 | "Browse an existing OO-Browser Environment" t)
24 |
25 | ; Lets just enable browsing for C++ and Python
26 | ; for full list of languages, see br-env.el
27 | (defvar br-env-lang-avector
28 | '[("C++" . "c++-")
29 | ("Python" . "python-")]
30 | "Association vector of (LANGUAGE-NAME . LANGUAGE-PREFIX-STRING) elements of OO-Browser languages.")
31 |
32 | (global-set-key "\C-c\C-o" 'oo-browser)
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr13.html:
--------------------------------------------------------------------------------
1 |
2 |
Limitations
3 |
4 |
5 |
6 |
7 |
8 | Limitations
9 |
10 | OO-Browser does not cope well in a situation where a class with a same
11 | name is defined in multiple source files in an OO-browser environment.
12 | It is not possible to see where a certain class is used, this
13 | has-a type relation is unsupported.
14 | In the Python support a shortcut was done in that no nested classes
15 | are supported.
16 | The browsing is based on static analysis of the python source code.
17 | This excludes built-in modules from the browsing. However, it would
18 | be relatively simple to build a python program that generates a python
19 | source code containing at least the function names and documentation
20 | strings in a format parsable by OO-Browser. Another drawback with
21 | just browsing the source is that due to dynamic nature of Python, it
22 | is possible to add methods to class instances at runtime, or even to
23 | create new classes. Naturally browsing these kinds of dynamic
24 | structures is currently impossible. Extending OO-Browser to the
25 | direction of debugging a live Python process would enable live object
26 | browsing.
27 |
28 |
29 |
--------------------------------------------------------------------------------
/conferences/1997-10/accomodations.htp:
--------------------------------------------------------------------------------
1 | Title: Hotel and Travel Information, Sixth International Python Conference
2 | Author: ipc6@python.org
3 |
4 |
Hotel Information
5 |
6 | 
7 |
8 | The conference will be held at the Hyatt Sainte Claire Hotel. The hotel is booked full so if you
11 | haven't already booked your room, you will have to stay in another San
12 | Jose hotel.
13 |
14 |
Hyatt Sainte Claire Hotel
15 | 302 South Market Street
16 | San Jose, California 95113
17 |
18 |
Reservations: 1-800-233-1234
19 | Telephone: (408)885-1234
20 | Fax: (408)977-0403
21 |
22 |
(This is only relevant as a reminder on the rates for those who
23 | already booked:)
24 | Hotel rooms are $138 a night for a single or double room (not
25 | including room tax) at the special conference rate. You must make
26 | your reservations by Friday, Septembed 19 and mention the
27 | Python conference in order to receive this rate; the regular rate can
28 | be as high as $210+tax for a similar room. You will get the same rate
29 | for up to two days before and/after the conference.
30 |
31 |
32 |
33 |
34 | - Here's a map of the hotel's vicinity.
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/conferences/1994-11/BuiltInClasses/BuiltInClasses_3.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | 2. Object System Enhancements
5 |
6 |
7 |
8 | [Next] [Previous] [Top]
9 | Deriving Built-In Classes in Python
10 |
2. Object System Enhancements
11 | My solution enhances the current Python implementation by giving its users the ability to:
12 |
13 | - Easily convert between C data types and Python objects,
14 |
- Easily bind to most complex C data types,
15 |
- Provide symbolic bindings to symbolic constants,
16 |
- Derive built-in types from other built-in types, and
17 |
- Derive built-in classes from other built-in classes.
18 |
19 |
20 | - 2.1. - Type Converters
-
21 |
- 2.2. - Binding to Complex C Data Structures
-
22 |
- 2.3. - Deriving Built-in Types from Other Built-in Types
-
23 |
- 2.4. - Deriving Built-in Classes
-
24 |
- 2.5. - Deriving Python Classes from Built-in Classes
-
25 |
26 |
27 |
28 | Deriving Built-In Classes in Python - 22 DEC 94
29 | [Next] [Previous] [Top]
30 | Generated with CERN WebMaker
31 |
32 |
33 |
--------------------------------------------------------------------------------
/conferences/1996-06/IPCIV.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Next Python Conference
6 |
7 |
8 |
9 |
12 |
13 |
50 |
51 |
52 |
53 |
--------------------------------------------------------------------------------
/conferences/2000-01/python_closed.html:
--------------------------------------------------------------------------------
1 |
2 |
3 | 8th International Python Conference Registration
4 |
5 | Pre-registration is now closed. You may register and/or pay on-site
6 | beginning at 7:30am on Monday, 24 January 2000, at the Python Registration Desk located at the Key Bridge
7 | Marriott Hotel.
8 |
9 | The registration fee for registering and/or paying on-site is US$75.00 in addition to the costs of
10 | the days of the conference for which you choose to register.
11 |
12 |
13 | Registration fees are as follows:
14 |
15 | Tutorials (1 day;2 tutorials): $295
16 | Conference Days (2 days): $395/$195 students
17 | Developers' Day (1 day): $195
18 |
19 |
20 | Add $50 for non-PSA members. This will be applied as payment for a one-year PSA membership.
21 |
22 | Students with proper ID will receive $200 off the registration fee for the Conference only. Failure to pr
23 | ovide proper ID on-site will revoke the $200 credit.
24 |
25 |
26 | Your registration fee includes admission to the specific sessions/days for which you register. Each day in
27 | cludes continental breakfast, lunch and refreshment breaks. Tutorial attendees will receive the handouts f
28 | or all tutorials and Conference attendees will receive the conference proceedings.
29 |
30 | CANCELLATION/REFUND POLICY: Refunds are subject to a US$50.00 service
31 | charge. Cancellations and requests for refunds must be received by 1700ET, Wednesday,
32 | 19 January 2000. Refund requests will not be honored beyond this point.
33 | To cancel and request a refund, contact the Registrar:
34 | juliek@foretec.com
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/conferences/1995-12/papers/bshomer/figure2.html:
--------------------------------------------------------------------------------
1 |
A Generic data collection system through WWW forms
2 |
3 |
4 | [Abstract]
5 | [Introduction]
6 | [Methods]
7 | [Discussion]
8 | [References]
9 |
10 | Figure 2.
11 |
12 | The class "valids" - an example of the use of some of it's methods.
13 | 1. The class instance is invoked.
14 | 2. Ensuring that there is no attempt to invoke a shell.
15 | 3. Checking an item contains only ASCII128 characters.
16 | 4. Checking an item is numeric.
17 | 5. Checking an email address. The return value implies
18 | that the syntax is allright but the country domain does not exist.
19 | 6. Checking a nucleic acid (DNA) sequence.The return
20 | value implies the sequence contains an ambigous character wich is
21 | permitted in sequences only in special cases.
22 |
23 |
24 |
25 |
26 | Written by Benny shomer, The EBI.
27 | bshomer@ebi.ac.uk
28 |
29 |
30 |
31 | <![CDATA[
32 | 1.
33 | >>> from validations import valids
34 | >>> v = valids()
35 |
36 | 2.
37 | >>> v.safe('!#rm *')
38 | '#rm *'
39 |
40 | 3.
41 | >>> v.is_text('This is a text')
42 | 1
43 |
44 | 4.
45 | >>> v.is_numeric('number 69')
46 | 0
47 |
48 | 5.
49 | >>> v.is_email('bshomer@ebi.ac.zz')
50 | 2
51 |
52 | 6.
53 | >>> v.is_na_sequence('actaacggatacnnacagt')
54 | 2
55 |
56 |
--------------------------------------------------------------------------------
/conferences/1996-06/admin/index.htp:
--------------------------------------------------------------------------------
1 | Title: IPC-IV Admin Info
2 |
3 | <H1>IPC-IV Admin</H1>
4 |
5 |
6 | This is an unadvertised directory for IPC-IV administrators. Comments
7 | and suggestions to <A HREF="mailto:klm@cnri.reston.va.us">Ken
8 | Manheimer</A>. <P>
9 |
10 | <LI>The general reference location to point direct people seeking
11 | conference information is <A HREF="http://www.python.org/workshops/1996-06/"
12 | >http://www.python.org/workshops/1996-06/</A>. <P>
13 |
14 | <LI><A HREF="../papers/">Index</A> of submitted papers. <P>
15 |
16 | <LI><A HREF="../registered.html">List</A> of registered people's
17 | names. (The raw data is not in the public hierarchy, since it
18 | contains sensitive info.) <P>
19 |
20 | <LI>Relevant IPC-IV email contacts <A HREF="#majordomo-note">[1]</A>:
21 | <DT><A HREF="mailto:IPC-IV-admin@python.org">IPC-IV-admin@python.org</A>
22 | <DD>Distribution to the IPC-IV administrators, including central
23 | organizers and the Python steering committee, in general.
24 | <DT><A HREF="mailto:IPC-IV-registration@python.org"
25 | >IPC-IV-registration@python.org</A>
26 | <DD>Address to notify of IPC-IV registration.
27 | <DT><A HREF="mailto:IPC-IV-Submissions@python.org"
28 | >IPC-IV-Submissions@python.org</A>
29 | <DD>Address for submission and discussion of papers.
30 | <DT><A HREF="mailto:IPC-IV-attendees@python.org"
31 | >IPC-IV-attendees@python.org</A>
32 | <DD>Distribution including all registered attendees for the
33 | conference. (Updated manually, <EM>will</EM> lag.)
34 | </DL>
35 |
36 | <P>
37 |
38 | <FN ID="majordomo-note">[1] These mail distributions are handled by
39 | majordomo, which enables you to do things like get a list of
40 | subscribed addresses via email commands - see our
41 | <A HREF="../../../sigs/md_cmds.html">Majordomo quick guide</A>for
42 | instructions</FN>.
43 |
--------------------------------------------------------------------------------
/conferences/2000-01/Imputil_session.html:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <HEAD>
3 | <TITLE>Import Utilities DevDay Session</TITLE>
4 | </HEAD>
5 |
6 | <BODY>
7 | <CENTER><H1>Import Utilities DevDay Session</H1></CENTER>
8 |
9 | <P>This session will discuss the proposed changes to the import system.
10 | <P>These changes generally follow the model of Greg Stein's <CODE>imputil</CODE> module.
11 | Items which may (or may not) come up for discussion:
12 | <UL>
13 | <LI>"Policy" import hooks vs. "collection" import hooks.
14 | <LI>Bootstrapping the import system (<CODE>Sys.path</CODE>).
15 | <LI>Managing <CODE>Sys.path</CODE>.
16 | <LI>Archives.
17 | <LI>Packages.
18 | <LI>Packages with extension modules.
19 | <LI>Coexistence / cooperation with Distutils.
20 | <LI>Barry's behavior at the reception.
21 | </UL>
22 | <H3>Background</H3>
23 | <P>The current import system is a convoluted mass of Python and C code.
24 | It uses a "find" and "load" strategy, with either or both being hookable.
25 | However, the hooks are nearly impossible to understand, and in practice, nearly all import hooks are ad-hoc affairs that don't play well with other import hooks, or alternate distribution techniques (eg, freeze).
26 | <P>The current import system assumes that modules will be found in a file system.
27 | Importing from other sources (code archives, databases, URLs) requires going around the import system entirely.
28 | <P>In addition, the officially approved techniques for distribution of packages are largely ignored in practice, (not surprising, since the sanctioned techniques have changed repeatedly).
29 | One of the guiding goals of reforming the import system is to provide a simple but general framework that makes life easier for package authors and package users.
30 | </BODY>
31 | </HTML>
32 |
--------------------------------------------------------------------------------
/conferences/2000-01/tut/Chilvers.txt:
--------------------------------------------------------------------------------
1 | Subject: Re: Tutorial commitments
2 | From: Martin.Chilvers@trilogy.com
3 | To: Guido van Rossum <guido@CNRI.Reston.VA.US>
4 | Date: Thu, 30 Sep 1999 16:19:26 -0500
5 | X-Priority: 3 (Normal)
6 | X-MIMETrack: Serialize by Router on Mailman/Trilogy(Release 5.0.1|July 16, 1999) at 09/30/1999
7 | 04:48:24 PM
8 |
9 |
10 | Hi Guido,
11 |
12 | Excellent! Yep - just re-use the same bio as DSTC are paying my expenses,
13 | not my new employer (Trilogy)!
14 |
15 | Thanks,
16 |
17 | Martin
18 |
19 |
20 |
21 |
22 |
23 | Guido van Rossum <guido@CNRI.Reston.VA.US> on 09/29/99 10:19:31 AM
24 |
25 |
26 | To: Martin.Chilvers@trilogy.com
27 | cc: Guido van Rossum <ipc8-tut@python.org>
28 |
29 | Subject: Re: Tutorial commitments
30 |
31 | > Hi Guido/Roger,
32 | >
33 | > I would be more than happy to give another Fnorb tutorial at the next
34 | > Python conference, although due to current time constraints (we are
35 | working
36 | > on a long-term project with typicallly ridiculous schedules!!) it would
37 | > have to be just the same presentation as last year (ie. an introduction
38 | to
39 | > CORBA/Fnorb). I feel kinda bad repeating the same talk, but if you still
40 | > think it would be useful then I can definitely do it.
41 | >
42 | > Regards,
43 | >
44 | > Martin
45 |
46 | Thanks, Martin. I think the tutorial was well received last year, so
47 | it's well worth repeating. We'll reuse last year's abstract and bio
48 | unless we hear from you. (Hm, maybe you'll want to update the text a
49 | bit since you changed jobs, right? It's at
50 |
51 | http://www.foretec.com/python/workshops/1998-11/tut_fnorb.html
52 | http://www.foretec.com/python/workshops/1998-11/bio_chilvers.html
53 |
54 | --Guido van Rossum (home page: http://www.python.org/~guido/)
55 |
56 |
57 |
58 |
59 |
60 |
--------------------------------------------------------------------------------
/conferences/1995-12/announcement.html:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <HEAD>
3 | <TITLE>Third Python Workshop</TITLE>
4 | </HEAD>
5 |
6 | <BODY>
7 | <H2>Third Python Workshop</H2>
8 |
9 | <P>The workshop is over... There were over 60 attendees. See the <A
10 | HREF="./">session notes</A> and the <A HREF="papers/">collected
11 | papers</A>.
12 |
13 | <P>What follows is the original announcement:
14 |
15 | <P>
16 |
17 | <DT><strong>Dates:</strong>
18 | <DD>Python Workshop: 4-6 December 1995
19 | <DD>Python Tutorials: 4-6 December 1995
20 | <DD>GUI SIG Meeting: 7 December 1995
21 | <P>
22 | <DT><strong>Location:</strong>
23 | <DD><A href="registration.html#location">U.S. Geological Survey(USGS), Reston, Virginia</A>
24 | <DD>(Reston is close to Washington Dulles airport.)
25 |
26 | <P>
27 | <DT><strong>Cost:</strong>
28 | <DD><A href="registration.html#cost">$60 if you pay in advance...</A>
29 | <P>
30 | <DT><strong>Registration:</strong>
31 | <DD><A href="registration.html">look here...</A>
32 | <P>
33 | <DT><strong>The Details:</strong>
34 | <UL>
35 | <LI><A href="agenda.html">Workshop agenda</A>
36 | <LI><A href="gui-sig.html">GUI SIG meeting</A>
37 | <LI><A href="tutorials.html">Tutorials</A>
38 | <LI><A href="tshirt.html">T-shirts</A>
39 | </UL>
40 |
41 | <DT><strong>How can you help?</strong>
42 | <UL>
43 | <LI><A href="call_for_papers.html">Call for papers</A>
44 | <LI><A href="tutorials.html#instructors">Become a Python Instructor</A>
45 | <LI><A href="/psa/Joining.html">Join the PSA</A>
46 | <LI>Tell a friend...
47 |
48 | </UL>
49 |
50 | <HR>
51 | <A HREF="/"><IMG ALIGN=left SRC="/pics/python55.gif"></A>
52 | For comments on this web page, send email to
53 | <A HREF="mailto:webmaster@python.org"><I>webmaster@python.org</I></A>.
54 | For questions about Python, send email to
55 | <A HREF="mailto:python-help@python.org"><I>python-help@python.org</I></A>.
56 | </BODY>
57 |
--------------------------------------------------------------------------------
/conferences/1994-11/BuiltInClasses/BuiltInClasses_6.html:
--------------------------------------------------------------------------------
1 | <!-- Generated with CERN WebMaker 1.4 -->
2 | <HTML>
3 | <HEAD>
4 | <TITLE>2.3. Deriving Built-in Types from Other Built-in Types</TITLE>
5 | </HEAD>
6 | <BODY>
7 | <A NAME=HEADING5></A>
8 | <A HREF="BuiltInClasses_7.html">[Next] </A><A HREF="BuiltInClasses_5.html">[Previous] </A><A HREF="BuiltInClasses_3.html">[Up] </A><A HREF="BuiltInClasses_1.html">[Top] </A><P>
9 | 2. Object System Enhancements<P>
10 | <H3>2.3. Deriving Built-in Types from Other Built-in Types</H3>
11 | All CTypes contain a reference to a structure descriptor that describes the instances of the type. The description includes all attributes of the instance as well as the methods that are available. This allows the built-in object to fully describe itself with a single mechanism that treats attributes and methods equally. In the current Python implementation the only way to determine if a built-in object has a particular attribute is to attempt to set or get its value. Self describing objects can answer questions about attribute existence without having to attempt a set or get operation. This make it relatively easy to write generic routines for querying, printing, saving, restoring, and even browsing object hierarchies. Since it is possible to write generic methods for common operations, inheritance of behavior becomes much more useful and worthwhile to support. <P>
12 | CType objects encapsulate the idea of a super-type, where the super-type of an object indicates the type object from which behavior and attributes can be inherited. A mechanism is also provided that facilitates the initialization of sub-type objects from the values in the super-type.<P>
13 |
14 | <HR>
15 | <ADDRESS>Deriving Built-In Classes in Python - 22 DEC 94</ADDRESS>
16 | <A HREF="BuiltInClasses_7.html">[Next] </A><A HREF="BuiltInClasses_5.html">[Previous] </A><A HREF="BuiltInClasses_3.html">[Up] </A><A HREF="BuiltInClasses_1.html">[Top] </A><P>
17 | Generated with <A HREF="AboutWebMaker.html">CERN WebMaker</A>
18 | </BODY>
19 | </HTML>
20 |
--------------------------------------------------------------------------------
/conferences/1996-06/papers/h.pasanen/oobr11.html:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <head><title>Common commands</title></head>
3 |
4 | <BODY BGCOLOR=#FFFFFF TEXT=#0000FF>
5 | <A NAME="topic10">
6 | <A HREF="oobr_contents.html"><img align=center src="contents.gif" ALT="Contents"></A> <A HREF="oobr9.html#topic8"><img align=center src="up.gif" ALT="Up"></A> <A HREF="oobr10.html#topic9"><img align=center src="back.gif" ALT="Previous"></A> <A HREF="oobr12.html#topic11"><img align=center src="forward.gif" ALT="Next"></A> <HR><BR>
7 |
8 | <H2>Common commands</H2></A>
9 | <P>
10 | There is a wide variety of commands available in OO-Browser. The
11 | following list displays just the subset I personally use most.<P>
12 | <DL>
13 |
14 | <DT> C-c C-o
15 | <DD> or <B>M-x oo-browser</B> starts the browser.
16 | <DT> C-c C-e
17 | <DD> Rebuilds the viewed environment. This must be done when
18 | new classes or methods are added to the source code.
19 | <DT> C-c C-v
20 | <DD> Moves the point between editor and listing windows.
21 | <DT> a
22 | <DD> View the ancestors of the selected class, all the way up to root class.
23 | <DT> d
24 | <DD> View all the descendants of the selected class.
25 | <DT> f
26 | <DD> View the features of the current class. Class features are all
27 | the methods specific to the class and all the inherited classes and
28 | their methods.
29 | <DT> v
30 | <DD> View the source code of the selected item. The item can be
31 | either class or feature.
32 | <DT> e
33 | <DD> Edit the source code of the selected item.
34 | <DT> i
35 | <DD> Display the documentation string for the selected item.
36 | <DT> I
37 | <DD> Display all classes implementing the selected method.
38 | <DT> M-g
39 | <DD> Launch xoobr to give a graphical tree view of the current item.
40 | Multiple tree views can be open at the same time. If items features
41 | are displayed, those will be visible in the tree view as well.
42 | Clicking on the tree leaves will display the corresponding source
43 | location in the editor.
44 | <DT> M-k
45 | <DD> Kills all the xoobr windows.
46 | </DL>
47 | <P>
48 |
49 | </BODY></HTML>
50 |
--------------------------------------------------------------------------------
/conferences/1995-12/gui-sig.html:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <HEAD>
3 | <TITLE>Agenda for the first Python GUI SIG meeting </TITLE>
4 | </HEAD>
5 | <BODY>
6 |
7 | <H2>Agenda for the first Python GUI SIG meeting </H2>
8 |
9 | <UL>
10 | <H4>The GUI SIG meeting isn't a part of the Workshop proper. The goal of
11 | the meeting is to work towards a common (not standard) Python interface for GUI
12 | programming. Everyone is invited to join in on the meeting, but it
13 | will probably only be of interest to the developers of GUI modules.</H4>
14 | </UL>
15 | The meeting will <STRONG>not</STRONG> be held at USGS.
16 | <P>
17 | <STRONG>Location:</STRONG> At CNRI, 1895 Preston White Drive, Reston, Va, in
18 | the big conference room.
19 |
20 | <H3>9:00-3:00 on 7 December 1995</H3>
21 | <Strong>SIG Chair:</Strong> Jim Fulton
22 |
23 | <DL>
24 |
25 | <DT>9:00- 9:30
26 | <DD>A Continental Breakfast will be provided by CNRI.
27 |
28 | <DT>9:30- 9:40
29 | <DD>Introduction and discussion of agenda
30 |
31 | <DT>9:40-10:00
32 | <DD>Review and discuss the goals and objectives of the GUI SIG
33 |
34 | <DT>10:00-10:30
35 | <DD>Review and discuss the GUI checklist.
36 |
37 | <DT>10:30-10:50
38 | <DD>Break
39 |
40 | <DT>10:50-12:00, 1:00- 2:30
41 | <DD>Presentations of GUI alternatives
42 |
43 | These presentations should include an overview of the GUI and
44 | a presentation of a sample application, preferably the simple
45 | regression application. I know we'll have presentations for:
46 |
47 | <UL>
48 | <LI> Tkinter,
49 | <LI><A href="./ahlstrom2.html">Status of WPY, a portable GUI module for Python</A><BR>
50 | <LI> wxWindows, and
51 | <LI> PNET (HTML-based GUI)
52 | </UL>
53 |
54 | Any others?<P>
55 |
56 | It looks like we will have 30-45 minutes to spend for each
57 | alternative. I'd be very happy to see other alternatives
58 | presented.
59 |
60 | <DT>12:00- 1:00
61 | <DD>Lunch will be provided by CNRI
62 |
63 | <DT> 2:30- 3:00
64 | <DD>Where do we go from here.
65 |
66 | <DT> 3:00
67 | <DD>Adjourn
68 |
69 | </DL>
70 | </BODY></HTML>
71 |
--------------------------------------------------------------------------------
/conferences/1994-11/BuiltInClasses/AboutWebMaker.html:
--------------------------------------------------------------------------------
1 |
2 | <HEAD>
3 | <TITLE>WebMaker welcome</TITLE>
4 | </HEAD>
5 | <BODY>
6 | <A HREF="http://www.cern.ch/">CERN</A> -
7 | European Laboratory for Particle Physics -
8 | <A HREF="http://www.cern.ch/CERN/Divisions/ECP/PT/Welcome.html">PT Group</A><P>
9 | <A HREF="http://www.cern.ch/WebMaker/"><IMG SRC="wmpanel.gif" ALT="WebMaker,a FrameMaker to WWW Converter"></A>
10 | <H3>Configurable converter of FrameMaker documents to the World-Wide Web
11 | </H3>
12 | <HR>
13 | <P>The combination of WebMaker and FrameMaker enables you to publish
14 | simultaneously both the printed and the WWW versions of a document.
15 | WebMaker converts FrameMaker documents and books to a hypertext network
16 | of HTML files that may be viewed by World-Wide Web browsers
17 | such as Mosaic.
18 | <P>WWW is a global hypertext information network
19 | conceived at CERN, the European Laboratory for Particle Physics.
20 |
21 | <P>WebMaker translates FrameMaker entities such as imported and native
22 | graphics, mathematics, tables, figures, anchored frames, cross-references,
23 | character highlights, indices and footnotes.
24 | It generates tables of contents automatically,
25 | and transforms into graphical images elements that are unknown to HTML.
26 | The user has control over a number of conversion aspects:
27 | <UL>
28 | <LI> the rules for the breakup of the Frame document into the component HTML
29 | files;
30 | <LI> a panel of hypertext links to facilitate navigation within the WWW
31 | documents web;
32 | <LI> the rules for the mapping of paragraph and character formats to HTML
33 | constructs;
34 | <LI> the specification of material for selective inclusion in the FrameMaker
35 | or WWW document.
36 | </UL>
37 |
38 | <HR>
39 | WebMaker is Copyright (C) 1994 CERN Geneva
40 | <HR>
41 | <PRE>
42 | email: webmaker@cern.ch
43 | Tel: +41-22-767 9393
44 | Fax: +41-22-767 9196
45 | URL: <A HREF="http://www.cern.ch/WebMaker/">http://www.cern.ch/WebMaker/</A>
46 | </PRE>
47 | <HR>
48 | <ADDRESS> WebMaker - CERN Programming Techniques Group - 12 October 94</ADDRESS>
49 | </BODY>
50 |
--------------------------------------------------------------------------------
/conferences/2000-01/tut/Hammond.txt:
--------------------------------------------------------------------------------
1 | Subject: [Ipc8papers] My contributions
2 | From: "Mark Hammond" <mhammond@skippinet.com.au>
3 | To: <ipc8papers@cs.uchicago.edu>
4 | Date: Fri, 1 Oct 1999 11:35:14 +1000
5 | X-BPC-Relay-Envelope-From: mhammond@skippinet.com.au
6 | X-BPC-Relay-Envelope-To: <ipc8papers@cs.uchicago.edu>
7 | X-BPC-Relay-Sender-Host: CPE-24-192-23-89.vic.bigpond.net.au [24.192.23.89]
8 | X-BPC-Relay-Info: Message delivered directly.
9 | X-Priority: 3 (Normal)
10 | X-MSMail-Priority: Normal
11 |
12 | Sorry I am so damn disorganized. Depending on time-zones, I may just
13 | sneak in :-)
14 |
15 | At this stage I can commit to attending the conference, presenting a
16 | tutorial, and possibly an "invited talk".
17 |
18 | The tutorial will be "Advanced Python and COM", and content will come
19 | largely from the book, and have a different focus from the one Greg
20 | and I did a few years ago (which was too esoteric in hind-sight) -
21 | that is about all I know about it at this stage!
22 |
23 | The invited talk will possibly be as I discussed previously - a topic
24 | that is currently under non-disclosure agreement. It is almost
25 | certain that some disclosure restrictions will be lifted by then, but
26 | it is unclear it is will all be lifted. Im guessing that this talk
27 | would not be very long - anything up to an hour would be fine.
28 | Unfortunately I cant commit to too much here due to these bloody
29 | lawyers [If it makes Guido feel any better, Im having to deal with MS
30 | lawyers, and they seem to be making the CNRI lawyers look like a bunch
31 | of girl-scouts :-[
32 |
33 | Sorry for my disorganized state. As I am not submitting a refereed
34 | paper, I guess you dont need actual content yet. Please let me know
35 | when you need a copy of the tutorial itself. As I become aware of the
36 | NDA requirements being lifted I will let you know how the "invited
37 | talk" plans go...
38 |
39 | Thanks,
40 |
41 | Mark.
42 |
43 |
44 | _______________________________________________
45 | Ipc8papers mailing list - Ipc8papers@cs.uchicago.edu
46 | http://www.cs.uchicago.edu/mailman/listinfo/ipc8papers
47 |
--------------------------------------------------------------------------------
/conferences/1996-11/papers/GRAD/html/GRADcover.html:
--------------------------------------------------------------------------------
1 | <html><head><title></title></head><body><bodytext><p><a href="GRADpaper.book.html"><img src="fm2html-toc.gif">Table of Contents</a>
2 | <!-- This file was created with the fm2html filter.
3 | The filter is copyright Norwegian Telecom Research and
4 | was programmed by Jon Stephenson von Tetzchner. -->
5 |
6 | <title>Grammar-based Rapid Application Development (GRAD)</title></p>
7 | <h1><a name="HDT0">Grammar-based Rapid Application Development (GRAD)</a></h1>
8 | <b>Charlie Fly</b>
9 | <p>United Space Alliance</p>
10 | <p>600 Gemini Ave.</p>
11 | <p>Houston, Texas 77058</p>
12 |
13 | <h4><a name="HDR1">Abstract</a></h4>
14 |
15 | <p><em>The <i>Grammar-based Rapid Application Development</i> (GRAD)
16 | system is an interface generator between Python and legacy
17 | languages. To allow the interface generator to work with multiple
18 | languages, the interface is based upon a grammar for a given
19 | language. Currently, the C++ language has had its interface compiler
20 | created and successfully emits the necessary binding code to make C++
21 | code accessible from Python.</em></p>
22 |
23 | <p><em>The GRAD process is non-intrusive so the legacy code does not
24 | have to be modified in order for the interface to work. No
25 | superclasses or include files are added to the existing code and
26 | changes in the interface generator system itself do not require
27 | changes in the legacy code. Changes in the target legacy code
28 | naturally requires the regeneration of the interface but no manual
29 | editing of the generated interface is needed, so the interface
30 | generation can be made part of the build process.</em></p>
31 |
32 | <p><em>Using GRAD, the promise of entire new applications written
33 | rapidly in the high level language Python is attainable while still
34 | preserving much of the operational advantages of, and investments in,
35 | existing compiled and tested code.</em></p>
36 |
37 | <p><a href="GRADpaper.book.html"><img src="fm2html-toc.gif">Table of Contents</a>
38 | <a href="GRADpaper.html"><img src="fm2html-next.gif">Next Chapter</a></p></bodytext></body></html>
39 |
--------------------------------------------------------------------------------
/conferences/2000-01/tut/Ascher.txt:
--------------------------------------------------------------------------------
1 | Subject: Re: your tutorial
2 | From: David Ascher <da@ski.org>
3 | To: Guido van Rossum <guido@CNRI.Reston.VA.US>
4 | Date: Mon, 11 Oct 1999 11:04:08 -0700 (Pacific Daylight Time)
5 | X-X-Sender: da@mail.ski.org
6 |
7 | sorry, forgot. Here it is:
8 |
9 | Abstract:
10 |
11 | In this tutorial, I will aim to teach Python programmers what they need to
12 | know in order to use JPython effectively. This includes:
13 |
14 | - What JPython is, and how it works,
15 | - How JPython manages memory differently from CPython, and the
16 | consequences thereof,
17 | - How one installs JPython (including the JVM installation and which
18 | JVMs one should use and why),
19 | - How to find out about Java libraries, Javadoc, etc,
20 | - Running Jpython, jpythonc, etc. Making class files, applets,
21 | servlets,
22 | - The ways in which JPython and CPython differ, including the ability to
23 | make Python methods synchronized, Unicode handling, and the library
24 | coverage,
25 | - The smarts JPython applies to Java libraries (bean property handling,
26 | action handling, etc.),
27 | - How JPython (a language with multiple inheritance but no polymorphism)
28 | interacts with Java (a language with single inheritance and interfaces
29 | and polymorphism), including issues of type conversion and type
30 | casting.
31 | - How to embed JPython in a Java application, and how to extend JPython
32 | with new extension modules.
33 | - Code examples will be used throughout to illustrate each point,
34 | including examples which use the Swing GUI library.
35 |
36 | Working knowledge of Python will be assumed, and knowledge of Java is
37 | useful but not needed to follow the tutorial.
38 |
39 | Bio:
40 |
41 | David Ascher is the co-author with Mark Lutz of O'Reilly & Associates'
42 | _Learning Python_. He is also a Python consultant and trainer, and a
43 | vision researcher at the Smith-Kettlewell Eye Research Institute. His
44 | special interests include Object Oriented Programming methods,
45 | scientific computing, user interfaces and visualization.
46 |
47 |
48 |
--------------------------------------------------------------------------------
/conferences/2002-02/papers/welcome.htm:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <HEAD>
3 | <TITLE>Python 10</TITLE>
4 | </HEAD>
5 | <BODY LINK="#0000ff" bgcolor="#ffffff">
6 | <center><h2><FONT face="arial"><P>A Message from the Conference Chair</P></FONT></h2></center>
7 | <font face="arial">
8 | <p>
9 | Welcome to the Tenth International Python Conference. It's been quite a year! But here we are again, gathered together to show each other our best Python programs, ready to learn from the experts, and eager to hear the latest and greatest Python news. A lot of exciting things are going on this year! Python is stronger than ever on the Web: we have a Zope track as well as a Web Services conference track this year. I also see a lot of cool tools: my personal favorite is PyChecker, a utility that finds bugs in your program before Python finds them.
10 | </p><p>
11 | I'm glad that Python is used in so many different application areas that are not (yet :-) related to the Web, like gaming, education, and computer vision. I also see Python show up more and more in mission-critical situations, both on and off the Web. In other words, Python is growing up, and it's a lot of fun to be part of this development. Have you looked in a technical bookstore lately? The bookstore in my home town now has a whole shelf full of Python books, and from the number of Python books I've reviewed or refereed lately, I expect that soon they'll need a second shelf...
12 | </p><p>
13 | Of course, like any software project, Python itself is never finished. The release of Python 2.2 recently was a big step forward in the language's development -- but it's just another step in the long march to Python 3000, and I'm already looking forward to participating in the debate on Developers' Day about the next steps. At the same time I'm very happy with the way Python 2.2 came out! If you haven't tried it already, I encourage you to download it and
14 | </p><p>
15 | <font face="courier" size="7"><b> >>> import this</b></font>
16 | </p><p>
17 | Guido van Rossum<br>
18 | Conference Chair<br>
19 | Tenth International Python Conference
20 | </p>
21 |
22 |
23 | <FONT SIZE=3><P></P>
24 | </FONT></BODY>
25 | </HTML>
26 |
--------------------------------------------------------------------------------
/conferences/1996-06/directions.htp:
--------------------------------------------------------------------------------
1 | Title: Directions
2 | <center><IMG ALIGN=middle SRC="./locale.gif" ALT="Conference Locale">
3 | </center>
4 | <P>
5 | The tutorials will be held at the Holiday Inn in Pleasonton CA, on June 3rd. The conference plenary sessions and workshop group will be held
6 | at <A HREF="http://www.llnl.gov">Lawrence Livermore National Labs</A> near Livermore, California on June 4,5 and 6. Below is an overview map of the area. First priority will be to get to the hotel as it will be the base of operations before and during the conference.
7 |
8 | <H3>How to get to the Holiday Inn in Pleasanton from surrounding airports?</H3>
9 |
10 | <H4>From San Francisco International Airport</H4>
11 | Exit the airport to 101 Southbound and continue to the 92/880 Hayward/San Mateo Bridge exit. Continue over bridge approximately 10 miles to Highway 880 North exit. Follow 880 to Highway 238 East to I-580 East towards Stockton. Take the San Ramon Road/Foothill Road Exit. Continue on Foothill Road to first stop light and turn right on Dublin Canyon Road, then turn right into hotel parking lot. Exhale; you're turning blue.
12 |
13 | <H4>From San Jose International Airport</H4>
14 | Exit the airport to 101 Southbound and continue to I-680 North. Follow 680 for approximately 78 miles to Stoneridge Drive. Turn left on Stoneridge Drive to Foothill Road. Turn right on Foothill Road to Dublin Canyon Road, turn left on Dublin Canyon Road then take the first right into hotel parking lot. Park. Do not strike pedestrians.
15 |
16 | <H4>From Oakland International Airport</H4>
17 | Exit the airport and take Interstate 880 South to Eastbound 238. Follow 238 to Interstate 580 East towards Stockton. Take the San Ramon Road/Foothill Road Exit. Continue on Foothill Road to first stop light and turn right on Dublin Canyon Road, then turn right into hotel parking lot. Flip decompression switch on lower right dashboard. Warning: Do NOT touch exhaust manifold. Severe burn may result.
18 | <P>
19 | <HR>
20 | <center> <IMG ALIGN=bottom SRC="HInn.gif" ALT="Holiday Inn">
21 | <HR>
22 | <IMG ALIGN=middle SRC="./LLNLarea.gif">
23 | <HR>
24 | <IMG ALIGN=middle SRC="./LLNLdet.gif">
25 | <HR>
26 |
27 |
28 |
--------------------------------------------------------------------------------
/conferences/2000-01/proceedings/posters/wilson/wilson.htm:
--------------------------------------------------------------------------------
1 | <HTML>
2 | <HEAD>
3 | <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
4 | <META NAME="Generator" CONTENT="Microsoft Word 97">
5 | <TITLE>Pythonic Build</TITLE>
6 | </HEAD>
7 | <BODY LINK="#0000ff">
8 |
9 | <B><FONT SIZE=5><P ALIGN="CENTER">Pythonic Build</P>
10 | </B></FONT><P ALIGN="CENTER">Mark Wilson, <I>Bibliocraft Ltd</P>
11 | </I><FONT SIZE=2><P> </P>
12 | </FONT>
13 | <B><P> </P>
14 | <P> </P>
15 | </B><I><P>Build</I> is a software framework designed for the development of multimedia applications, which uses Python as a scripting language. </P>
16 |
17 | <I><P>Build</I> currently exists as an executable running under Microsoft Windows from which the user can create and edit <I>Build</I> documents using a graphical editing environment. These documents can be populated with a wide variety of user-interface objects, ranging from simple ones such as pictures and borders, through to the more complex such as scrolling text. Further user interface component types can be defined using Python.</P>
18 |
19 | <P>Python is also used to define the functionality behind these interfaces. A wide variety of predefined behaviours is present within <I>Build</I> itself and these can be extended through user defined Python scripts. <I>Build</I> can also be used in conjunction with 3<SUP>rd</SUP> party Python libraries.</P>
20 |
21 | <I><P>Build</I> can be put to a wide variety of uses. Multimedia presentations are easily assembled using the framework. It is also useful as a tool for the creation of desktop utility programs. More complex applications can be built with more extensive Python scripting.</P>
22 |
23 | <P>The aim of the demonstration is to give a concise overview of the capabilities of <I>Build</I>, and to provide an introduction to the manner in which <I>Build</I> applications are created, with the focus primarily on graphical and user-interface components. We will also demonstrate a number of projects undertaken with <I>Build</I>, including a multimedia database using Gadfly, some multimedia presentations, and a variety of in-house production tools.</P>
24 |
25 | <FONT SIZE=2><P></FONT><A HREF="http://www.bibliocraft.com/build">http://www.bibliocraft.com/build</A></P>
26 | </BODY>
27 | </HTML>
28 |
--------------------------------------------------------------------------------
/conferences/1995-12/papers/bshomer/abstract.html:
--------------------------------------------------------------------------------
1 | <TITLE>A Generic data collection system through WWW forms</TITLE>
2 | <BODY>
3 |
4 | <H1>A Generic data collection system through WWW forms, based on a
5 | Python OOD program. </H1>
6 | <HR>
7 | <A HREF = "abstract.html">[Abstract]</A>
8 | <A HREF = "introduction.html">[Introduction]</A>
9 | <A HREF = "methods.html">[Methods]</A>
10 | <A HREF = "discussion.html">[Discussion]</A>
11 | <A HREF = "references.html">[References]</A>
12 | <HR>
13 | <A href = "shomer.ps">An updated version of this paper is available in postscript .</A>
14 | <HR>
15 | <H2>Abstract</H2>
16 | One of the problems associated with modern data management is the
17 | efficient collection and validation of data from providers of information.
18 | WWW browsers, able to support forms provide an
19 | excellent, machine independent interface for collectiong data through the
20 | network. When the information to be provided is rich and complex, a robust
21 | program on the server side should provide the user with a friendly
22 | interface that breaks the complex task into smaller, more managable tasks
23 | and on the other hand act as a powerful pre-filter, scanning errors
24 | on-line.<P>
25 | Albeit some limitations which are a consequence of the server-client
26 | phylosophy, object oriented programs are especially efficient for
27 | interfacing with WWW forms.<P>
28 |
29 | Described here is a generic, object oriented data submission system,
30 | entirely based on the Python programming language. This system can be
31 | easily accomodated to serve several data submission schemes with a
32 | relatively short development and implantation time.
33 |
34 | <A HREF = "http://www.ebi.ac.uk/subs/emblsubs.html">This system already
35 | serves successfuly </A> in the EMBL outstation -
36 | <A HREF = "http://www.ebi.ac.uk/">the European Bioinformatics
37 | Iinstitute (EBI).</A> It caters one of the
38 | world's largest biology databases - <A HREF = "http://www.ebi.ac.uk/ebi_docs/embl_db/ebi/topembl.html">EMBL
39 | </A> as well as a few others.<P>
40 | <HR>
41 | <CITE>Written by <A HREF = "http://www.ebi.ac.uk/ebi_docs/staff/benny.html">Benny shomer</A>, The EBI. <P>
42 | <A HREF = "http://www.ebi.ac.uk/ebi_docs/staff/bennymail.html">bshomer@ebi.ac.uk</A>
43 | </CITE>
44 | <HR>
45 | </BODY>
46 |
--------------------------------------------------------------------------------
/conferences/1997-10/index.htp:
--------------------------------------------------------------------------------
1 | Title: Sixth International Python Conference
2 | Author: ipc6@python.org
3 |
4 | <H1>The Sixth International Python Conference</H1>
5 |
6 | <HR>
7 |
8 | <H3>October 14-17, 1997 - San Jose, California</H3>
9 |
10 | <H4>Sponsored by <A href="http://www.cnri.reston.va.us/">CNRI</A>
11 | and the <a href="/psa/">PSA</A><br>
12 | Co-sponsored by <A href="http://www.usenix.org/">USENIX</A>,
13 | the Advanced Computing Systems Association</H4>
14 |
15 | <HR>
16 |
17 | <i>The conference is over. These pages remain as a memento. The
18 | <a href="proceedings">proceedings</A> are available.</i>
19 |
20 | <HR>
21 |
22 | <H3>Conference Information:</H3>
23 |
24 | <P>
25 |
26 | <LI><A href="registration.html">Registration</A>
27 |
28 | <LI><A href="accomodations.html">Hotel Information</A>
29 |
30 | <LI><A href="program.html">Conference Program</A>
31 |
32 | <UL>
33 |
34 | <LI><A href="tutorials.html">Tutorials Program</A>
35 |
36 | <LI><A href="techprogram.html">Paper Sessions Program</A>
37 |
38 | <LI><A href="devday.html">Developers' Day Program</A>
39 |
40 | </UL>
41 |
42 | <LI><A href="shorties.html">Call for Short Talks</A>
43 |
44 | <LI><A href="cfp.html">Call for Papers</A>
45 |
46 | <UL>
47 |
48 | <LI><A href="guidelines.html">Guidelines for Authors</A>
49 |
50 | <LI><A href="instructions.html">Instructions for Accepted Papers</A>
51 |
52 | </UL>
53 |
54 | <P>
55 |
56 | <HR>
57 |
58 | <P>Come join us and meet other Python users at the sixth Python
59 | conference this fall. This conference will be bigger and better than
60 | ever. We start with a full day of tutorials, where the best Python
61 | experts in the world share their knowledge with both beginners and
62 | advanced Python users. Next we'll have two days of refereed paper
63 | presentations, where you'll hear about the most exciting applications,
64 | tools and extensions written by other Python users. And last but not
65 | least, come to the developers' day and discuss the future of Python
66 | with Python's creator, Guido van Rossum.
67 |
68 | <P>Whether you're a Python user or a developer, whether you're using
69 | Python to write CGI scripts or to control scientific calculations,
70 | whether you're using it on Unix, Windows or Macintosh, <b>don't miss
71 | the most exciting Python event ever!</b>
72 |
73 | <P>
74 |
--------------------------------------------------------------------------------
]]></plaintext></digitome@iol.ie></li></beazley@cs.uchicago.edu></p></dd></div>
![[front]](tshirt-front.gif)
14 | ![[back]](tshirt-back.gif)
15 |
16 | 
16 | Home |
17 | Software |
18 | Documentation |
19 | PSA |
20 | Workshops |
21 | SIGs |
22 | Search
23 | ![]](../../pics/ArrowRight.gif){kind=small}
24 |