[Idle-dev] CVS: idle INSTALLATION,1.1,1.2 setup.py,1.4,1.5

Kurt B. Kaiser kbk@users.sourceforge.net
Mon, 16 Jul 2001 22:12:44 -0700


Update of /cvsroot/idlefork/idle
In directory usw-pr-cvs1:/tmp/cvs-serv14862

Modified Files:
	INSTALLATION setup.py 
Log Message:
INSTALLATION: Remove the coexist.patch instructions

****************
setup.py: 

Remove the idles script, add some words on IDLE Fork to the
long_description, and clean up some line spacing.


Index: INSTALLATION
===================================================================
RCS file: /cvsroot/idlefork/idle/INSTALLATION,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -r1.1 -r1.2
*** INSTALLATION	2001/07/16 07:08:20	1.1
--- INSTALLATION	2001/07/17 05:12:42	1.2
***************
*** 36,54 ****
  
  NOTE that the above procedure will install idlefork IDLE on top of any
! "official" IDLE that may be already installed.  If you wish to avoid doing
! that, there is a patch file, coexist.patch, in the idlefork directory. If,
! _*before*_ you install idle, you run
! 
! # patch -p0 < coexist.patch
! 
! idlefork will be modified so that it installs as .../site-packages/fildlelib,
! idle as fidle, and idles as fidles. (If you previously installed without
! patching, remove the idlefork/build directory before running the install.)
! 
! NOTE: You must then append "fidlelib" to site-packages.pth !
! 
! Then "official" IDLE and idlefork IDLE will exist side by side for comparision.
! And if idlefork is temporarily broken :-(, well, you have your old IDLE ways.
! 
! This is obviously an expedient development hack, but if popular, I imagine
! there could be a setup option.
--- 36,38 ----
  
  NOTE that the above procedure will install idlefork IDLE on top of any
! "official" IDLE that may be already installed.
\ No newline at end of file

Index: setup.py
===================================================================
RCS file: /cvsroot/idlefork/idle/setup.py,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** setup.py	2001/07/16 04:00:10	1.4
--- setup.py	2001/07/17 05:12:42	1.5
***************
*** 56,59 ****
--- 56,60 ----
  # Arghhh. install_lib thinks that all files returned from build_py's
  # get_outputs are bytecode files
+ 
  class idle_install_lib(install_lib):
      def _bytecode_filenames(self, files):
***************
*** 61,68 ****
          return install_lib._bytecode_filenames(self,files)
  
- 
  setup(name="IDLE",
        version = idlever.IDLE_VERSION,
!       description = "IDLE, the Python IDE",
        author = "Guido van Rossum",
        author_email = "guido@python.org",
--- 62,68 ----
          return install_lib._bytecode_filenames(self,files)
  
  setup(name="IDLE",
        version = idlever.IDLE_VERSION,
!       description = "IDLE Fork, the Forked Python IDE",
        author = "Guido van Rossum",
        author_email = "guido@python.org",
***************
*** 72,76 ****
  Python and works both on Windows and Unix. It features a multi-window
  text editor with multiple undo, Python colorizing, and many other things,
! as well as a Python shell window and a debugger.""",
  
        cmdclass = {'build_py':idle_build_py,
--- 72,81 ----
  Python and works both on Windows and Unix. It features a multi-window
  text editor with multiple undo, Python colorizing, and many other things,
! as well as a Python shell window and a debugger.
! 
! IDLE Fork is a separate line of development which was initiated by D. Scherer
! at CMU as part of Visual Python.  It features execution in a separate
! process, with a fresh environment for each run. For further details, 
! refer to idlefork.sourceforge.net.""",
  
        cmdclass = {'build_py':idle_build_py,
***************
*** 78,81 ****
        package_dir = {idlelib:'.'},
        packages = [idlelib],
!       scripts = ['idle', 'idles']
        )
--- 83,86 ----
        package_dir = {idlelib:'.'},
        packages = [idlelib],
!       scripts = ['idle']
        )