Tweaks to work around wxMac bugs

[wxWidgets.git] / wxPython / docs / PyManual.txt

diff --git a/wxPython/docs/PyManual.txt b/wxPython/docs/PyManual.txt
index dc33a20fa40bc58c884eb2c5d4c814aa7ce8b018..543dd379641a569956b05411687c7ceca9d591d6 100644 (file)
--- a/wxPython/docs/PyManual.txt
+++ b/wxPython/docs/PyManual.txt
@@ -43,8 +43,7 @@ Besides being `a delicious dessert`_, Py is the name for a collection
 of whimsically-named Python programs and modules that began as the
 PyCrust project.  So Py is really several things: a set of standalone
 programs, including the original PyCrust program, a library of Python
-source code modules that can be used in your own programs, a set of
-decorator classes that enhance the wxPython class library, and as many
+source code modules that can be used in your own programs, and as many
 examples of bad "pie" puns as I can come up with.  (If you're going to
 do something, you might as well do it all the way, right?)  Py uses
 Python and wxPython, so it works equally well on Windows, Linux and
@@ -67,15 +66,15 @@ Python shells any more.
 
 Around that same time, the wxPython folks asked me if I'd be willing
 to move all my wxPython-related projects into the `wxPython CVS
-repository`_, and become part of the wxPython_/wxWindows_ developer team.
+repository`_, and become part of the wxPython_/wxWidgets_ developer team.
 I decided the time was right to restructure the PyCrust project.
 During the move, the PyCrust package was renamed to "py" (lowercase
 "p") and the collection of programs and modules as a whole became
 known as "Py" (with a capital "P").
 
-.. _wxPython CVS repository: http://cvs.wxwindows.org
+.. _wxPython CVS repository: http://cvs.wxWidgets.org
 .. _SourceForge: http://www.sf.net/projects/pycrust/
-.. _wxWindows: http://www.wxwindows.org/
+.. _wxWidgets: http://www.wxWidgets.org/
 
 The original goal of PyCrust was to be the best interactive, graphical
 Python shell (of course, I claimed it was the "flakiest" Python
@@ -97,10 +96,7 @@ program, and without having to alter one line of your source code.
 Py also contains a collection of modules that you can use in your own
 wxPython applications to provide similar services, either for your own
 use during development, or as an interface for users of your programs.
-These modules are the same ones used by all the Py programs.  In
-addition, Py contains a set of decorator classes that enhance the
-wxPython class library, by dynamically attaching docstrings and call
-signatures at runtime.
+These modules are the same ones used by all the Py programs.  
 
 
 Py standalone programs
@@ -155,9 +151,9 @@ PyShell is an interactive, Python shell.  It shares the same base code
 as PyCrust, but doesn't have any of the extra features that appear in
 the PyCrust notebook interface.
 
-.. figure:: /screenshots/PyShell.png
+.. figure:: screenshots/PyShell.png
 
-   PyShell running on Mandrake Linux 9.1.
+   PyShell running on Mandrake Linux.
 
 
 PyWrap
@@ -168,9 +164,7 @@ program with a PyCrust frame at the same time.  Inside the PyCrust
 shell namespace, the local variable ``app`` is assigned to your
 application instance.  In this way you can introspect your entire
 application within the PyCrust shell, as well as the PyFilling
-namespace viewer.  And through the use of the Py decorator classes,
-PyCrust can display wxPython function and method signatures as well as
-docstrings for the entire wxPython library.
+namespace viewer.  
 
 
 Py modules
@@ -186,14 +180,6 @@ required, PyCrust will work just as well with your interpreter as with
 its default interpreter.
 
 
-Decorator classes
-=================
-
-Py contains a set of decorator classes that enhance the wxPython class
-library, by dynamically attaching docstrings and call signatures at
-runtime.
-
-
 Projects using Py
 =================