1. zjes
  2. rope_py3k

Commits

Ali Gholami Rudi  committed 73bf30a

Updated docs

  • Participants
  • Parent commits d258a28
  • Branches trunk

Comments (0)

Files changed (4)

File README.txt

View file
 New Features
 ============
 
-* Inlining a single occurrence
-* Global extract method/variable
-* Reporting fixed errors when ``max_fixes`` errors were fixed but yet
-  there are more syntax errors when using code-assist
-* Better scope finding
-* Better return value inference
-
-``Inline(Method|Variable).get_changes()`` take a new parameter called
-``only_current``.  If ``True``, only the current occurrence will be
-inlined.
-
-``Extract(Variable|Method).get_changes()`` take a new parameter called
-``global_``.  If ``True``, the extracted variable|method will be made
-global and the whole file is searched for similar pieces instead of
-the original search scope.
-
 
 Getting Started
 ===============

File docs/overview.txt

View file
 
 Note that the global `a_func` was not renamed because we are sure that
 it is not a match.  But when using this option there might be some
-unexpected renames.  So only use this option when the name is not
-another python defined elements.
+unexpected renames.  So only use this option when the name is almost
+unique and is not defined in other places.
 
 Move Method Refactoring
 -----------------------
 
 It happens when you perform move refactoring on a method of a class.
-In this refactoring a method of a class is moved to the class of one
+In this refactoring, a method of a class is moved to the class of one
 of its attributes.  The old method will call the new method.  If you
 want to change all of the occurrences of the old method to use the new
 method you can inline it afterwards.
 -------------
 
 Rope does not have a separate refactoring for moving fields.  Rope's
-refactorings are very flexible.  You can use the rename refactoring to
-rename fields.  For instance::
+refactorings are very flexible, though.  You can use the rename
+refactoring to move fields.  For instance::
 
   class A(object):
       pass
 Restructurings
 --------------
 
-Restructuring support was one of the main goals of the ``0.6`` release
-of rope.  `rope.refactor.restructure` can be used for performing
-restructurings.  Currently a simple dialog has been added for
-performing them in the IDE.
-
+`rope.refactor.restructure` can be used for performing restructurings.
 A restructuring is a program transformation; not as well defined as
 other refactorings like rename.  Let's see some examples.
 
   a = A()
   a.f(1, 2)
 
-But who's going to fix all those nasty occurrences (Actually this
+But who's going to fix all those nasty occurrences (actually this
 situation can be handled using inline method refactoring but this is
-just an example; Consider inline refactoring is not implemented yet!).
+just an example; consider inline refactoring is not implemented yet!).
 Restructurings come to rescue::
 
   pattern: ${?inst}.f(${?p1}, ${?p2})

File docs/rope.txt

View file
   * Extract method/local variable
   * Move class/function/module/package/method
   * Inline method/local variable
-  * Change method signature
   * Restructuring (like converting ``${?a}.f(${?b})`` to
     ``${?b}.g(${?a})`` where ``a.type == mymod.A``)
+  * Change method signature
   * Introduce factory method
   * Introduce parameter
   * Encapsulate field

File rope/__init__.py

View file
 """rope, a python refactoring library"""
 
 INFO = __doc__
-VERSION = '0.7.3'
+VERSION = '0.7.4'
 COPYRIGHT = """\
 Copyright (C) 2006-2007 Ali Gholami Rudi