From gward@mems-exchange.org  Fri Sep  8 15:14:26 2000
From: gward@mems-exchange.org (Greg Ward)
Date: Fri, 8 Sep 2000 10:14:26 -0400
Subject: [Idle-dev] Distutil-ized IDLE
In-Reply-To: <20000908085930.A15918@ludwig.cnri.reston.va.us>; from gward@mems-exchange.org on Fri, Sep 08, 2000 at 08:59:30AM -0400
References: <20000908085930.A15918@ludwig.cnri.reston.va.us>
Message-ID: <20000908101426.A16014@ludwig.cnri.reston.va.us>

On 08 September 2000, I said:
> I would be happy to write a setup script that makes it easy to install
> Tools/idle as a "third-party" module distribution, complete with a
> launch script, if there's interest.  Oh hell, maybe I'll do it
> anyways... just howl if you don't think I should check it in.

OK, as threatened, I've written a setup script for IDLE.  (Specifically,
the version in Tools/idle in the Python 1.6 and 2.0 source
distributions.)  This installs IDLE into a pacakge "idle", which means
that the imports in idle.py have to change.  Rather than change idle.py,
I wrote a new script just called "idle"; this would replace idle.py and
be installed in <prefix>/bin (on Unix -- I think scripts installed by
the Distutils go to <prefix>/Scripts on Windows, which was a largely
arbitrary choice).

Anyways, here's the setup script:

  #!/usr/bin/env python

  import os
  from distutils.core import setup
  from distutils.command.install_data import install_data

  class IDLE_install_data (install_data):
      def finalize_options (self):
          if self.install_dir is None:
              install_lib = self.get_finalized_command('install_lib')
              self.install_dir = os.path.join(install_lib.install_dir, "idle")

  setup(name = "IDLE",
        version = "0.6",
        author = "Guido van Rossum",
        author_email = "guido@python.org",
        cmdclass = {'install_data': IDLE_install_data},
        packages = ['idle'],
        package_dir = {'idle': ''},
        scripts = ['idle'],
        data_files = ['config.txt', 'config-unix.txt', 'config-win.txt'])

And the changes I suggest to make IDLE smoothly installable:
  * remove idle.py 
  * add this setup.py and idle (which is just idle.py with the imports
    changed)
  * add some instructions on how to install and run IDLE somewhere

I just checked the CVS repository for the IDLE fork, and don't see a
setup.py there either -- so presumably the forked IDLE could benefit
from this as well (hence the cc: idle-dev@python.org).

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange / CNRI                           voice: +1-703-262-5376
Reston, Virginia, USA                            fax: +1-703-262-5367

From roberto@ccmc.unam.mx  Mon Sep 18 22:21:08 2000
From: roberto@ccmc.unam.mx (Roberto Machorro Mejia)
Date: Mon, 18 Sep 2000 21:21:08 +0000
Subject: [Idle-dev] installation denied
Message-ID: <39C68744.3E79DB9F@ccmc.unam.mx>

Hello every one!
  I am new in Python and IDLE. When trying to run IDLE I got the problem

[roberto@pc-machorro idle]$ python idle.py
Traceback (innermost last):
  File "idle.py", line 3, in ?
    PyShell.main()
  File "PyShell.py", line 625, in main
    t = PyShell(flist)
  File "PyShell.py", line 255, in __init__
    OutputWindow.__init__(self, flist, None, None)
  File "OutputWindow.py", line 15, in __init__
    apply(EditorWindow.__init__, (self,) + args)
  File "EditorWindow.py", line 153, in __init__
    self.saved_change_hook()
  File "EditorWindow.py", line 393, in saved_change_hook
    self.top.wm_title(title)
AttributeError: wm_title

Placing a coment to this line make the program continue, open a tk
window but errors in there.
How can I solve this problem?
Thank you in advance
Roberto


From njriley@uiuc.edu  Tue Sep 19 02:15:59 2000
From: njriley@uiuc.edu (Nicholas Riley)
Date: Mon, 18 Sep 2000 20:15:59 -0500
Subject: [Idle-dev] idleFork 0.7 tgz file
In-Reply-To: <399A8C00.CFBFDF8F@nowonder.de>; from nowonder@nowonder.de on Wed, Aug 16, 2000 at 12:41:36PM +0000
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de>
Message-ID: <20000918201559.A17179@uiuc.edu>

On Wed, Aug 16, 2000 at 12:41:36PM +0000, Peter Schneider-Kamp wrote:
> idlefork-0.7.1.tar.gz should correct this.

Is development on this going on somewhere?  I just tried to get
idlefork-0.7.1 running in Python 1.6 and had to fix a couple of
obvious problems in protocol.py and spawn.py that were preventing me
from running anything.  The SourceForge project has looked pretty dead
since the initial upload...

-- 
Nicholas Riley <njriley@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>

From peter@schneider-kamp.de  Tue Sep 19 09:07:35 2000
From: peter@schneider-kamp.de (Peter Schneider-Kamp)
Date: Tue, 19 Sep 2000 08:07:35 +0000
Subject: [Idle-dev] idleFork 0.7 tgz file
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de> <20000918201559.A17179@uiuc.edu>
Message-ID: <39C71EC7.E18DCE82@schneider-kamp.de>

Hi Nicholas!

I would very much appreciate if you could send me patches for the
changes you've made. If you would like to contribute to idlefork,
you can be added as a developer and/or admin at SourceForge in
almost no time (besides the 6 hour cron delay <wink>).

Nicholas Riley wrote:
> 
> The SourceForge project has looked pretty dead
> since the initial upload...

Actually it has been pretty dead. I have moved from Norway to
Germany and I still don't have my own computer running on the
net. Another factor is, that the number of people volunteering
to help has been exactly nil. :-/

Peter

From guido@beopen.com  Tue Sep 19 14:44:05 2000
From: guido@beopen.com (Guido van Rossum)
Date: Tue, 19 Sep 2000 08:44:05 -0500
Subject: [Idle-dev] idleFork 0.7 tgz file
In-Reply-To: Your message of "Tue, 19 Sep 2000 08:07:35 GMT."
 <39C71EC7.E18DCE82@schneider-kamp.de>
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de> <20000918201559.A17179@uiuc.edu>
 <39C71EC7.E18DCE82@schneider-kamp.de>
Message-ID: <200009191344.IAA02100@cj20424-a.reston1.va.home.com>

> > The SourceForge project has looked pretty dead
> > since the initial upload...
> 
> Actually it has been pretty dead. I have moved from Norway to
> Germany and I still don't have my own computer running on the
> net. Another factor is, that the number of people volunteering
> to help has been exactly nil. :-/

Peter,

Let me tell you from experience that this is nothing unusual.  People
are reluctant to contribute to a project that seems to have no
activity -- it's like being the first to arrive at a party, or like
being the only guests in a restaurant.

But there's a way to break out of that vicious circle: get things
going!  Add Nicholas to the list of developers (so he can check in his
own fixes), add a feature or two of your own, and call it a release!

It doesn't matter that it's not perfect -- the more rough edges, the
more motivation people have to participate.  Don't be shy to give
others checkin privileges (once they've contributed something good).

Once you have something to talk about, the word will spread.

--Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)

From peter@schneider-kamp.de  Wed Sep 20 09:07:21 2000
From: peter@schneider-kamp.de (Peter Schneider-Kamp)
Date: Wed, 20 Sep 2000 08:07:21 +0000
Subject: [Idle-dev] idleFork 0.7 tgz file
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de> <20000918201559.A17179@uiuc.edu>
 <39C71EC7.E18DCE82@schneider-kamp.de> <200009191344.IAA02100@cj20424-a.reston1.va.home.com>
Message-ID: <39C87039.A3373C2B@schneider-kamp.de>

Guido van Rossum wrote:
> 
> But there's a way to break out of that vicious circle: get things
> going!  Add Nicholas to the list of developers (so he can check in his
> own fixes), add a feature or two of your own, and call it a release!

Thanks for the advice. I have added Nicholas (and Fred) to the
developer list.

Do you have any ideas on the direction idlefork should/could be
heading in? I don't really have that many of them:

1. Make it stable.
2. Improve command line arguments.
3. Make it more configurable (auto save on run as an option etc.).

Peter

From jbaker@ummelec.com  Wed Sep 20 22:36:58 2000
From: jbaker@ummelec.com (Jake Baker)
Date: Wed, 20 Sep 2000 16:36:58 -0500
Subject: [Idle-dev] idleFork 0.7 tgz file
Message-ID: <s9c8e7b7.029@gwia.ummelec.com>

> Do you have any ideas on the direction idlefork should/could be
> heading in? I don't really have that many of them:

> 3. Make it more configurable (auto save on run as an option etc.).

I have been working on this (from the 0.6 baseline, since I can't get the =
sourceforge stuff to work for me.)

So far I've added:

 * Recent Files Sub-Menu
 * Recent Directories Sub-Menu
 * Use application CWD for open/save dialogs
 * Auto save before run
 * A user-edited list of help files

(I also comment my code. *grin*)

Right now I'm working on a dialog box where the user can edit these =
options. I want to add the stuff in the config files here too (especially =
syntax coloring options.)

If I can ever make the sourceforge stuff work for me [1], I'll be happy to =
share my work. (Although I'm using Pmw for the Options Dialog, and I don't =
know other's feelings about requiring users to install a package before =
they can use it.)

 - Jake Baker


From David_Abrahams@dragonsys.com  Thu Sep 21 01:23:11 2000
From: David_Abrahams@dragonsys.com (David_Abrahams@dragonsys.com)
Date: Wed, 20 Sep 2000 20:23:11 -0400
Subject: [Idle-dev] Re: IDLE-dev digest, Vol 1 #66 - 1 msg
Message-ID: <OF974E9003.1B1FF9FB-ON85256961.00020847@dragonsys.com>

Er, if I may: fix debugging capabilities for Win32
-Dave


Please respond to idle-dev@python.org
Sent by:        idle-dev-admin@python.org
To:     idle-dev@python.org
cc: 
Subject:        IDLE-dev digest, Vol 1 #66 - 1 msg


Send IDLE-dev mailing list submissions to
        idle-dev@python.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.python.org/mailman/listinfo/idle-dev
or, via email, send a message with subject or body 'help' to
        idle-dev-request@python.org

You can reach the person managing the list at
        idle-dev-admin@python.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of IDLE-dev digest..."


Today's Topics:

   1. Re: idleFork 0.7 tgz file (Peter Schneider-Kamp)

--__--__--

Message: 1
Date: Wed, 20 Sep 2000 08:07:21 +0000
From: Peter Schneider-Kamp <peter@schneider-kamp.de>
To: Guido van Rossum <guido@beopen.com>
Cc: Nicholas Riley <njriley@uiuc.edu>, idle-dev@python.org
Subject: Re: [Idle-dev] idleFork 0.7 tgz file

Guido van Rossum wrote:
>
> But there's a way to break out of that vicious circle: get things
> going!  Add Nicholas to the list of developers (so he can check in his
> own fixes), add a feature or two of your own, and call it a release!

Thanks for the advice. I have added Nicholas (and Fred) to the
developer list.

Do you have any ideas on the direction idlefork should/could be
heading in? I don't really have that many of them:

1. Make it stable.
2. Improve command line arguments.
3. Make it more configurable (auto save on run as an option etc.).

Peter



--__--__--

_______________________________________________
IDLE-dev mailing list
IDLE-dev@python.org
http://www.python.org/mailman/listinfo/idle-dev


End of IDLE-dev Digest



From hei@adtranzsig.de  Thu Sep 21 08:43:09 2000
From: hei@adtranzsig.de (Dirk-Ulrich Heise)
Date: Thu, 21 Sep 2000 09:43:09 +0200
Subject: [Idle-dev] idleFork 0.7 tgz file
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de> <20000918201559.A17179@uiuc.edu>              <39C71EC7.E18DCE82@schneider-kamp.de> <200009191344.IAA02100@cj20424-a.reston1.va.home.com> <39C87039.A3373C2B@schneider-kamp.de>
Message-ID: <004f01c0239f$96ad83e0$13ec1fc2@adtranzsig.de>

-----Ursprüngliche Nachricht-----
Von: "Peter Schneider-Kamp" <peter@schneider-kamp.de>
> Do you have any ideas on the direction idlefork should/could be
> heading in? I don't really have that many of them:

How about a macro facility?
E.g., some menu bar that is independent of  the IDLE main window,
thus, permanently floating somewhere, with a python function attached
to each entry in it, and one top entry saying "ChangeThis", so clicking on
it would warp you into the script that defines the macros.
Alternatively, as a local (right-click) menu. (How do Macs handle that
without a right mouse button???)

Or, a key-reinterpreting python script with some useful completions,
like, typing "if " in an empty line would automatically expand to
   if :
   else:
etc.

If IDLE has already grown one or the other macro facility,
forgive me, it's been a while since i last used it.

And finally, Bicycle Repair Man (the Python refactoring browser)
comes to mind - could an integration
between BRM and IDLE make sense? I suppose BRM is mainly
confessed with parsing, maybe using IDLE as its front-end
would make sense.

Dipl.Inform. Dirk-Ulrich Heise
hei@adtranzsig.de
dheise@debitel.net



From guido@beopen.com  Thu Sep 21 19:09:04 2000
From: guido@beopen.com (Guido van Rossum)
Date: Thu, 21 Sep 2000 13:09:04 -0500
Subject: [Idle-dev] idleFork 0.7 tgz file
In-Reply-To: Your message of "Wed, 20 Sep 2000 08:07:21 GMT."
 <39C87039.A3373C2B@schneider-kamp.de>
References: <v04210101b5bf5d71de12@[192.12.134.105]> <399A8C00.CFBFDF8F@nowonder.de> <20000918201559.A17179@uiuc.edu> <39C71EC7.E18DCE82@schneider-kamp.de> <200009191344.IAA02100@cj20424-a.reston1.va.home.com>
 <39C87039.A3373C2B@schneider-kamp.de>
Message-ID: <200009211809.NAA29474@cj20424-a.reston1.va.home.com>

> Do you have any ideas on the direction idlefork should/could be
> heading in? I don't really have that many of them:

Have a look at the TODO file!  There are a ton of things to be worked
on.

--Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)

From jbaker@ummelec.com  Mon Sep 25 20:58:20 2000
From: jbaker@ummelec.com (Jake Baker)
Date: Mon, 25 Sep 2000 14:58:20 -0500
Subject: [Idle-dev] Idle config file preference inquiry
Message-ID: <s9cf6818.076@gwia.ummelec.com>

Hi all!

 I'm working on a GUI dialog box for editing the parameters in IDLEs =
config files. My question is: where and how should I save this information?=
 One of my desires is to have the config.txt file still be editable in a =
text file, so I need to leave those alone in some fashion.

 My current solution is this:

 Changes to config made through the editor are saved to a config.inf file =
in the idle directory. This file is placed last in the load list for =
IdleConfig so that it's params override those set in the manual config =
files.

 This method leaves a lot to be desired, but I can't think of anything =
better. [Note: I was going to rewrite the changes to config.txt (leaving =
comments and whitespace alone) but there's two problems with that: which =
config file *where* (idle/config or ~/config) and *which* config file =
('cause idle uses 3 - config.txt, config-xxx.txt and something else.)

 Your ideas are appreciated,
 - Jake



From guido@beopen.com  Tue Sep 26 02:57:44 2000
From: guido@beopen.com (Guido van Rossum)
Date: Mon, 25 Sep 2000 20:57:44 -0500
Subject: [Idle-dev] Idle config file preference inquiry
In-Reply-To: Your message of "Mon, 25 Sep 2000 14:58:20 EST."
 <s9cf6818.076@gwia.ummelec.com>
References: <s9cf6818.076@gwia.ummelec.com>
Message-ID: <200009260157.UAA25904@cj20424-a.reston1.va.home.com>

>  I'm working on a GUI dialog box for editing the parameters in IDLEs
>  config files. My question is: where and how should I save this
>  information? One of my desires is to have the config.txt file still
>  be editable in a text file, so I need to leave those alone in some
>  fashion.

Great idea!!!

>  My current solution is this:
> 
>  Changes to config made through the editor are saved to a config.inf
>  file in the idle directory. This file is placed last in the load
>  list for IdleConfig so that it's params override those set in the
>  manual config files.
> 
>  This method leaves a lot to be desired, but I can't think of
>  anything better. [Note: I was going to rewrite the changes to
>  config.txt (leaving comments and whitespace alone) but there's two
>  problems with that: which config file *where* (idle/config or
>  ~/config) and *which* config file ('cause idle uses 3 - config.txt,
>  config-xxx.txt and something else.)

Definitely ~/.idle.  The others are for storing defaults.  Don't
bother about keeping the comments; it's probably too hard.

--Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)