File: readme.html

package info (click to toggle)
pype 2.9.1-4
links: PTS, VCS
area: main
in suites: wheezy
size: 1,292 kB
sloc: python: 13,861; makefile: 11
file content (1551 lines) | stat: -rw-r--r-- 80,415 bytes
parent folder | download | duplicates (2)
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.7: http://docutils.sourceforge.net/" />
<title>Readme/Help for PyPE (Python Programmer's Editor)</title>
<style type="text/css">

/*
:Author: David Goodger (goodger@python.org)
:Id: $Id: html4css1.css 6194 2009-11-11 12:05:10Z milde $
:Copyright: This stylesheet has been placed in the public domain.

Default cascading style sheet for the HTML output of Docutils.

See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
customize this style sheet.
*/

/* used to remove borders from tables and images */
.borderless, table.borderless td, table.borderless th {
  border: 0 }

table.borderless td, table.borderless th {
  /* Override padding for "table.docutils td" with "! important".
     The right padding separates the table cells. */
  padding: 0 0.5em 0 0 ! important }

.first {
  /* Override more specific margin styles with "! important". */
  margin-top: 0 ! important }

.last, .with-subtitle {
  margin-bottom: 0 ! important }

.hidden {
  display: none }

a.toc-backref {
  text-decoration: none ;
  color: black }

blockquote.epigraph {
  margin: 2em 5em ; }

dl.docutils dd {
  margin-bottom: 0.5em }

/* Uncomment (and remove this text!) to get bold-faced definition list terms
dl.docutils dt {
  font-weight: bold }
*/

div.abstract {
  margin: 2em 5em }

div.abstract p.topic-title {
  font-weight: bold ;
  text-align: center }

div.admonition, div.attention, div.caution, div.danger, div.error,
div.hint, div.important, div.note, div.tip, div.warning {
  margin: 2em ;
  border: medium outset ;
  padding: 1em }

div.admonition p.admonition-title, div.hint p.admonition-title,
div.important p.admonition-title, div.note p.admonition-title,
div.tip p.admonition-title {
  font-weight: bold ;
  font-family: sans-serif }

div.attention p.admonition-title, div.caution p.admonition-title,
div.danger p.admonition-title, div.error p.admonition-title,
div.warning p.admonition-title {
  color: red ;
  font-weight: bold ;
  font-family: sans-serif }

/* Uncomment (and remove this text!) to get reduced vertical space in
   compound paragraphs.
div.compound .compound-first, div.compound .compound-middle {
  margin-bottom: 0.5em }

div.compound .compound-last, div.compound .compound-middle {
  margin-top: 0.5em }
*/

div.dedication {
  margin: 2em 5em ;
  text-align: center ;
  font-style: italic }

div.dedication p.topic-title {
  font-weight: bold ;
  font-style: normal }

div.figure {
  margin-left: 2em ;
  margin-right: 2em }

div.footer, div.header {
  clear: both;
  font-size: smaller }

div.line-block {
  display: block ;
  margin-top: 1em ;
  margin-bottom: 1em }

div.line-block div.line-block {
  margin-top: 0 ;
  margin-bottom: 0 ;
  margin-left: 1.5em }

div.sidebar {
  margin: 0 0 0.5em 1em ;
  border: medium outset ;
  padding: 1em ;
  background-color: #ffffee ;
  width: 40% ;
  float: right ;
  clear: right }

div.sidebar p.rubric {
  font-family: sans-serif ;
  font-size: medium }

div.system-messages {
  margin: 5em }

div.system-messages h1 {
  color: red }

div.system-message {
  border: medium outset ;
  padding: 1em }

div.system-message p.system-message-title {
  color: red ;
  font-weight: bold }

div.topic {
  margin: 2em }

h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
  margin-top: 0.4em }

h1.title {
  text-align: center }

h2.subtitle {
  text-align: center }

hr.docutils {
  width: 75% }

img.align-left, .figure.align-left{
  clear: left ;
  float: left ;
  margin-right: 1em }

img.align-right, .figure.align-right {
  clear: right ;
  float: right ;
  margin-left: 1em }

img.align-center, .figure.align-center {
  display: block;
  margin-left: auto;
  margin-right: auto;
}

.align-left {
  text-align: left }

.align-center {
  clear: both ;
  text-align: center }

.align-right {
  text-align: right }

/* reset inner alignment in figures */
div.align-right {
  text-align: left }

/* div.align-center * { */
/*   text-align: left } */

ol.simple, ul.simple {
  margin-bottom: 1em }

ol.arabic {
  list-style: decimal }

ol.loweralpha {
  list-style: lower-alpha }

ol.upperalpha {
  list-style: upper-alpha }

ol.lowerroman {
  list-style: lower-roman }

ol.upperroman {
  list-style: upper-roman }

p.attribution {
  text-align: right ;
  margin-left: 50% }

p.caption {
  font-style: italic }

p.credits {
  font-style: italic ;
  font-size: smaller }

p.label {
  white-space: nowrap }

p.rubric {
  font-weight: bold ;
  font-size: larger ;
  color: maroon ;
  text-align: center }

p.sidebar-title {
  font-family: sans-serif ;
  font-weight: bold ;
  font-size: larger }

p.sidebar-subtitle {
  font-family: sans-serif ;
  font-weight: bold }

p.topic-title {
  font-weight: bold }

pre.address {
  margin-bottom: 0 ;
  margin-top: 0 ;
  font: inherit }

pre.literal-block, pre.doctest-block {
  margin-left: 2em ;
  margin-right: 2em }

span.classifier {
  font-family: sans-serif ;
  font-style: oblique }

span.classifier-delimiter {
  font-family: sans-serif ;
  font-weight: bold }

span.interpreted {
  font-family: sans-serif }

span.option {
  white-space: nowrap }

span.pre {
  white-space: pre }

span.problematic {
  color: red }

span.section-subtitle {
  /* font-size relative to parent (h1..h6 element) */
  font-size: 80% }

table.citation {
  border-left: solid 1px gray;
  margin-left: 1px }

table.docinfo {
  margin: 2em 4em }

table.docutils {
  margin-top: 0.5em ;
  margin-bottom: 0.5em }

table.footnote {
  border-left: solid 1px black;
  margin-left: 1px }

table.docutils td, table.docutils th,
table.docinfo td, table.docinfo th {
  padding-left: 0.5em ;
  padding-right: 0.5em ;
  vertical-align: top }

table.docutils th.field-name, table.docinfo th.docinfo-name {
  font-weight: bold ;
  text-align: left ;
  white-space: nowrap ;
  padding-left: 0 }

h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
  font-size: 100% }

ul.auto-toc {
  list-style-type: none }

</style>
</head>
<body>
<div class="document" id="readme-help-for-pype-python-programmer-s-editor">
<h1 class="title">Readme/Help for PyPE (Python Programmer's Editor)</h1>

<style type="text/css">
pre.literal-block {
    background-color: rgb(192, 192, 255);
    margin: 0cm 1.5cm 0cm 1.5cm;
}
</style><div class="contents topic" id="table-of-contents">
<p class="topic-title first">Table of Contents</p>
<ul class="simple">
<li><a class="reference internal" href="#license-and-contact-information" id="id2">License and Contact information</a></li>
<li><a class="reference internal" href="#requirements" id="id3">Requirements</a></li>
<li><a class="reference internal" href="#installation" id="id4">Installation</a><ul>
<li><a class="reference internal" href="#why-doesn-t-the-windows-install-work" id="id5">Why doesn't the Windows install work?</a></li>
<li><a class="reference internal" href="#why-doesn-t-pype-work-on-linux" id="id6">Why doesn't PyPE work on Linux?</a></li>
<li><a class="reference internal" href="#why-isn-t-the-most-recent-pype-available-as-deb-or-rpm" id="id7">Why isn't the most recent PyPE available as deb or RPM?</a></li>
<li><a class="reference internal" href="#why-doesn-t-pype-work-on-osx" id="id8">Why doesn't PyPE work on OSX?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#command-line-options" id="id9">Command Line Options</a><ul>
<li><a class="reference internal" href="#last" id="id10">--last</a></li>
<li><a class="reference internal" href="#unicode-and-ansi" id="id11">--unicode and --ansi</a></li>
<li><a class="reference internal" href="#fontsize" id="id12">--fontsize</a></li>
<li><a class="reference internal" href="#font" id="id13">--font</a></li>
<li><a class="reference internal" href="#nothread" id="id14">--nothread</a></li>
<li><a class="reference internal" href="#macros" id="id15">--macros</a></li>
<li><a class="reference internal" href="#standalone" id="id16">--standalone</a></li>
<li><a class="reference internal" href="#port" id="id17">--port</a></li>
<li><a class="reference internal" href="#use-old-parser" id="id18">--use_old_parser</a></li>
</ul>
</li>
<li><a class="reference internal" href="#pype-features-and-functionality" id="id19">PyPE features and functionality</a><ul>
<li><a class="reference internal" href="#what-to-expect-when-coming-from-other-editors-ides" id="id20">What to expect when coming from other editors/IDEs</a></li>
<li><a class="reference internal" href="#encoding-detection-for-opening-files" id="id21">Encoding detection for opening files</a></li>
<li><a class="reference internal" href="#encoding-detection-for-saving-files" id="id22">Encoding detection for saving files</a></li>
<li><a class="reference internal" href="#what-is-a-coding-directive" id="id23">What is a &quot;coding directive&quot;?</a></li>
<li><a class="reference internal" href="#shells" id="id24">Shells</a></li>
<li><a class="reference internal" href="#vim-options" id="id25">Vim options</a></li>
<li><a class="reference internal" href="#using-options-realtime-options-for-syntax-checking-and-tool-updates" id="id26">Using Options -&gt; Realtime Options for syntax checking and tool updates</a></li>
<li><a class="reference internal" href="#what-is-sloppy-cut-copy" id="id27">What is Sloppy Cut/Copy?</a></li>
<li><a class="reference internal" href="#what-is-smart-paste" id="id28">What is Smart Paste?</a></li>
<li><a class="reference internal" href="#what-do-the-different-options-in-the-filter-tool-do" id="id29">What do the different options in the Filter tool do?</a></li>
<li><a class="reference internal" href="#how-do-i-update-the-default-settings-for-a-particular-document-type" id="id30">How do I update the default settings for a particular document type?</a></li>
<li><a class="reference internal" href="#dictionaries-and-alphabets-for-the-spell-checker" id="id31">Dictionaries and alphabets for the Spell checker</a></li>
<li><a class="reference internal" href="#how-does-one-pype-work" id="id32">How does &quot;One PyPE&quot; work?</a></li>
<li><a class="reference internal" href="#what-the-heck-is-a-trigger" id="id33">What the heck is a Trigger?</a></li>
<li><a class="reference internal" href="#find-replace-bars" id="id34">Find/Replace bars</a></li>
<li><a class="reference internal" href="#what-happens-when-smart-case-is-enabled-during-a-replace" id="id35">What happens when &quot;Smart Case&quot; is enabled during a replace?</a></li>
<li><a class="reference internal" href="#string-escapes-in-regular-expressions-and-multiline-searches" id="id36">String escapes in regular expressions and multiline searches?</a></li>
<li><a class="reference internal" href="#how-do-i-use-the-todo-list" id="id37">How do I use the 'Todo' list?</a></li>
<li><a class="reference internal" href="#labels-transforms-insert-comment" id="id38">Labels / Transforms -&gt; Insert Comment</a></li>
<li><a class="reference internal" href="#what-are-the-known-issues-within-pype-s-parser" id="id39">What are the known issues within PyPE's parser?</a><ul>
<li><a class="reference internal" href="#the-c-c-parser" id="id40">The C/C++ parser</a></li>
<li><a class="reference internal" href="#the-python-parser" id="id41">The Python parser</a></li>
<li><a class="reference internal" href="#tex-latex" id="id42">TeX/LaTeX</a></li>
<li><a class="reference internal" href="#html-xml" id="id43">HTML/XML</a></li>
<li><a class="reference internal" href="#label-parser" id="id44">Label Parser</a></li>
<li><a class="reference internal" href="#name-line-expanded-state" id="id45">Name/Line Expanded State</a></li>
</ul>
</li>
<li><a class="reference internal" href="#how-do-you-get-usable-calltips" id="id46">How do you get usable Calltips?</a></li>
<li><a class="reference internal" href="#how-do-you-get-autocompletion" id="id47">How do you get autocompletion?</a></li>
<li><a class="reference internal" href="#crlf-lf-cr-line-endings" id="id48">CRLF/LF/CR line endings</a></li>
<li><a class="reference internal" href="#stcstyleeditor-py" id="id49">STCStyleEditor.py</a></li>
<li><a class="reference internal" href="#expandable-collapsable-foldable-code" id="id50">Expandable/collapsable/foldable code</a></li>
<li><a class="reference internal" href="#converting-between-tabs-and-spaces" id="id51">Converting between tabs and spaces</a></li>
</ul>
</li>
<li><a class="reference internal" href="#how-do-i-program-my-own-macros" id="id52">How do I program my own macros?</a><ul>
<li><a class="reference internal" href="#an-example-nontrivial-macro" id="id53">An example nontrivial macro</a></li>
<li><a class="reference internal" href="#using-macros-as-code-snippets" id="id54">Using macros as code snippets</a></li>
<li><a class="reference internal" href="#sample-macros-included-with-pype" id="id55">Sample Macros included with PyPE</a></li>
<li><a class="reference internal" href="#non-white-background-colors" id="id56">Non-white background colors</a></li>
</ul>
</li>
<li><a class="reference internal" href="#faq" id="id57">FAQ</a><ul>
<li><a class="reference internal" href="#how-do-you-come-up-with-new-feature-ideas" id="id58">How do you come up with new feature ideas?</a></li>
<li><a class="reference internal" href="#what-s-the-deal-with-the-version-numbering-scheme" id="id59">What's the deal with the version numbering scheme?</a></li>
<li><a class="reference internal" href="#how-did-pype-come-about" id="id60">How did PyPE come about?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#thank-yous" id="id61">Thank Yous</a></li>
</ul>
</div>
<div class="section" id="license-and-contact-information">
<h1><a class="toc-backref" href="#id2">License and Contact information</a></h1>
<p><a class="reference external" href="http://pype.sourceforge.net">http://pype.sourceforge.net</a>
<a class="reference external" href="http://come.to/josiah">http://come.to/josiah</a></p>
<p>PyPE is copyright 2003-2006 Josiah Carlson.
Contributions are copyright their respective authors.</p>
<p>This software is licensed under the GPL (GNU General Public License) version 2
as it appears here: <a class="reference external" href="http://www.gnu.org/copyleft/gpl.html">http://www.gnu.org/copyleft/gpl.html</a>
It is also included with this archive as <a class="reference external" href="gpl.txt">gpl.txt</a>.</p>
<p>The portions of STCStyleEditor.py included in StyleSetter.py, which is used to
support styles, was released under the wxWindows license and is copyright (c)
2001 - 2002 Riaan Booysen.</p>
<p>Any software that was originally licensed as wxWindows or LGPL v2 I have
relicensed as GPL v2 as is allowed under both the wxWindows and LGPL licenses.</p>
<p>The included stc-styles.rc.cfg was modified from the original version in order
to not cause exceptions during style changes, as well as adding other language
style definitions, and was originally distributed with wxPython version
2.4.1.2 for Python 2.2 .</p>
<p>If you do not also receive a copy of <a class="reference external" href="gpl.txt">gpl.txt</a>, with your version
of this software, please inform me of the violation at either web page at the
top of this document.</p>
</div>
<div class="section" id="requirements">
<h1><a class="toc-backref" href="#id3">Requirements</a></h1>
<p>Either a machine running Python and wxPython, or a Windows machine that can
run the binaries should be sufficient.  Initial revisions of PyPE were
developed on a PII-400 with 384 megs of ram, but it should work on any machine
that can run the most recent wxPython revisions.  Some portions may be slow
(when using Document-&gt;Wrap Long Lines especially, which is a known issue with
the scintilla text editor control), but it should still be usable.</p>
<p>PyPE 2.x has been tested on Python 2.3 and wxPython 2.6.3.0.  It should work
on later versions of Python and wxPython.  If you are having issues, file a
bug report on <a class="reference external" href="http://sourceforge.net/projects/pype">http://sourceforge.net/projects/pype</a> .</p>
</div>
<div class="section" id="installation">
<h1><a class="toc-backref" href="#id4">Installation</a></h1>
<p>If you have Python 2.3 or later as well as wxPython 2.6.3 or later, you can
extract PyPE-X.Y.Z-src.zip anywhere and run it by double-clicking on pype.py
or pype.pyw .  Note that the 2.6.3.3 ansi build of wxPython has issues with
pasting, so use some other ansi build, or even the 2.6.3.3 unicode build.</p>
<p>If you don't have Python 2.3 wxPython 2.6.3 or later, and are running Windows,
you should (hopefully) be able to run the Windows binaries.  They are provided
for your convenience (so you don't have to install Python and wxPython).</p>
<p>At the current time, the Windows binaries are constructed with Python 2.3 and
wxPython 2.6.3.0 .  I have considered moving to Python 2.5 or even 2.4 with
wxPython 2.8, but switching to Python 2.4 with wxPython 2.6.x adds 700k to the
binary distribution, and going with Python 2.5 and wxPython 2.8 (there are
currently no wxPython 2.6.3.* releases for Python 2.5) adds 2.2 megs to the
binary distribution, some of which is the Python 2.4-2.5 size difference, much
of it being the necessity to include the gdi plus dll for non-XP/Vista
platforms, and even the MSVC 7.1 runtime.  While many users have copies of
both of these runtimes <em>somewhere</em> on their system, PyPE cannot rely on them
being accessable (on my machine only the MSVC 7.1 runtime is in a system path,
while the gdi plus dll is in about a dozen places).</p>
<p>If it so happens that the Windows binaries don't work for you, and you have an
installation of Python and wxPython that fits the requirements, why don't you
run the source version?  The only difference is a pass through py2exe, and a
minor loading time speed increase.  Just because the Windows binaries exist,
doesn't mean that you /have/ to run them.  If you have a Python and wxPython
installation, you should have the necessary dlls to make PyPE run (Python is
shipped with the 7.1 runtime, and wxPython 2.7+ ships with the gdi plus dll).</p>
<div class="section" id="why-doesn-t-the-windows-install-work">
<h2><a class="toc-backref" href="#id5">Why doesn't the Windows install work?</a></h2>
<p>Depending on your platform, it may or may not work.  It works for me on
Windows 2k and XP.  Most problems people have is that they mistakenly extract
library.zip, which they shouldn't do (and in recent PyPE binary releases
may not be able to do).  It could also be due to the lack of some DLL, in
which case an error message should inform you of which DLL you are missing.</p>
</div>
<div class="section" id="why-doesn-t-pype-work-on-linux">
<h2><a class="toc-backref" href="#id6">Why doesn't PyPE work on Linux?</a></h2>
<p>PyPE 2.5+ has been tested on Ubuntu 6.06 with...</p>
<ul class="simple">
<li>python-wxversion_2.6.1.2ubuntu2_all.deb</li>
<li>libwxgtk2.6-0_2.6.1.2ubuntu2_i386.deb</li>
<li>python-wxgtk2.6_2.6.1.2ubuntu2_i386.deb</li>
</ul>
<p>And</p>
<ul class="simple">
<li>libwxgtk2.7-0_2.7.1.3-0_i386.deb</li>
<li>python-wxgtk2.7_2.7.1.3-0_i386.deb</li>
</ul>
<p>The only anomalies observed so far is seemingly a bug with some
wx.ScrolledPanel uses (which have been replaced in more recent releases), and
when using a pure Kubuntu install (installed via the Kubuntu install, and not
Ubuntu + Kubuntu core via synaptic), there may be errors and/or warnings
during PyPE startup.  I have not been able to crash PyPE yet, so I presume it
is stable.  I have recently switched to using Ubuntu + Kubuntu core + Xubuntu
core, and I haven't noticed any of aforementioned errors.</p>
<p>There have previously been reports of PyPE segfaulting in certain Linux
distributions when opening a file.  This seems to be caused by icons in the
file listing in the 'Documents' tab on the right (or left) side of the editor
(depending on your preferences), or by icons in the notebook tabs along the
top of the editor.  It was due to either the platform not being able to find
the icons to display, or the icons being improperly sized.  You can disable
these icons by starting up PyPE, going to Options-&gt;Use Icons, and making sure
that it is unchecked.  You should restart PyPE to make sure that the setting
sticks.  PyPE will be uglier, but it should work.  I believe that this has
been fixed in PyPE 2.4.1 and later, but this documentation persists &quot;just in
case&quot;.</p>
</div>
<div class="section" id="why-isn-t-the-most-recent-pype-available-as-deb-or-rpm">
<h2><a class="toc-backref" href="#id7">Why isn't the most recent PyPE available as deb or RPM?</a></h2>
<p>Short answer: it's a pain in the ass.</p>
<p>Longer answer: I'm not the maintainer for the PyPE package in any of the
Ubuntu repositories, but have recently discovered that PyPE has a newer
maintainer.  Whether or not the new maintainer keeps PyPE up-to-date is up to
him.  Personal attempts to create .debs have resulted in utter failure, which
I can either blame on a personal failure to comprehend the documentation, or a
failure in the documentation to impart the necessary information.  Either way,
you are going to have to wait for the debian/ubuntu/whatever repositories to
update, or you can get the most recent PyPE from
<a class="reference external" href="http://sourceforge.net/projects/pype">http://sourceforge.net/projects/pype</a> and extract it wherever you desire.  I'm
a fan of ~/apps/PyPE, but choose what you will.</p>
<p>I'm not going to package any RPMs for PyPE, primarily because I'm not going to
install the RPM build/install stuff into Ubuntu.  Recent attempts to get
bdist_wininst working in such a way that the results don't mangle Python
installations have failed, and this experience leads me to believe that
bdist_rpm has similar issues.  Essentially, you are on your own with regards
to rpm packages.</p>
</div>
<div class="section" id="why-doesn-t-pype-work-on-osx">
<h2><a class="toc-backref" href="#id8">Why doesn't PyPE work on OSX?</a></h2>
<p>Aside from &quot;PyPE works on OSX&quot; (or &quot;almost works&quot;) from 2 users, I don't know
what may be causing PyPE to not work in OSX.  If you send bug reports with
tracebacks, etc., we can probably figure out what is going on and how we can
fix it.</p>
<p>In the summer of 2008, I actually had an OS X laptop to use mid June 2008 to
late August 2008.  I did my best to improve PyPE, but because of how slow PyPE
is on OS X (I believe it is caused by the way the editor control is wrapped on
OS X with wxPython), I actually abandoned the platform.  PyPE inside an Ubuntu
or Windows virtual machine (Virtual Box or Parallels are both good) works
well on OS X.</p>
</div>
</div>
<div class="section" id="command-line-options">
<h1><a class="toc-backref" href="#id9">Command Line Options</a></h1>
<div class="section" id="last">
<h2><a class="toc-backref" href="#id10">--last</a></h2>
<p>When PyPE is run with the '--last' command line option, PyPE will attempt to
load all documents that were opened the last time you shut down PyPE.  This is
equivalent to starting up PyPE and using File-&gt;Open Last .</p>
</div>
<div class="section" id="unicode-and-ansi">
<h2><a class="toc-backref" href="#id11">--unicode and --ansi</a></h2>
<p>If PyPE is started up with the --unicode or --ansi command line options, it
will attempt to use the unicode or ansi versions of wxPython respectively.  On
failure, it will display to the user with a failure notice.  These options
have no effect on the Windows distributions of PyPE, or wherever
<tt class="docutils literal">hasattr(sys, 'frozen')</tt> is true.</p>
</div>
<div class="section" id="fontsize">
<h2><a class="toc-backref" href="#id12">--fontsize</a></h2>
<p>If you provide <tt class="docutils literal"><span class="pre">--fontsize=12</span></tt>, PyPE will change the font size for all open
documents to 12.  The default font size that PyPE uses is 10.  If you want
text to be bigger, use a number larger than 10.  If you want text to be
smaller, use a number smaller than 10.  The line number margin will be scaled
proportional to the font size specified.</p>
</div>
<div class="section" id="font">
<h2><a class="toc-backref" href="#id13">--font</a></h2>
<p>If you provide <tt class="docutils literal"><span class="pre">--font=Lucida-Console</span></tt>, PyPE will change the font for all
open documents to &quot;Lucida Console&quot;.  The default font that PyPE uses is
Courier New.</p>
</div>
<div class="section" id="nothread">
<h2><a class="toc-backref" href="#id14">--nothread</a></h2>
<p>This command line option will disable the threaded parser, which has caused
problems on some platforms.  This will reduce the accuracy of the tools in
the &quot;Tools&quot; menu, due to the faster and not necessarily correct parser being
used in its place.</p>
</div>
<div class="section" id="macros">
<h2><a class="toc-backref" href="#id15">--macros</a></h2>
<p>PyPE 2.6 has what I would consider to be a fully-functioning macro system.
The Python 2.5 <tt class="docutils literal"><span class="pre">--macros</span></tt> command line option is now ignored because macros
are enabled by default in 2.6+.</p>
</div>
<div class="section" id="standalone">
<h2><a class="toc-backref" href="#id16">--standalone</a></h2>
<p>Providing this command line option will use the path in which the PyPE source
or binary is for where PyPE's state is saved (document history, menu
configuration, etc.).  This will allow for 'embedded' applications.</p>
</div>
<div class="section" id="port">
<h2><a class="toc-backref" href="#id17">--port</a></h2>
<p>Providing this command line option will allow you to choose the port number
that PyPE uses when Options -&gt; One PyPE is checked.  The default port number
is 9999.</p>
</div>
<div class="section" id="use-old-parser">
<h2><a class="toc-backref" href="#id18">--use_old_parser</a></h2>
<p>This uses the old parser (PyPE 2.8.8 and a few revisions prior).  It is faster
than the modern parser, but it's not as accurrate, nor does it provide all of
the scope introspection capabilities that the new compiler.ast-based parser
does.</p>
</div>
</div>
<div class="section" id="pype-features-and-functionality">
<h1><a class="toc-backref" href="#id19">PyPE features and functionality</a></h1>
<div class="section" id="what-to-expect-when-coming-from-other-editors-ides">
<h2><a class="toc-backref" href="#id20">What to expect when coming from other editors/IDEs</a></h2>
<p>While PyPE has quite a few of the features that one would expect from an IDE,
I do not consider PyPE to be an IDE; I consider PyPE to be an editor.  The
semantic difference between the two in my mind is a bit wishy-washy, so I'll
not bore you with the details.  In any case:</p>
<ol class="arabic simple">
<li>Hitting F5 will not run your Python, nor compile the latex, nor compile the
C/C++, nor open a browser for the HTML.  It will (by default) refresh the
browsable source trees and other tools.  You can change hotkeys, and in
particular, the (new in PyPE 2.8) 'File -&gt; Run Current File' menu item.
For .py and .pyw files, 'Run Current File' will use the Python specified in
the lower part of 'Options -&gt; Shell Options' to run your Python source,
capturing the output and allowing interaction.  For .htm, .html, .shtm and
.shtml, PyPE will try to use your system defined default web browser to
open the file.  For .tex files, PyPE will attempt to run pdflatex on them.</li>
<li>If PyPE seems complicated when you are first starting out, hide all of the
optional features; 'Options -&gt; Layout Options -&gt; Show Wide Tools', 'Show
Tall Tools', and '(toolbar) Hide'.  Start editing.  If it isn't doing what
you want/expect it to, check the 'Document' menu for per-document settings
or the 'Options' menu for other editor-wide options.  Want to change
hotkeys?  Use 'Options -&gt; Change Menus and Hotkeys' .</li>
<li>PyPE is not going to gain a debugger any time soon, if ever.  I agree with
many of you that debuggers can be useful, but aside from attempting to
steal Idle's or some other project's remote debugger and making it work in
PyPE, 1) I wouldn't know where to begin, 2) it may kill bookmark
indicators, 3) I find that print statements are sufficient for me, 4) I
have not had sufficient desire to make it happen.</li>
<li>PyPE is not like every other editor you have ever used.  It may share some
features, but it is likely just a bit different.  Before you freak out and
email me with, &quot;PyPE sux, go find something else to do with your time
newb! lols&quot; spend some time looking for the feature in the menus, the
various tabs, etc.  You may find that your desired feature is available.
Again note that if the key bindings are not to your liking, you can change
them with 'Options -&gt; Change Menus and Hotkeys' for all the menus.  Macros
are handled a bit differently, which you will find out by hitting the
'hotkey' button in the Macros tab.</li>
<li>PyPE has macros.  These macros can record what you do with the keyboard and
some menu actions, then play them back.  You can also use them to
programmatically edit the document you are working on, including the
handling of 'code snippets'.  Look at the macro help below and the samples
included with PyPE (including the failure conditions).</li>
</ol>
</div>
<div class="section" id="encoding-detection-for-opening-files">
<h2><a class="toc-backref" href="#id21">Encoding detection for opening files</a></h2>
<p>If you are using the Unicode version of PyPE, when opening a file, PyPE will
attempt to decode your file using the following encodings in order:</p>
<ol class="arabic simple">
<li>The encoding specified by the BOM, if any (PyPE writes BOMs for UTF-*
encodings by default).</li>
<li>Encodings specified by &quot;coding directives&quot; in the first two lines of
source, if any.</li>
<li>Ascii (only allows for values from 0...127)</li>
<li>Latin-1/iso-8859-1 (allows for values 0...255)</li>
</ol>
<p>If options 1-3 above fail, then 4 will succeed, but may not necessarily
display the correct content, and may cause corruption if you were to save the
document.</p>
<p>In 2.6.3 and earlier, PyPE would try 1, 2, then 3, but not 4.</p>
<p>Note that PyPE does not default to assuming XML or HTML files are UTF-8 as per
spec: <a class="reference external" href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-EncodingDecl">http://www.w3.org/TR/2000/REC-xml-20001006#NT-EncodingDecl</a> due to
backwards compatability concerns with PyPE 2.6.3 and earlier. Users desiring
UTF-8 decoding support should make sure that their xml/html files include a
UTF-8 encoding directive or BOM at the beginning of their file, which is
recommended for all xml/html anyways.</p>
</div>
<div class="section" id="encoding-detection-for-saving-files">
<h2><a class="toc-backref" href="#id22">Encoding detection for saving files</a></h2>
<p>If you are using the Unicode version of PyPE, when saving a file, PyPE will
attempt to encode your file using the following encodings in order:</p>
<ol class="arabic simple">
<li>Any encoding specified by the Document -&gt; Encodings menu option (note that
a specification of 'other' will be ignored, and will assume the existence
of a &quot;coding&quot; directive.</li>
<li>Encodings specified by &quot;coding directives&quot; in the first two lines of
source, if any.</li>
<li>Ascii (only allows for values from 0...127)</li>
<li>Latin-1/iso-8859-1 (allows for values 0...255)</li>
<li>UTF-8</li>
</ol>
<p>If options 1-4 above fail, 5 will succeed.  If the first encoding option does
not succeed: say, for instance, that you have specified &quot;other&quot; as the
Document -&gt; Encodings option, then used the iso-8859-9 coding declaration for
Turkish, but included some Arabic letters in a comment somewhere (possibly an
unlikely occurrence, I don't know, but this is an example), PyPE will inform
you that your intended encoding (iso-8859-9) does not match the first encoding
to succeed (UTF-8), and ask you if it is ok to continue.</p>
<p>In 2.6.3 and earlier, PyPE would try 1, 2, 3, then 5.</p>
</div>
<div class="section" id="what-is-a-coding-directive">
<h2><a class="toc-backref" href="#id23">What is a &quot;coding directive&quot;?</a></h2>
<p>If in the first two lines of your source file (all initial blank lines being
ignored), the following regular expression matches something:</p>
<pre class="literal-block">
[cC][oO][dD][iI][nN][gG][=:](?:[&quot;'\s]*)([-\w.]+)
</pre>
<p>... then you have a properly specified &quot;coding directive&quot;.  This regular
expression was intended to match things like:</p>
<pre class="literal-block">
# -*- coding: ENCODING_NAME -*-
# -*- cOdInG: ENCODING-NAME -*-
# vim:fileencoding=ENCODING_NAME
&lt;?xml version='1.0' encoding='ENCODING-NAME' ?&gt;
</pre>
<p>... in [X]Emacs or Vim style encoding declarations for Python source, or
XML-style declarations in XML or HTML source.</p>
</div>
<div class="section" id="shells">
<h2><a class="toc-backref" href="#id24">Shells</a></h2>
<p>PyPE includes the ability to open up Python or command shells.  See the File
menu.  To choose which Python is used in the &quot;New Python Shell&quot; or &quot;Run
Selected Code&quot;, see &quot;Options -&gt; Shell Options&quot;.</p>
<p>When using &quot;New Python shell&quot; or the &quot;Run Selected Code&quot;, you may notice that
when you run wxPython code, any initial wx.Frame.Show() calls may not actually
show the frame on Windows.  To work around this, use a .Show(), followed by a
.Hide(), followed by a .Show() again.  This should work around the issue on
Windows platforms.</p>
<p>When using &quot;Run Selected Code&quot;, PyPE will try to find some open Python shell.
If one is not found, PyPE will open a new Python shell using the Python
specified in &quot;Options -&gt; Shell Options&quot;.  PyPE will then send the selected
code to the Python shell after reindenting it.</p>
<p>When using &quot;Run Current File&quot;, PyPE will try to find a currently unused output
document that was previously created.  If it cannot find one, it will open a
new output document and use that.</p>
<p>Note: as of May 2009, though shells work, there are some bugs, and seem to
have become quite slow.  There are some things I've been meaning to do to
improve their functionality, but I've not had time (in over 2 years).</p>
</div>
<div class="section" id="vim-options">
<h2><a class="toc-backref" href="#id25">Vim options</a></h2>
<p>When opening up a file that you have never opened before, or whose history you
have cleared by closing and removing it from the &quot;Recently Open&quot; list in the
Documents tab, PyPE will scan the first and last 20 lines of the file for
comments (see the Todo stuff below for what constitutes a comment), then check
for :set commands.  If :set commands are found, only cul, nocul, et, noet, sw,
sts, ts, and their aliases (including 'inv' prefix or '!' suffix for toggles,
and both '=' and ':' assignment operators for values) are used to set the
preferences in the Document menu.</p>
<p>If there exists both sw and sts options, sw will be preferred.</p>
</div>
<div class="section" id="using-options-realtime-options-for-syntax-checking-and-tool-updates">
<h2><a class="toc-backref" href="#id26">Using Options -&gt; Realtime Options for syntax checking and tool updates</a></h2>
<p>Syntax checking is always enabled for Python shells, and will highlight the
first line with an error as you type (it is actually checks shortly after you
stop typing), using the same indicator as defined in Options -&gt; Shell Options.</p>
<p>Syntax checking for Python source files is only enabled if you have chosen a
delay in the Options -&gt; Realtime Options submenu.  If your file is fewer than
200,000 bytes long, it will take max(SYNTAX_CHECK_TIME, 1)*CHOICE_IN_SECONDS,
and wait that long after you have stopped using your keyboard, etc., to check
the syntax, indicating the first error, if any, using the same indicator as
defined in Options -&gt; Shell Options.</p>
<p>Automatic source tree rebuilding for the Name and Line tools, entries for the
Filter tool, Todo listing, autocomple entries, and calltips is only enabled if
you have chosen a delay for update tools in the Options -&gt; Realtime Options
submenu.  Otherwise you need to use Document -&gt; Refresh (or the equivalent key
binding).  Similar to syntax checking above, it will take max(REFRESH_TIME, 1)
*CHOICE_IN_SECONDS, and wait that long after you have stopped using your
keyboard, etc., to do the automatic Document -&gt; Refresh call.</p>
<p>Note that PyPE will only check syntax or rebuild the tree if the content has
changed since the last time either operation was scheduled.</p>
</div>
<div class="section" id="what-is-sloppy-cut-copy">
<h2><a class="toc-backref" href="#id27">What is Sloppy Cut/Copy?</a></h2>
<p>When selecting multiple lines for a cut/copy operation, Sloppy Cut/Copy will
select the entirety of partially selected lines.  This saves the user from
having to meticulously select the start and end points of multi-line
selections.</p>
</div>
<div class="section" id="what-is-smart-paste">
<h2><a class="toc-backref" href="#id28">What is Smart Paste?</a></h2>
<p>Smart Paste is two functionalities in one.</p>
<ol class="arabic simple">
<li>When pasting multiple lines into a currently indented region, it will
reindent the pasted region such that the least indented line of the pasted
region matches the current indentation level, all other indent levels being
relative to the current/minimum.</li>
<li>When the cursor is in a non-indent portion of a line, and you paste, Smart
Paste will automatically paste to the next line, indenting one level deeper
as necessary if you had selected the start of a new block (like if, for,
while, def, etc., for Python, open curly braces '{' in C, etc.).</li>
</ol>
</div>
<div class="section" id="what-do-the-different-options-in-the-filter-tool-do">
<h2><a class="toc-backref" href="#id29">What do the different options in the Filter tool do?</a></h2>
<dl class="docutils">
<dt>subsequence</dt>
<dd>will match things like <tt class="docutils literal">us.et</tt> to <tt class="docutils literal">UserString.ExpandTabs</tt></dd>
<dt>score</dt>
<dd>when subsequence is defined, will score the matches and show the best
matches at the top of the list</dd>
<dt>no context</dt>
<dd>will not provide any context in the display or search</dd>
<dt>long</dt>
<dd>will provide a 'verbose' display and search context, like
<tt class="docutils literal">class foo: def bar(self)</tt></dd>
<dt>short</dt>
<dd>will provide a concise display and search context, like
<tt class="docutils literal">def foo.bar(self)</tt></dd>
<dt>exact</dt>
<dd>will find entries that include <em>exactly</em> what you typed in.</dd>
<dt>any</dt>
<dd>will find entries that include <em>any</em> of the 'words' you provide.</dd>
<dt>all</dt>
<dd>will find the entries that include <em>all</em> of the 'words' you provide</dd>
</dl>
<p>Given the following three definitions and the <tt class="docutils literal">no context</tt> option without
subsequence searching:</p>
<pre class="literal-block">
def abc(ghi, jkl)
def jkl(mno, pqr)
def stu(vwx, yz)
</pre>
<p>...the following searches are true:</p>
<pre class="literal-block">
exact 'def abc' -&gt; #1
any 'def abc' -&gt; #1, #2, #3
all 'def abc' -&gt; #1

exact 'abc ghi' -&gt; Nothing
any 'abc ghi' -&gt; #1
all 'abc ghi' -&gt; #1

exact 'jkl stu' -&gt; Nothing
any 'jkl stu' -&gt; #1, #2, #3
all 'jkl stu' -&gt; Nothing
</pre>
<p>With the new parser introduced in PyPE 2.9, line count information should be
fairly precise.</p>
</div>
<div class="section" id="how-do-i-update-the-default-settings-for-a-particular-document-type">
<h2><a class="toc-backref" href="#id30">How do I update the default settings for a particular document type?</a></h2>
<ol class="arabic simple">
<li>Close all open documents of the particular type whose default settings you
want to update.</li>
<li>Create or open a document of the specific document type that you want to
change the settings of.</li>
<li>Adjust all of the settings in the &quot;Document&quot; menu to those settings that
you want to be the default when you open up that particular kind of
document.</li>
<li>Use &quot;Options -&gt; Save Settings&quot; and choose the particular language whose
settings you would like to save.</li>
<li>If in the future, a particular document of that type does not have the
proper settings, use &quot;Options -&gt; Load Settings&quot; to load the defaults for
that specific language.</li>
</ol>
<p>In PyPE 2.6.3 and later, whenever a document shares the default settings for
its file type and is closed, those settings aren't explicitly saved, under the
assumption that you would prefer to have it use the default settings directly.
If you are going to change the default settings for all documents of a
specific type, follow the above 5 steps.</p>
</div>
<div class="section" id="dictionaries-and-alphabets-for-the-spell-checker">
<h2><a class="toc-backref" href="#id31">Dictionaries and alphabets for the Spell checker</a></h2>
<p>You can create/delete custom dictionaries via the +/- buttons right next to
the &quot;Custom Dictionaries:&quot; section.  You can add words to these custom
dictionaries by &quot;Check&quot;ing your document for misspellings, checking all of the
words you want to add, clicking &quot;+ ./&quot;, then choosing the custom dictionary
you want the words added to.</p>
<p>If you want to use a large primary dictionary, create a 'dictionary.txt' file
that is utf-8 encoded, and place it into the same path that PyPE is.  This
will be far faster for startup, shutdown, and creating the list than manually
adding all of the words to custom dictionaries.  Fairly reasonable word lists
for english (British, Canadian, or American) are available at Kevin's Word
list page: <a class="reference external" href="http://wordlist.sourceforge.net/">http://wordlist.sourceforge.net/</a> Words should be separated by any
standard whitespace character (spaces, tabs, line endings, etc.).</p>
<p>If you want to customize the alphabet that PyPE uses for suggesting spelling,
you can create an 'alphabet.txt' file that is utf-8 encoded, where alphabet
characters separated by commas ',', and place it into the same path that PyPE
is.</p>
<p>Please note that the spell checker is very simple.  After discovering &quot;words&quot;,
which are contiguous sequences of letters, suggestions are created by removing
single letters, inserting single letters, and swapping pairs of letters
internally.  It then checks these suggestions against the user-supplied
dictionaries, and any that match become suggestions.</p>
</div>
<div class="section" id="how-does-one-pype-work">
<h2><a class="toc-backref" href="#id32">How does &quot;One PyPE&quot; work?</a></h2>
<p>If &quot;One PyPE&quot; is selected, it will remove the file named 'nosocket' from the
path in which PyPE is running from (if it exists), and start a listening
socket on 127.0.0.1:9999 .  If &quot;One PyPE&quot; is deselected, it will create a file
called 'nosocket' in the path from which PyPE is running, and close the
listening socket (if one was listening).</p>
<p>Any new PyPE instances which attempt to open will check for the existence of
the nosocket file.  If it does not find that file, it will attempt to create a
new listening socket on 127.0.0.1:9999 .  If the socket creation fails, it
will attempt to connect to 127.0.0.1:9999 and send the documents provided on
the command-line to the other PyPE instance.  If it found the file, or if it
was able to create the socket, then a new instance of PyPE will be created,
and will use the preferences-defined &quot;One PyPE&quot; (preventing certain issues
involving a read-only path which PyPE is on, or a read-only nosocket file).</p>
<p>If you want to prevent new instances of PyPE from ever creating or using
sockets, create a file called 'nosocket' and make it read-only to PyPE.</p>
</div>
<div class="section" id="what-the-heck-is-a-trigger">
<h2><a class="toc-backref" href="#id33">What the heck is a Trigger?</a></h2>
<p>Let us say that you writing a web page from scratch.  Let us also say that
typing in everything has gotten a bit tiresome, so you want to offer yourself
a few macro-like expansions, like 'img' -&gt; '&lt;img src=&quot;&quot;&gt;'.</p>
<ol class="arabic simple">
<li>Go to: Document-&gt;Set Triggers.</li>
<li>Click on 'New Trigger'.</li>
<li>In the 'input' column of the new trigger, type in <tt class="docutils literal">img</tt></li>
<li>In the 'output' column, type in <tt class="docutils literal">&lt;img <span class="pre">src=&quot;%C&quot;&gt;</span></tt></li>
</ol>
<p>In the future, if you type in <tt class="docutils literal">img</tt> and use Transforms-&gt;Perform Trigger, it
will expand itself to <tt class="docutils literal">&lt;img <span class="pre">src=&quot;&quot;&gt;</span></tt> with your cursor between the two double
quotes.</p>
<p>What other nifty things are possible?  How about automatic curly and square
brace matching with [, [%C] and {, {%C}?  Note that triggers with a single
character in the 'enter' column are automatically done as you type, but
triggers with multiple characters in the 'input' column require using
Transforms-&gt;Perform Trigger (or its equivalent hotkey if you have assigned
one via Options -&gt; Change Menus and Hotkeys).</p>
<p>As described, there is a <tt class="docutils literal">%C</tt> directive that defines where the cursor will
end up.  There is also a <tt class="docutils literal">%L</tt> directive that inserts a line break with
autoindentation.  The semantics for string escapes are the same as in the
Find/Replace bar, and a non-indenting line break can be inserted with the
standard <tt class="docutils literal">\n</tt>.</p>
</div>
<div class="section" id="find-replace-bars">
<h2><a class="toc-backref" href="#id34">Find/Replace bars</a></h2>
<p>If you have ' or &quot; as the first character in a find or find/replace entry, and
what you entered is a proper string declaration in Python, PyPE will use the
compiler module to parse and discover the the string.  For example, to
discover LF characters, use <tt class="docutils literal">&quot;\n&quot;</tt>, including quotes.</p>
</div>
<div class="section" id="what-happens-when-smart-case-is-enabled-during-a-replace">
<h2><a class="toc-backref" href="#id35">What happens when &quot;Smart Case&quot; is enabled during a replace?</a></h2>
<p>If the found string is all upper or lower case, it will be replaced by a
string that is also all upper or lower case.</p>
<p>Else if the length of the found string is the same length as the replacement
string, you can replace one string for another, preserving capitalization.</p>
<p>For example...</p>
<pre class="literal-block">
def handleFoo(foo, arg2):
    tfOO = fcn(foo)
    tFOO2 = fcn2(tfOO)
    return fcn3(tfOO, tFOO2, foo)
</pre>
<p>...becomes...</p>
<pre class="literal-block">
def handleGoo(goo, arg2):
    tgOO = fcn(goo)
    tGOO2 = fcn2(tgOO)
    return fcn3(tgOO, tGOO2, goo)
</pre>
<p>...by enabling &quot;Smart Case&quot;, and putting 'foo' and 'goo' in the find/replace
boxes.</p>
<p>Otherwise if the first letter of the found string is upper or lowercase, then
its replacement will have the first letter be upper or lowercase respectively.</p>
</div>
<div class="section" id="string-escapes-in-regular-expressions-and-multiline-searches">
<h2><a class="toc-backref" href="#id36">String escapes in regular expressions and multiline searches?</a></h2>
<p>When using the 'Search' tab, you can use standard Python strings with escapes
and quote marks just like when you use the find/replace bars with one minor
difference; all searched data is normalized to have <tt class="docutils literal">\n</tt> line endings
regardless of the input.  This means that if you want to find a colon followed
by a line ending followed by a space, you would use <tt class="docutils literal"><span class="pre">&quot;:\n</span> &quot;</tt>, including
quotes.</p>
<p>If you include line endings in your search string, then multiline searching
will be automatically enabled during the search (but the box will remain
checked or unchecked).</p>
</div>
<div class="section" id="how-do-i-use-the-todo-list">
<h2><a class="toc-backref" href="#id37">How do I use the 'Todo' list?</a></h2>
<p>On a line by itself (any amount of leading spaces), place something that
matches the following regular expression: <tt class="docutils literal"><span class="pre">([a-zA-Z0-9</span> <span class="pre">]+):(.*)</span></tt> and is
immediately proceeded with a language-specific single-line comment (<tt class="docutils literal">#</tt>,
<tt class="docutils literal">//</tt>, <tt class="docutils literal">%</tt>, or <tt class="docutils literal"><span class="pre">&lt;!--</span></tt>).</p>
<p>The first group (after a .strip().lower() translation) will become category in
the 'Category' column, the second group (after a .strip()) becomes the todo in
the 'Todo' column, and the number of exclamation points will become the number
in the '!' column.</p>
<p>PyPE should also toss all entries with a 'Category' that is also a keyword
(keyword.kwlist), or one of the following: http, ftp, mailto, news, gopher,
and telnet.</p>
<p>The following lines are all valid todos</p>
<pre class="literal-block">
# todo: fix the code below
        #todo:fix the code below!
    #        TODo: fix the code below
#bug:I am a big ugly bug...no, I really am, but I'm also a todo
# this thing can even have spaces: but it cannot have punctuation!

#I am not a valid todo...: because there is punctuation on the left
</pre>
<p>In PyPE 2.6.5 and later, for Python, C/C++, and TeX files, PyPE supports the
use of <tt class="docutils literal">#&gt;</tt> (or equivalents for non-XML/HTML languages) as a &quot;strict&quot; todo,
with the option to only recognize these &quot;strict&quot; todos.</p>
</div>
<div class="section" id="labels-transforms-insert-comment">
<h2><a class="toc-backref" href="#id38">Labels / Transforms -&gt; Insert Comment</a></h2>
<p>When you use Transforms -&gt; Insert Comment, you create a comment of the form
(for example in Python):</p>
<pre class="literal-block">
#--------------------- comment ---------------------
</pre>
<p>With your comment centered, and the comment filling up the number of columns
defined via Document -&gt; Set Long Line Column.  Such comments will show up as
'labels' within the Name, Line, and Filter tools as:</p>
<pre class="literal-block">
-- comment --
</pre>
<p>This works similarly to SPE's display of such labels, but PyPE trims
extraneous dashes and spaces from either end, inserting a single space and a
double dash around the comment (for consistency and readability).</p>
</div>
<div class="section" id="what-are-the-known-issues-within-pype-s-parser">
<h2><a class="toc-backref" href="#id39">What are the known issues within PyPE's parser?</a></h2>
<div class="section" id="the-c-c-parser">
<h3><a class="toc-backref" href="#id40">The C/C++ parser</a></h3>
<p>PyPE 2.6.1 and later added a C/C++ parser that uses a combination of regular
expressions and some post-processing to extract function definition
information.  Note that it can handle things like the following and their
variations:</p>
<pre class="literal-block">
int ** foo(char* arg1, int larg1) \{ ...

str1 myClass :: operator[] (indices, count)
int* indices;
int count;
\{ ...
</pre>
<p>Generally speaking, it searches for all matches of the following regular
expressions for function-like examples of <tt class="docutils literal">#define</tt> and functions
respectively:</p>
<pre class="literal-block">
(#ys+i\(i(?:,s*i)*\))
(?:(cs*\([^\)]*\))[^{;\)]*[;{])
</pre>
<p>Where the following replacements are made to the regular expressions prior to
matching:</p>
<pre class="literal-block">
c -&gt; (?:i|operator[^\w]+)
i -&gt; (?:[a-zA-Z_]\w*)
s -&gt; [ \t]
y -&gt; (?:[dD][eE][fF][iI][nN][eE])
</pre>
<p>The function-like macros are returned unchanged, while the possible function
matches have various other tests performed on them and everything on the same
line as the potential function definition.</p>
<p>Note that the parser doesn't recognize struct definitions, data members of
classes, class hierarchies, functions with default values, etc., but it should
generally be sufficient for most navigation and/or file-specific autocomplete
and calltips.</p>
</div>
<div class="section" id="the-python-parser">
<h3><a class="toc-backref" href="#id41">The Python parser</a></h3>
<p>For Python source files, if given a syntactically correct Python source file,
the Python parser should work without issue (as long as --nothread is not
provided), though it may not be quite as fast as desired (where fast is &lt; .1
seconds).  Recent versions of PyPE have a much faster &quot;slow&quot; parser than
previous versions, but it is still limited to syntactically correct source
files.</p>
<p>If not given a syntactically correct Python source file (or if --nothread was
provided as a command line option), the parser splits the file into lines,
performing a check to see if there is a function, class, or comment on that
line, then saves the hierarchy information based on the level of indentation
and what came before it.  This can be inaccurate, as it will mistakenly
believe that the below function 'enumerate' is a method of MyException.</p>
<pre class="literal-block">
class MyException(Exception):
    pass
try:
    enumerate
except:
    def enumerate(inp):
        return zip(range(len(inp)), inp)
</pre>
<p>It also doesn't know anything about multi-line strings, so the definition nada
in the following lines would be seen as a function, and not part of a string.</p>
<pre class="literal-block">
'''
this used to be a function
def nada(inp):
    return None
'''
</pre>
<p>This parser will not pull out doc strings or handle multi-line function
definitions properly (which can be difficult if not impossible when provided
with a bad source file).</p>
</div>
<div class="section" id="tex-latex">
<h3><a class="toc-backref" href="#id42">TeX/LaTeX</a></h3>
<p>In TeX/LaTeX, PyPE extracts \(sub)*section and \label headings, todo items,
and labels (defined below).</p>
</div>
<div class="section" id="html-xml">
<h3><a class="toc-backref" href="#id43">HTML/XML</a></h3>
<p>PyPE only extracts todo items and labels (defined below).</p>
</div>
<div class="section" id="label-parser">
<h3><a class="toc-backref" href="#id44">Label Parser</a></h3>
<p>Knowing where to insert a label (in the trees) is tricky work, and we can only
generally choose the right place to insert labels in one of the following two
cases:</p>
<pre class="literal-block">
def foo():
    #-- label 1 --
    ...

#--label 2--
</pre>
<p>Relying on indentation for these is not generally reliable, so we place it in
the context of the scope of the following function/class/whatever definition.
The following source:</p>
<pre class="literal-block">
class foo:
    def bar(self):
        #-- label 1 --
        def goo():
            #-- label 2 --
            ...
    #-- label 3 --
    def baz(self):
        #-- label 4 --
        ...
    #-- label 5 --
</pre>
<p>Will have a general tree layout of:</p>
<pre class="literal-block">
class foo:
    def bar():
        -- label 1 --
        def goo():
    -- label 2 --
    -- label 3 --
    def baz():
-- label 4 --
-- label 5 --
</pre>
<p>Using a 'previous definition' semantic, we get a layout of:</p>
<pre class="literal-block">
class foo:
    def bar():
        -- label 1 --
        def goo():
            -- label 2 --
            -- label 3 --
    def baz():
        -- label 4 --
        -- label 5 --
</pre>
<p>Which is different, but not substantially better, and may hide labels. It is
better to show too many labels in a particular context than too few.</p>
</div>
<div class="section" id="name-line-expanded-state">
<h3><a class="toc-backref" href="#id45">Name/Line Expanded State</a></h3>
<p>PyPE will only be able to remember those items that were expanded, selected or
first visible (to keep the scrollbar consistant) if the names hadn't been
changed.  Say that you had an item named <tt class="docutils literal">class foo:</tt> that was expanded
prior to using Document -&gt; Refresh.  If you renamed it to <tt class="docutils literal">class foo_bar:</tt>,
then PyPE wouldn't remember that it was expanded in the browsable source tree.</p>
<p>Also, if you have two classes with the same name like the following:</p>
<pre class="literal-block">
if CONDITION:
    class foo:
        def bar(self):
            ...
else:
    class foo:
        def bar(self):
            ...
</pre>
<p>And one was expanded in the Name (or Line) tool, then both will be expanded in
the Name (or Line) tool.</p>
</div>
</div>
<div class="section" id="how-do-you-get-usable-calltips">
<h2><a class="toc-backref" href="#id46">How do you get usable Calltips?</a></h2>
<p>Hit F5.  This will also rebuild the browsable source tree, autocomplete
listing, filter, and todo list.</p>
</div>
<div class="section" id="how-do-you-get-autocompletion">
<h2><a class="toc-backref" href="#id47">How do you get autocompletion?</a></h2>
<p>Easy.  In the 'Document' menu, there is an entry for 'Show autocomplete'.
Make sure there is a check by it, and you are set.  If you want to get a new
or updated listing of functions, hit the F5 key on your keyboard.</p>
</div>
<div class="section" id="crlf-lf-cr-line-endings">
<h2><a class="toc-backref" href="#id48">CRLF/LF/CR line endings</a></h2>
<p>PyPE will attempt to figure out what kind of file was opened, it does this by
counting the number of different kinds of line endings.  Which ever line
ending appears the most in an open file will set the line ending support for
viewing and editing in the window.  Also, any new lines will have that line
ending.  New files will have the same line endings as the host operating
system.</p>
<p>Additionally, copying from an open document will not change the line-endings.
Future versions of PyPE may support the automatic translation of text during
copying and pasting to/from the host operating system's native line endings.</p>
<p>Converting between line endings is a menu item that is available in the
'Document' menu.</p>
</div>
<div class="section" id="stcstyleeditor-py">
<h2><a class="toc-backref" href="#id49">STCStyleEditor.py</a></h2>
<p>As I didn't write this, I can offer basically no support for it.  It seems to
work to edit python colorings, and if you edit some of the last 30 or so lines
of it, you can actually use the editor to edit some of the other styles that
are included.</p>
<p>If it doesn't work for you, I suggest you revert to the copy of the editor and
stc-styles.rc.cfg that is included with the distribution of PyPE you received.
As it is a known-good version, use it.</p>
</div>
<div class="section" id="expandable-collapsable-foldable-code">
<h2><a class="toc-backref" href="#id50">Expandable/collapsable/foldable code</a></h2>
<p>Since the beginning, there have been expandable and collapsable scopes thanks
to wxStyledTextCtrl.  How to use them...
Given the below...</p>
<pre class="literal-block">
- class nada:
-     def funct(self):
-         if 1:
|             #do something
|             pass
</pre>
<p>Shift-clicking the '-' next to the class does this...</p>
<pre class="literal-block">
- class nada:
+     def funct(self):
</pre>
<p>Or really, it's like ctrl-clicking on each of the functions declared in the
scope of the definition.  Shift-clicking on the '-' a second time does
nothing. Shift-clicking on a '+' expands that item completely.</p>
<p>Control-clicking on a '+' or '-' collapses or expands the entirety of the
scopes contained within.</p>
<p>I don't know about you, but I'm a BIG fan of shift-clicking classes.  Yeah.
Play around with them, you may like it.</p>
</div>
<div class="section" id="converting-between-tabs-and-spaces">
<h2><a class="toc-backref" href="#id51">Converting between tabs and spaces</a></h2>
<p>So, you got tabs and you want spaces, or you have spaces and want to make them
tabs.  As it is not a menu option, you're probably wondering &quot;how in the hell
am I going to do this&quot;.  Well, if you read the above stuff about string
escapes in the find/replace bar, it would be trivial.
Both should INCLUDE the quotation marks.
To convert from tabs to 8 spaces per tab; replace <tt class="docutils literal">&quot;\t&quot;</tt> with <tt class="docutils literal">&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;</tt>
To convert from 8 spaces to one tab; replace <tt class="docutils literal">&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;</tt> with <tt class="docutils literal">&quot;\t&quot;</tt></p>
<p>Note that you don't need to use the double quotes for the spaces, but it
allowed me to be explicit in this documentation.</p>
<p>Alternatively, this is available via the &quot;Transforms&quot; menu.</p>
</div>
</div>
<div class="section" id="how-do-i-program-my-own-macros">
<h1><a class="toc-backref" href="#id52">How do I program my own macros?</a></h1>
<p>Users of PyPE 2.5.1 (a test release) and later will have the ability to
record, edit, playback, and delete macros.  Most keyboard related tasks are
recorded (typing, keyboard movement, selection, cut, copy, paste, etc.), as
are all items in the Transforms menu; including automatic and manual triggers.</p>
<p>Any macro without any action performed will not be recorded.  That is, if you
hit &quot;Start Recording&quot; and do nothing other than hit &quot;Stop Recording&quot;, a macro
will not be created.  If you would like to create an initially empty macro,
you can use &quot;Empty Macro&quot; and it will get everything all set up for you.</p>
<p>Before you execute your macro, I encourage you to save all currently open
documents.  While I haven't experienced any recent crashes or segfaults while
using macros, I may not be able to replicate your particular crash condition
even if given the macro source, so may not be able to fix your problem.  Be
careful!</p>
<p>Let us assume that you have created an initially empty macro with the &quot;Empty
Macro&quot; button, whose contents are something like the following:</p>
<pre class="literal-block">
creation_date = 'Wed Jul 12 21:35:34 2006'
name = 'macro: Wed Jul 12 21:35:34 2006'
hotkeydisplay = &quot;&quot;
hotkeyaccept = &quot;&quot;

def macro(self):
    pass
</pre>
<dl class="docutils">
<dt><tt class="docutils literal">creation_date</tt></dt>
<dd>is merely for reference purposes</dd>
<dt><tt class="docutils literal">name</tt></dt>
<dd>is the name you will see in the macro list.  If this value is
missing, you will see the file name instead.</dd>
<dt><tt class="docutils literal">hotkeydisplay</tt></dt>
<dd>if you have created a hotkey for this macro, this represents how the
hotkey would be displayed to PyPE.  To get usable values for
<tt class="docutils literal">hotkeydisplay</tt>, use the 'Create Hotkey' button.</dd>
<dt><tt class="docutils literal">hotkeyaccept</tt></dt>
<dd>if you have created a hotkey for this macro, this represents the
actual underlying keyboard keypresses necessary to make the macro run.  To
get usable values for <tt class="docutils literal">hotkeyaccept</tt>, use the 'Create Hotkey' button.</dd>
<dt><tt class="docutils literal">def macro(self):</tt></dt>
<dd>is the initial definition of the macro.  You can have any number of helper
functions, extra data, etc., but the macro itself must be named <tt class="docutils literal">macro</tt>,
and must take at least one argument, the first of which being the
<tt class="docutils literal">wxStyledTextCtrl</tt> instance that contains the current document.  You can
also import any module that is available (which may be limited on systems
using the Windows binary).</dd>
</dl>
<p>The <tt class="docutils literal">self</tt> parameter will actually be my own custom subclass of the
<tt class="docutils literal">StyledTextCtrl</tt>.  You will never receive a shell or interpreter, and you
will not be able to execute macros on shells or interpreters.</p>
<p>Generally speaking, the <tt class="docutils literal">wxStyledTextCtrl</tt> subclass has everything that the
normal control subclass has, with a few caveats.</p>
<ol class="arabic">
<li><p class="first"><tt class="docutils literal">self.GetText()</tt> and <tt class="docutils literal">self.SetText()</tt> will return and set the content
of the document, paying attention to encodings as necessary.  That is, if
you perform <tt class="docutils literal">y = self.GetText()</tt> inside a macro on a document including
unicode characters, or a document defining one of the standard Python
document encoding methods, you will receive the encoded version of your
document.  Strictly ASCII documents or those without any encodings will
produce the document as-is.</p>
<p>If you would like to acquire the contents of the file as-is, unicode on
unicode platforms, etc.:</p>
<pre class="literal-block">
import wx.stc

def macro(self):
    content = wx.stc.StyledTextCtrl.GetText(self)
</pre>
</li>
<li><p class="first"><tt class="docutils literal">self.lines</tt> is a special property that gives you a line-based view of
the current document.:</p>
<pre class="literal-block">
line = self.lines[i]        # will return line &quot;i&quot; including whitespace
lines = self.lines[i:j]     # will return lines i...j-1, using standard Python slice semantics
bad = self.lines[i:j:-1]    # will raise an exception (only steps == 1 are acceptable)

self.lines[0] = 'hello world\n' # will set the first line to be &quot;hello world&quot;
self.lines[0] = 'hello world '  # will set the first line to be &quot;hello world &quot;,
                                # and the next line will become the tail end of the first line

del self.lines[i] # same as self.lines[i] = ''

#other special properties of self.lines:
self.lines.curline          # manipulation of the line the cursor is on
self.lines.curlinei         # manipulation of the index where the cursor is
self.lines.curlinep         # manipulation of the column in the line where the cursor is
self.lines.selectedlines    # manipulation of the lines where the selection exists
self.lines.selectedlinesi   # manipulation of the indices where the selection exists
self.lines.targetlines      # manipulation of the lines where the target exists
self.lines.targetlinesi     # manipulation of the indices where the target exists
                            # the target is like an invisible selection


#to force the selection of all of all lines where a selection currently exists:
self.lines.selectedlinesi = self.lines.selectedlinesi

#to iterate over the indices of all selected lines:
for i in xrange(*self.lines.selectedlinesi):
    ...

#etcetera.
</pre>
</li>
<li><p class="first"><tt class="docutils literal">self.InterpretTrigger(text)</tt> will interpret the text you provide as it
would interpret a trigger, with a small change.  That is,:</p>
<pre class="literal-block">
self.InterpretTrigger('def foo(%C):\npass')
</pre>
<p>will produce the following, with the cursor where the <tt class="docutils literal">&#64;</tt> is, without
the <tt class="docutils literal">&#64;</tt> sign.:</p>
<pre class="literal-block">
def foo(&#64;):
    pass
</pre>
<p>If you want your <tt class="docutils literal">'\n'</tt> line endings to not include auto-indenting (as
is the default for normal triggers), use <tt class="docutils literal">self.InterpretTrigger(text, 1)</tt>.</p>
</li>
<li><p class="first"><tt class="docutils literal">self._autoindent(0)</tt> will perform the equivalent of
<tt class="docutils literal"><span class="pre">self.InterpretTrigger('\n')</span></tt>.</p>
</li>
</ol>
<div class="section" id="an-example-nontrivial-macro">
<h2><a class="toc-backref" href="#id53">An example nontrivial macro</a></h2>
<p>When I was writing macro support, I would have found macros to be quite
convenient for developing macros.  What do I mean?  Let us say that I wanted
to turn a line that read (from main_window_callback.c in the gPHPedit sources):</p>
<pre class="literal-block">
case (2316) : gtk_scintilla_document_start(GTK_SCINTILLA(main_window.current_editor-&gt;scintilla)); break;
</pre>
<p>Into a line that read:</p>
<pre class="literal-block">
2316: 'DocumentStart',
</pre>
<p>As I ended up doing by hand.  Well, I could write the following macro, select
those lines I wanted to update, and execute the macro.:</p>
<pre class="literal-block">
def macro(self):
    lines = self.lines
    newlines = []
    for i in xrange(*lines.selectedlinesi):
        line = lines[i]
        pieces = line.split()
        num = pieces[1].strip('()')
        name = pieces[3]
        name = name.split('(', 1)[0].title()
        name = ''.join(name.split('_')[2:])
        newlines.append(&quot;    %s: '%s',&quot;%(num, name))
    lines.selectedlines = newlines
</pre>
<p>Presumably one would want to include error handling in your nontrivial macros,
but that shouldn't be terribly difficult.</p>
</div>
<div class="section" id="using-macros-as-code-snippets">
<h2><a class="toc-backref" href="#id54">Using macros as code snippets</a></h2>
<ol class="arabic simple">
<li>Create a macro.</li>
<li>Paste the content of your snippet into a global variable in the macro and
call it something like <tt class="docutils literal">snippet</tt>.</li>
<li>Use <tt class="docutils literal">self.InterpretTrigger(snippet)</tt>.</li>
</ol>
<p>That is, let us say that you wanted a snippet that inserted the following
content:</p>
<pre class="literal-block">
def foo(bar):
    pass
</pre>
<p>You would create the following macro:</p>
<pre class="literal-block">
name = 'Code Snippet foo()'

snippet = '''
def foo(bar):
    pass
'''

def macro(self):
    self.InterpretTrigger(snippet, 1)
</pre>
</div>
<div class="section" id="sample-macros-included-with-pype">
<h2><a class="toc-backref" href="#id55">Sample Macros included with PyPE</a></h2>
<p>PyPE includes a handful of sample macros to give you some idea of what works
and what doesn't.  The most important ones you should look at are the various
Timeout macros.  They will show you what things will and won't stop after the
5 second timeout.  The timeout conditions are there to try to prevent you from
trying to kill PyPE because it stopped responding.  The general rule of thumb:
don't perform any system calls that could take a long time to finish.</p>
</div>
<div class="section" id="non-white-background-colors">
<h2><a class="toc-backref" href="#id56">Non-white background colors</a></h2>
<p>In PyPE 2.8.6, the stylesetter now has support for non-white background
colors.  To set a non-white background color, change the 'backcol' value in
the proper common.defs.* in your 'stc-styles.rc.cfg'.</p>
</div>
</div>
<div class="section" id="faq">
<h1><a class="toc-backref" href="#id57">FAQ</a></h1>
<div class="section" id="how-do-you-come-up-with-new-feature-ideas">
<h2><a class="toc-backref" href="#id58">How do you come up with new feature ideas?</a></h2>
<p>Every once and a while, I'll be editing with PyPE, and I'll say, &quot;hey, it
would be neat if I could do X with PyPE&quot;.  This is rare, though it has
produced things like the dragable document list, spell check, customizable
menu hotkey bindings, open module, &quot;One PyPE&quot;, etc.</p>
<p>More often than not, I will be surfing the net, and someone will rant and rave
about their super ultra mega favorite editor X, and how it has so many
features that are so great that no other editor has.  Out of curiosity, I'll
usually go to the specific site, look at the editor, the features it offers,
and consider if I would want PyPE to have such features, what changes would be
necessary, and what it would take to make them happen.  This has produced
things like workspaces, shells, find/replace bars (idea from Firefox),
triggers (and most everything else in the Transforms menu), the name and line
oriented browsable source trees, etc.</p>
<p>Occasionally, some user of PyPE will contact me, perhaps report a bug, or
somesuch, and eventually either suggest features or offer up patches.  While
I had written the original Search tab, the current Search tab and the table
display of results were submitted almost complete.  Suggestions have resulted
in the addition of Start/End selection, bookmarks, the line-based abstraction
for macros, macros themselves, tools whose positions can be switched, title
options, the optional toolbar, caret tracking and width options, find/replace
bar history, the actual find/replace bar keybindings and what they do based on
context, the embedded HTML help, the Find Definition/filter tool, etc.</p>
<p>Astute observers will note that I have not really come up with anything
terribly original myself.  However, through observing other editors and IDEs,
and receiving great suggestions from users, I think that PyPE has managed to
acquire some very useful features.  Generally, I have written PyPE primarily
for myself, so if tools have a particular aesthetic or design, it's so that
look and work according to how I think they should (the exception being how
document preferences are handled, I really need to change that design).  I
hope that others find PyPE as natural to use as I do, but if not, then I
welcome your feedback.</p>
</div>
<div class="section" id="what-s-the-deal-with-the-version-numbering-scheme">
<h2><a class="toc-backref" href="#id59">What's the deal with the version numbering scheme?</a></h2>
<p>Early in development, PyPE raised version numbers very quickly.  From 1.0 to
1.5, not much more than 2 months passed.  In that time, most of the major
initial architectural changes that were to happen, happened.  This is not the
reason for the version number change.  Really it was so that the MAJOR
versions could have their own point release (1.0 being the first), and minor
bugfixes on the point releases would get a minor release number (like 1.0.1).</p>
<p>Then, at around PyPE 1.4.2, I had this spiffy idea.  What if I were to release
a series of PyPE versions with the same version numbers as classic Doom?  I
remembered updating to 1.1, then to 1.2a, etc.  My favorite was 1.666.  Ah
hah! PyPE 1.6.6.6, the best version of PyPE ever.</p>
<p>I decided that I would slow version number advancement, if only so that people
didn't get sick of new releases of PyPE being numbered so much higher when
there were minimal actual changes.  Then the more I thought about it, the more
I realized that it doesn't matter at all, I mean, Emacs is on version 20+.
*shrug*</p>
<p>When PyPE 1.9.3 came out, I had a few other ideas for what I wanted to happen,
but since major changes to the underlying architecture were required, it
really should get a major number bump to 2.0.  After spending 3 months not
working on PyPE May-July 2004, I got some time to muck around with it here and
there.  After another few months of trying to rebuild it to only require a
single STC (with multiple document pointers, etc.) I realized that I'd have to
rebuild too much of PyPE to be able to get 2.0 out the door by 2010.  So I
started modifying 1.9.3.  All in all, around 85% of what I wanted made it into
PyPE 2.0, the rest was either architectural (ick), or questionable as to
whether or not anyone would even want to use the feature (even me).</p>
</div>
<div class="section" id="how-did-pype-come-about">
<h2><a class="toc-backref" href="#id60">How did PyPE come about?</a></h2>
<p>The beginnings of PyPE were written from 10:30PM on the 2nd of July through
10:30PM on the 3rd of July, 2003.  Additional features were put together on
the 4th of July along with some bug fixing and more testing for version 1.0.
Truthfully, I've been using it to edit itself since the morning of the 3rd of
July, and believe it is pretty much feature-complete (in terms of standard
Python source editing).  There are a few more things I think it would be nice
to have, and they will be added in good time (if I have it).</p>
<p>One thing you should never expect is for PyPE to become an IDE.  Don't expect
a UML diagram.  Don't expect a debugger.  Don't expect debugging support
(what, print statements not good enough for you?)</p>
<p>On the most part, this piece of software should work exactly the way you
expect it to...or at least the way I expect it to.  That is the way I wrote
it.  As a result, you don't get much help in using it (mostly because I am
lazy).  There was a discussion of a PyPE wiki a long time ago, but that will
likely never happen (I've lost contact with the people who initially put
forward the wiki idea, and I have no interest in starting or maintaining one).</p>
<p>The majority of the things that this editor can do are in the menus.  Hotkeys
for things that have them are listed next to their menu items, and you can
both rename menu items and change their hotkeys via Options-&gt;Change Menus and
Hotkeys.</p>
</div>
</div>
<div class="section" id="thank-yous">
<h1><a class="toc-backref" href="#id61">Thank Yous</a></h1>
<p>Certainly there are some people I should thank, because without them, the
piece of software you are using right now, just wouldn't be possible.</p>
<p>Guido van Rossum - without Guido, not only would I not have Python, I also
wouldn't have had some of the great inspiration that IDLE has offered.  IDLE
is a wonderful editor, has some excellent ideas in terms of functionality, but
unfortunately does not offer the extended functionality I want, and it hurts
my brain to use tk, so I cannot add it myself.</p>
<p>The people writing wxWidgets (previously named wxWindows) and wxPython -
without you, this also would not have been possible.  You have made the most
self-consistent GUI libraries that I have ever used, made them easy to use,
and offer them on every platform that I would ever want or need.  You rock.</p>
<p>Neil Hodgson and others who work on Scintilla.  As wx.StyledTextCtrl is a
binding for scintilla in wxWidgets, which then has bindings for wxPython,
basically ALL the REAL functionality of the editor you are now using is the
result of Scintilla.  The additional things like tabbed editing, hotkeys,
etc., they are mere surface decorations in comparison to what it would take to
write everything required for a text editor from scratch.  Gah, an editor
widget that just works?  Who would have figured?</p>
<p>To everyone who I have already thanked: thank you for making PyPE an almost
trivial task.  It would have been impossible to go so far so fast by hand in
any other language using any other GUI toolkit or bindings.</p>
</div>
</div>
</body>
</html>